Skip site navigation (1) Skip section navigation (2)

Re: Feature freeze progress report

From: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
To: Lukas Kahwe Smith <smith(at)pooteeweet(dot)org>
Cc: Alvaro Herrera <alvherre(at)commandprompt(dot)com>, pgsql-hackers(at)postgresql(dot)org
Subject: Re: Feature freeze progress report
Date: 2007-04-29 17:07:46
Message-ID: 24513.1177866466@sss.pgh.pa.us (view raw or flat)
Thread:
Lists: pgsql-hackerspgsql-www
Lukas Kahwe Smith <smith(at)pooteeweet(dot)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

In response to

pgsql-www by date

Next:From: Marc G. FournierDate: 2007-04-29 17:15:13
Subject: Profiling disabled on Wiki ...
Previous:From: Tom LaneDate: 2007-04-29 16:53:30
Subject: Re: Feature freeze progress report

pgsql-hackers by date

Next:From: shieldyDate: 2007-04-29 17:36:36
Subject: SOS, help me please, one problem towards the postgresql developement on windows
Previous:From: Tom LaneDate: 2007-04-29 16:58:51
Subject: Re: strange buildfarm failures

Privacy Policy | About PostgreSQL
Copyright © 1996-2014 The PostgreSQL Global Development Group