Re: 8.4 release planning
Dimitri Fontaine <dfontaine@hi-media.com>
From: Dimitri Fontaine <dfontaine@hi-media.com>
To: Simon Riggs <simon@2ndQuadrant.com>
Cc: Magnus Hagander <magnus@hagander.net>, Robert Treat <xzilla@users.sourceforge.net>, "pgsql-hackers@postgresql.org" <pgsql-hackers@postgresql.org>, Tom Lane <tgl@sss.pgh.pa.us>, "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-28T21:22:52Z
Lists: pgsql-hackers
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? That would mean first 8.5 commit-fest begins e.g. April 1st, while hopefully 8.4 enters beta or get ready for it. If no commiter is available for reviewed patch they just get postponed as ready to commit on next commit fest. This way our Round Robin Reviewers team is still at work while in beta, and more importantly developpers still get feedback. -- dim