Skip site navigation (1) Skip section navigation (2)

Re: Feature freeze status

From: Gregory Stark <stark(at)enterprisedb(dot)com>
To: "Heikki Linnakangas" <heikki(at)enterprisedb(dot)com>
Cc: <josh(at)agliodbs(dot)com>, <pgsql-hackers(at)postgresql(dot)org>, "Bruce Momjian" <bruce(at)momjian(dot)us>
Subject: Re: Feature freeze status
Date: 2008-04-07 23:34:45
Message-ID: 87myo5fdd6.fsf@oxford.xeocode.com (view raw or flat)
Thread:
Lists: pgsql-hackers
"Heikki Linnakangas" <heikki(at)enterprisedb(dot)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!

In response to

Responses

pgsql-hackers by date

Next:From: Tom LaneDate: 2008-04-08 01:50:52
Subject: Re: Feature freeze status
Previous:From: Andrew DunstanDate: 2008-04-07 22:28:07
Subject: Re: [PATCHES] Integer datetime by default

Privacy Policy | About PostgreSQL
Copyright © 1996-2014 The PostgreSQL Global Development Group