Re: damage control mode - Mailing list pgsql-hackers

From Magnus Hagander
Subject Re: damage control mode
Date
Msg-id 9837222c1001080105q28b1e834h7959f0911f592829@mail.gmail.com
Whole thread Raw
In response to Re: damage control mode  (Dimitri Fontaine <dfontaine@hi-media.com>)
Responses Re: damage control mode
List pgsql-hackers
On Fri, Jan 8, 2010 at 10:02, Dimitri Fontaine <dfontaine@hi-media.com> wrote:
> David Fetter <david@fetter.org> writes:
>> If we *must* have SR and it's not in by the 15th, let's do another
>> Commitfest rather than jack the people who played by the rules.
>
> If we do add another Commitfest what we do is exactly jacking people who
> played by the rules. Because all those patches that are already part of
> alpha3 have been worked on by people expecting a 4 CF development cycle,
> and adjusted their agenda, and want a mid-year release.
>
> Now, I'll second Greg Smith and Tom here, in that I think we need to run
> the last commitfest as usual, knowing that the outcome of the commitfest
> for any given patch is not "it made it" but "we reviewed it". It's still
> right for the project to bump a patch on resources ground rather than on
> technical merit, at the end of the commitfest.

+1.

> Why we can do it this way is because we're not starving on
> reviewers. We're starving on commiters time. And seeing this:

Well, we're actually somewhat starving on senior reviewers as well.
That can take on things like the index patches, Writable CTE or SR.
We're not starving on reviewers for small-to-medium patches.


-- Magnus HaganderMe: http://www.hagander.net/Work: http://www.redpill-linpro.com/


pgsql-hackers by date:

Previous
From: Fujii Masao
Date:
Subject: Re: ACK from walreceiver to walsender
Next
From: Nikhil Sontakke
Date:
Subject: Re: Why doesn't query_tree_walker examine the intoClause field?