Re: Feature freeze status - Mailing list pgsql-hackers

From Gregory Stark
Subject Re: Feature freeze status
Date
Msg-id 87myo5fdd6.fsf@oxford.xeocode.com
Whole thread Raw
In response to Re: Feature freeze status  (Heikki Linnakangas <heikki@enterprisedb.com>)
Responses Re: Feature freeze status  (Tom Lane <tgl@sss.pgh.pa.us>)
List pgsql-hackers
"Heikki Linnakangas" <heikki@enterprisedb.com> writes:

> Josh Berkus wrote:
>> Maybe we should make the next commit-fest June 1 to give people some time
>> off?  And some time to improve the tools?
>
> I would rather do the commit fests often, to keep the patch queue and the
> commit fests short.

Just throwing out a crazy idea. What if we had a commitfest as scheduled at
the start of May but made it a Tom-free commitfest. Specifically to try to
organize a larger work-force rather than to leave it all on Tom's shoulders.
Not that your efforts aren't appreciated but surely you wouldn't mind a break?

I'm thinking we should have a column in the commitfest info "reviewer" and
specifically assign all the patches to someone, preferably distributed over as
wide a list as possible. 

--  Gregory Stark EnterpriseDB          http://www.enterprisedb.com Ask me about EnterpriseDB's PostGIS support!


pgsql-hackers by date:

Previous
From: Andrew Dunstan
Date:
Subject: Re: [PATCHES] Integer datetime by default
Next
From: Tom Lane
Date:
Subject: Re: Feature freeze status