Re: CommitFest 2011-01 as of 2011-02-04 - Mailing list pgsql-hackers

From Peter Eisentraut
Subject Re: CommitFest 2011-01 as of 2011-02-04
Date
Msg-id 1297745365.18922.8.camel@vanquo.pezone.net
Whole thread Raw
In response to Re: CommitFest 2011-01 as of 2011-02-04  (Stephen Frost <sfrost@snowman.net>)
Responses Re: CommitFest 2011-01 as of 2011-02-04  (Simon Riggs <simon@2ndQuadrant.com>)
List pgsql-hackers
On mån, 2011-02-14 at 11:49 -0500, Stephen Frost wrote:
> Perhaps a thought for next time would be to offset things a bit.  eg:
> 
> CF 2011-03 (or whatever):
> 2011-02-14: Patches should all be submitted
> 2011-02-14: Reviewers start
> 2011-03-01: Committers start w/ 'Ready for Committer' patches
> 2011-03-14: Patches not marked 'Ready for Committer' get bounced
> 2011-03-31: All patches committed
> 
> I'm not against the 'waiting on author' approach, but I do feel like
> if we're going to continue to have it, we need to spread it out a bit
> more.

I don't think it is realistic to add even more dates and bounds and
guidelines.  People are already widely ignoring the current ones.

If you want to have the ability the bounce things more aggressively, I'd
argue for shorter and more frequent commitfests.  Say, one week per
month.



pgsql-hackers by date:

Previous
From: Peter Eisentraut
Date:
Subject: Re: pl/python do not delete function arguments
Next
From: Tom Lane
Date:
Subject: pg_upgrade seems a tad broken