Received: from localhost (maia-2.hub.org [200.46.204.187]) by postgresql.org (Postfix) with ESMTP id 4F0279FB464 for ; Sun, 29 Apr 2007 12:40:40 -0300 (ADT) Received: from postgresql.org ([200.46.204.71]) by localhost (mx1.hub.org [200.46.204.187]) (amavisd-maia, port 10024) with ESMTP id 84764-08 for ; Sun, 29 Apr 2007 12:40:13 -0300 (ADT) X-Greylist: from auto-whitelisted by SQLgrey-1.7.4 Received: from lists.commandprompt.com (host-254.commandprompt.net [207.173.203.254]) by postgresql.org (Postfix) with ESMTP id BF5919FB488 for ; Sun, 29 Apr 2007 12:40:35 -0300 (ADT) Received: from perhan.alvh.no-ip.org (201-221-221-161.bk12-dsl.surnet.cl [201.221.221.161]) (authenticated bits=0) by lists.commandprompt.com (8.13.7/8.13.6) with ESMTP id l3TFeASI027681; Sun, 29 Apr 2007 08:40:11 -0700 Received: by perhan.alvh.no-ip.org (Postfix, from userid 1000) id DFD8C32A10; Sun, 29 Apr 2007 11:40:06 -0400 (CLT) Date: Sun, 29 Apr 2007 11:40:06 -0400 From: Alvaro Herrera To: Stefan Kaltenbrunner Cc: Simon Riggs , Bruce Momjian , PostgreSQL-development Subject: Re: Feature freeze progress report Message-ID: <20070429154006.GA18593@alvh.no-ip.org> Mail-Followup-To: Stefan Kaltenbrunner , Simon Riggs , Bruce Momjian , PostgreSQL-development References: <200704270313.l3R3DwF16449@momjian.us> <1177792836.3663.61.camel@silverbirch.site> <46348320.7080808@kaltenbrunner.cc> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <46348320.7080808@kaltenbrunner.cc> User-Agent: Mutt/1.5.13 (2006-08-11) X-Virus-Scanned: ClamAV version 0.88.5, clamav-milter version 0.88.5 on projects.commandprompt.com X-Virus-Status: Clean X-Greylist: Sender succeded SMTP AUTH authentication, not delayed by milter-greylist-1.6 (lists.commandprompt.com [192.168.2.159]); Sun, 29 Apr 2007 08:40:16 -0700 (PDT) X-Virus-Scanned: Maia Mailguard 1.0.1 X-Archive-Number: 200704/1197 X-Sequence-Number: 102530 Stefan Kaltenbrunner wrote: > Simon Riggs wrote: > > I would also suggest that 8.3 be labelled a dev release. We have a > > reasonable number of fairly invasive patches, so we need a mechanism to > > integrate them with reduced risk. > > I would rather like to see patches we don't are confident enough in to > be dropped from 8.3 and moved to 8.4 - the goal should not be jamming as > much patches into a single release s we can (because they are proposed) > but rather putting those in that meet the quality bar and we trust in. 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. (The only complication would be the pgindent changes which could cause merge problems for some patches. It would be good to have a mechanism to "update" a patch over pgindent easily.) -- Alvaro Herrera http://www.CommandPrompt.com/ PostgreSQL Replication, Consulting, Custom Development, 24x7 support