To: Lukas Kahwe Smith <smith@pooteeweet.org>
cc: Alvaro Herrera <alvherre@commandprompt.com>, pgsql-hackers@postgresql.org
Subject: Re: Feature freeze progress report 
In-reply-to: <4634C81E.3040100@pooteeweet.org> 
References: <200704270313.l3R3DwF16449@momjian.us>
	<1177792836.3663.61.camel@silverbirch.site>
	<46348320.7080808@kaltenbrunner.cc>
	<20070429154006.GA18593@alvh.no-ip.org>
	<4634C81E.3040100@pooteeweet.org>
Comments: In-reply-to Lukas Kahwe Smith <smith@pooteeweet.org>
	message dated "Sun, 29 Apr 2007 09:30:22 -0700"
Date: Sun, 29 Apr 2007 13:07:46 -0400
Message-ID: <24513.1177866466@sss.pgh.pa.us>
From: Tom Lane <tgl@sss.pgh.pa.us>

Lukas Kahwe Smith <smith@pooteeweet.org> writes:
> Hmm, I do not have an overview on this, but like Alvaro mentions, the 
> shorter release cycles for 8.3 was done because we felt that a number of 
> patches that were originally slated for 8.2 were almost but not quite 
> ready for 8.2. So are all of those patches from back then ready to go 
> into 8.3? If not then it would indicate that fast tracking a release 
> cycle for patches there are not quite there yet is not paying off?

In fact several of the major ones are still not ready, so I think that
experience is evidence that we couldn't handle a six-month release cycle
anyway.  We'll still stick to the announced 8.3 schedule though, since
part of the reason for it was to rotate around to a spring release time
instead of a fall release time, on the thought that that might work more
conveniently for many people.

			regards, tom lane