public inbox for [email protected]  

help / color / mirror / Atom feed

From: Bruce Momjian <[email protected]>
To: Andrew Dunstan <[email protected]>
Cc: Dave Page <[email protected]>
Cc: Heikki Linnakangas <[email protected]>
Cc: Simon Riggs <[email protected]>
Cc: PostgreSQL-development <[email protected]>
Subject: Re: Feature freeze progress report
Date: Mon, 30 Apr 2007 07:28:51 -0400 (EDT)
Message-ID: <[email protected]> (raw)
In-Reply-To: <[email protected]>

Andrew Dunstan wrote:
> 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.

This is what already happens, and if it doesn't happen sometimes, it is
just because people are too busy.  Making arbitrary deadlines isn't
going to help, partly because we have little control over our community.

-- 
  Bruce Momjian  <[email protected]>          http://momjian.us
  EnterpriseDB                               http://www.enterprisedb.com

  + If your life is a hard drive, Christ can be your backup. +

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