To: Eric Lee Green <eric@linux-hw.com>
cc: "pgsql-hackers@postgreSQL.org" <pgsql-hackers@postgreSQL.org>,
	PostgreSQL Interfaces <pgsql-interfaces@postgreSQL.org>
Subject: Re: [INTERFACES] crypt not included when compiling libpgtcl !!!!!!! 
In-reply-to: Your message of Mon, 7 Dec 1998 00:18:48 -0500 (EST)
	<Pine.LNX.4.04.9812070002280.535-100000@england.local.net>
Date: Mon, 07 Dec 1998 00:54:32 -0500
Message-ID: <2699.913010072@sss.pgh.pa.us>
From: Tom Lane <tgl@sss.pgh.pa.us>

Eric Lee Green <eric@linux-hw.com> writes:
> I have to maintain a stable Postgres on my development machine. The reason
> I'm working on the 6.4 RPM for Red Hat 5.2 is for deployment purposes, not
> for testing purposes, though of course I'll test it before deploying it.
> (I want the latest stable version possible for deployment, because once
> deployed, it will be out there for a LONG time).

Fair enough.  I have not been around Postgres very long and may be out
of line to make this remark, but here goes anyway: as far as I've seen,
the minor releases (6.3.2, 6.4.1, etc) are likely to be your best bet
for a solid install-and-forget version.  Major releases are for feature
additions, minor releases are made to clean up whatever got broken. 
We do the best we can to test major releases before they go out, but
things do slip through the cracks sometimes.

In short, unless you need something in the next few days, the upcoming
6.4.1 release is likely to be a better bet for an RPM distribution
than 6.4.

Perhaps one of the senior Postgres guys would like to expound on the
release philosophy?  The above is just what I've observed, it may
not be the official policy...

			regards, tom lane