Received: from localhost (maia-5.hub.org [200.46.204.182]) by postgresql.org (Postfix) with ESMTP id 7341B9FB4CC for ; Mon, 30 Apr 2007 08:19:39 -0300 (ADT) Received: from postgresql.org ([200.46.204.71]) by localhost (mx1.hub.org [200.46.204.182]) (amavisd-maia, port 10024) with ESMTP id 21774-06 for ; Mon, 30 Apr 2007 08:19:31 -0300 (ADT) X-Greylist: from auto-whitelisted by SQLgrey-1.7.4 Received: from momjian.us (momjian.us [70.90.9.53]) by postgresql.org (Postfix) with ESMTP id 989959FB469 for ; Mon, 30 Apr 2007 08:19:35 -0300 (ADT) Received: (from bruce@localhost) by momjian.us (8.11.6/8.11.6) id l3UBJKZ10920; Mon, 30 Apr 2007 07:19:20 -0400 (EDT) From: Bruce Momjian Message-Id: <200704301119.l3UBJKZ10920@momjian.us> Subject: Re: Feature freeze progress report In-Reply-To: <4634C81E.3040100@pooteeweet.org> To: Lukas Kahwe Smith Date: Mon, 30 Apr 2007 07:19:20 -0400 (EDT) CC: Alvaro Herrera , pgsql-hackers@postgresql.org X-Mailer: ELM [version 2.4ME+ PL123] MIME-Version: 1.0 Content-Transfer-Encoding: 7bit Content-Type: text/plain; charset="US-ASCII" X-Virus-Scanned: Maia Mailguard 1.0.1 X-Archive-Number: 200704/1234 X-Sequence-Number: 102567 Lukas Kahwe Smith wrote: > Alvaro Herrera wrote: > > > Yeah; the agreement we had was that 8.3 would be a short release. So if > > we're going to take too long to review and apply the outstanding patches > > we have, we should rather push them to 8.4, get 8.3 released quickly and > > then go on with the regular annual release. The postponed patches can > > be reviewed and committed early in 8.4, instead of at the last minute in > > 8.3. Sounds like a smarter, safer move. > > 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? > > Otherwise, if all/most of the patches originally planned for 8.2 have > made it into 8.3, everything is good. If new additions are not yet ready > then they will just get bumped to 8.4, just like the changes that got > bumped to 8.3. The patches _might_ be ready. Please re-read my earlier posting that started this thread -- the major problem is new developers adding complex features, and the difficulty of reviewing all of that. Fortunately I have gotten approval from EnterpriseDB for Heikki to spend full-time helping with the 8.3 patch queue, and he, Tom and I have already been over many of the items via private email and will be moving forward. -- Bruce Momjian http://momjian.us EnterpriseDB http://www.enterprisedb.com + If your life is a hard drive, Christ can be your backup. +