Horton

Re: 8.4 release planning

Tom Lane <tgl@sss.pgh.pa.us>

View thread View on postgr.es
From: Tom Lane <tgl@sss.pgh.pa.us>
To: Dimitri Fontaine <dfontaine@hi-media.com>
Cc: Simon Riggs <simon@2ndQuadrant.com>, Magnus Hagander <magnus@hagander.net>, Robert Treat <xzilla@users.sourceforge.net>, "pgsql-hackers@postgresql.org" <pgsql-hackers@postgresql.org>, "dpage@pgadmin.org" <dpage@pgadmin.org>, Josh Berkus <josh@agliodbs.com>, Jaime Casanova <jcasanov@systemguards.com.ec>, "Joshua D. Drake" <jd@commandprompt.com>, Robert Haas <robertmhaas@gmail.com>, Merlin Moncure <mmoncure@gmail.com>, "Jonah H. Harris" <jonah.harris@gmail.com>, Gregory Stark <stark@enterprisedb.com>, Bruce Momjian <bruce@momjian.us>, Bernd Helmle <mailings@oopsware.de>, Peter Eisentraut <peter_e@gmx.net>
Date: 2009-01-28T22:04:01Z
Lists: pgsql-hackers 
Dimitri Fontaine <dfontaine@hi-media.com> writes:
> Le 28 janv. 09  16:22, Simon Riggs <simon@2ndQuadrant.com> a crit :
>> The only way to keep the dev window open longer is to overlap the  
>> start of the next cycle with the previous one. i.e. branch new version  
>> before final release.

> This is the second time the idea is raised and I like it.

> Do we have anywhere near enough resources for this to happen?

No.  The key committers are overstressed already.

It would also pretty much guarantee that we get *no* help during review
and beta, because everyone else will find it more interesting/fun to
work on new patches instead.  The current system at least gives
non-committer developers some motivation to help with that stuff,
because they know their patches won't be looked at until beta is over.

			regards, tom lane