Re: commit fests (was Re: primary key error message) - Mailing list pgsql-hackers

From Robert Haas
Subject Re: commit fests (was Re: primary key error message)
Date
Msg-id 603c8f071001220610i612d7b98y1bfba8aa72ca25dd@mail.gmail.com
Whole thread Raw
In response to Re: commit fests (was Re: primary key error message)  (Peter Eisentraut <peter_e@gmx.net>)
Responses Re: commit fests (was Re: primary key error message)  (Andrew Dunstan <andrew@dunslane.net>)
Re: commit fests (was Re: primary key error message)  (Devrim GÜNDÜZ <devrim@gunduz.org>)
Re: commit fests (was Re: primary key error message)  (Tom Lane <tgl@sss.pgh.pa.us>)
Re: commit fests  (Dimitri Fontaine <dfontaine@hi-media.com>)
List pgsql-hackers
On Fri, Jan 22, 2010 at 8:40 AM, Peter Eisentraut <peter_e@gmx.net> wrote:
> On tor, 2010-01-21 at 18:05 -0500, Andrew Dunstan wrote:
>> Well, we used to have the idea of a feature freeze ... is that going
>> to apply at the end of the commitfest?
>
> Feature freeze was used to discourage the submission of very big patches
> shortly before beta.  The commit fest process has IMO alleviated this
> concern.  Beta is still the definite cutoff; and the closer we get to
> beta, the smaller the acceptable changes become.  I think that formula
> basically applies throughout the entire cycle.

I'm not sure whether you're stating a position that's been agreed to
by -core or some other group, or just expressing your own opinion, but
I think feature freeze should be the beginning of the last CommitFest,
not the end.

...Robert


pgsql-hackers by date:

Previous
From: Peter Eisentraut
Date:
Subject: Re: commit fests (was Re: primary key error message)
Next
From: Michael Meskes
Date:
Subject: Re: Fix auto-prepare #2