On Wed, Mar 29, 2017 at 3:04 PM, Alvaro Herrera
<alvherre@2ndquadrant.com> wrote:
> Tom Lane wrote:
>> My own thought is that there's room for at least a few days' slop in
>> the end date of the final commitfest, depending on what patches remain
>> open and what the prospects are for getting them done. (In the past
>> we've sometimes let the final fest stretch on indefinitely, which is
>> clearly the Wrong Thing; but that doesn't mean that the Right Thing is
>> to say that it ends at 2017-04-01 00:00 UTC no matter what.) The RMT
>> should look at things in another day or two and make a judgment call
>> about that.
>
> I was rather surprised to see the March commitfest declared to exactly
> one month and feature freeze immediately thereafter. Last time around
> we left 2 weeks between CF end and feature freeze; the previous one I
> think we had the final CF last two months. Not stretch on indefinitely,
> but we know the final CF for a cycle takes more effort than previous
> ones, so it seems reasonable to give more time. We have a large number
> of patches still waiting for review.
That's true, but at
https://wiki.postgresql.org/wiki/PgCon_2016_Developer_Meeting we
agreed on March 31st as the feature freeze date. I don't think the
RMT should substantially vary a date that was agreed by a developer
meeting with wide attendance; that seems like the tyranny of the few
over the many. To quote from that page:
===
The dates agreed were:
CF1: September 1 to 30th
CF2: November 1 to 30th
CF3: January 1 to 31st.
CF4: March 1 to 31st.
Feature Freeze: March 31st
May 16th: Beta
===
I think we should be trying to hit those dates, not re-litigate them.
--
Robert Haas
EnterpriseDB: http://www.enterprisedb.com
The Enterprise PostgreSQL Company
