public inbox for [email protected]  

help / color / mirror / Atom feed

From: Magnus Hagander <[email protected]>
To: Bruce Momjian <[email protected]>
Cc: Josh Berkus <[email protected]>
Cc: [email protected]
Cc: Dave Page <[email protected]>
Cc: Tom Lane <[email protected]>
Cc: Heikki Linnakangas <[email protected]>
Cc: Simon Riggs <[email protected]>
Subject: Re: Feature freeze progress report
Date: Wed, 2 May 2007 09:34:38 +0200
Message-ID: <[email protected]> (raw)
In-Reply-To: <[email protected]>
References: <[email protected]>
	<[email protected]>

On Tue, May 01, 2007 at 07:09:24PM -0400, Bruce Momjian wrote:
> > The current patch-queue process is failing to scale with the project: every 
> > release it gets to be more work for you & Tom to integrate the patches.  We 
> > need to think of new approaches to make the review process scale.  As a 
> > pointed example, you're about to go on tour for 2 weeks and patch review will 
> > stall while you're gone.  That's not sustainable.
> 
> I am traveling --- I left on Friday.  I am in Sydney now.
> 
> As far as scaling, patch information isn't our problem right now.  If
> someone wants to help we can give them up-to-date information on exactly
> how to deal with the patch.  It is people doing the work that is the
> bottleneck.

<snip>

> As an example, how is patch information going to help us review HOT or
> group-item-index?  There is frankly more information about these in the
> archives than someone could reasonable read.  What someone needs is a
> summary of where we are now on the patches, and lots of time.
> 
> FYI, Tom, Heikki, I need one of you to post the list of patches and
> where we think we are on each one, even if the list is imperfect.

I think you just contradicted yourself. Information isn ot the problem, but
you need more information...

I think this is a fairly clear indication that we do need a better way to
track this information.

//Magnus

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], [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