public inbox for [email protected]  

help / color / mirror / Atom feed

From: Andrew Dunstan <[email protected]>
To: Dave Page <[email protected]>
Cc: Heikki Linnakangas <[email protected]>
Cc: Simon Riggs <[email protected]>
Cc: Bruce Momjian <[email protected]>
Cc: PostgreSQL-development <[email protected]>
Subject: Re: Feature freeze progress report
Date: Sun, 29 Apr 2007 19:38:21 -0400
Message-ID: <[email protected]> (raw)
In-Reply-To: <[email protected]>
References: <[email protected]>
	<[email protected]>
	<[email protected]>
	<[email protected]>



Dave Page wrote:
>
>> But I don't like the idea of making a release out of it. Who would 
>> use such a release? No one in production. Making a release comes with 
>> a cost, even if it's just a dev release.
>
> Agreed. That would have the opposite effect of what should happen.
>
> I like the idea of having a sync point mid cycle, however, what I'd 
> like to see even more is an improved system in which we put less 
> pressure on the few committers we have, and give them more freedom to 
> commit patches they may not understand fully themselves by having an 
> improved community review and feedback process to give the patches the 
> approval they need. Doing so might allow us to keep the queue of a 
> more or less fixed, short length throughout the cycle. There would be 
> a few advantages to this:
>
>

I don't think we need a sync point. I think we need to get better at 
setting expectations and at managing the patch queue so that it gets 
drained better all the time. Nothing can be more frustrating for patch 
authors than to have patches in the queue for a very long time. They 
bitrot, and we sometime end up throwing curly questions at authors long 
after the issues are hot in their minds. I'd like to see us set 
ourselves some targets for handling patches. Something like: patches 
held over from feature freeze from the previous release will be reviewed 
within two months of the tree re-opening, and all other patches will be 
reviewed within one month of being submitted. That implies that one 
month after feature freeze the tree will only be open for bug fixes. Any 
patches unapplied at that time would be held over. Maybe that would give 
pgAdmin and friends enough head room to catch up.

cheers

andrew

view thread (98+ messages)  latest in thread

reply

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Reply to all the recipients using the --to and --cc options:
  reply via email

  To: [email protected]
  Cc: [email protected], [email protected], [email protected], [email protected], [email protected], [email protected]
  Subject: Re: Feature freeze progress report
  In-Reply-To: <[email protected]>

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

This inbox is served by agora; see mirroring instructions
for how to clone and mirror all data and code used for this inbox