Re: CommitFest 2011-01 as of 2011-02-04

From: Peter Eisentraut <peter_e(at)gmx(dot)net>
To: Stephen Frost <sfrost(at)snowman(dot)net>
Cc: Robert Haas <robertmhaas(at)gmail(dot)com>, pgsql-hackers(at)postgresql(dot)org
Subject: Re: CommitFest 2011-01 as of 2011-02-04
Date: 2011-02-15 04:49:25
Message-ID: 1297745365.18922.8.camel@vanquo.pezone.net
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: 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.

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Tom Lane 2011-02-15 04:53:40 pg_upgrade seems a tad broken
Previous Message Peter Eisentraut 2011-02-15 04:39:00 Re: pl/python do not delete function arguments