Received: from localhost (maia-5.hub.org [200.46.204.182])
	by postgresql.org (Postfix) with ESMTP id E470A9FB8D9;
	Wed,  2 May 2007 04:34:42 -0300 (ADT)
Received: from postgresql.org ([200.46.204.71])
	by localhost (mx1.hub.org [200.46.204.182]) (amavisd-maia, port 10024)
	with ESMTP id 32870-10; Wed,  2 May 2007 04:34:31 -0300 (ADT)
X-Greylist: from auto-whitelisted by SQLgrey-1.7.5
X-Greylist: from auto-whitelisted by SQLgrey-1.7.5
Received: from svr2.hagander.net (svr2.hagander.net [88.198.128.226])
	by postgresql.org (Postfix) with ESMTP id 5B3B89FB863;
	Wed,  2 May 2007 04:34:39 -0300 (ADT)
Received: by svr2.hagander.net (Postfix, from userid 1000)
	id 6DF21DCC8EA; Wed,  2 May 2007 09:34:38 +0200 (CEST)
Date: Wed, 2 May 2007 09:34:38 +0200
From: Magnus Hagander <magnus@hagander.net>
To: Bruce Momjian <bruce@momjian.us>
Cc: Josh Berkus <josh@agliodbs.com>, pgsql-hackers@postgresql.org,
	Dave Page <dpage@postgresql.org>, Tom Lane <tgl@sss.pgh.pa.us>,
	Heikki Linnakangas <heikki@enterprisedb.com>,
	Simon Riggs <simon@2ndquadrant.com>
Subject: Re: Feature freeze progress report
Message-ID: <20070502073438.GA2495@svr2.hagander.net>
References: <200705010943.19924.josh@agliodbs.com>
	<200705012309.l41N9O908241@momjian.us>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <200705012309.l41N9O908241@momjian.us>
User-Agent: Mutt/1.5.11
X-Virus-Scanned: Maia Mailguard 1.0.1
X-Archive-Number: 200705/89
X-Sequence-Number: 102691

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