Date: Wed, 2 May 2007 19:37:14 +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: <20070502173714.GC11219@svr2.hagander.net>
References: <20070502073438.GA2495@svr2.hagander.net>
	<200705021044.l42AiCJ20657@momjian.us>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <200705021044.l42AiCJ20657@momjian.us>
User-Agent: Mutt/1.5.11

On Wed, May 02, 2007 at 06:44:12AM -0400, Bruce Momjian wrote:
> Magnus Hagander wrote:
> > > 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.
> 
> No, my point is that 100% information is already available by looking at
> email archives.

Yes, and hard to find.

>  What we need is a short description of where we are on
> each patch --- that is a manual process, not something that can be
> automated.

Right. But it can be presented in a central way and incrementally updated.


> Tom has posted it --- tell me how we will get such a list in an
> automated manner.

There's no way to get it automated, but you can get it incrementally
updated.

//Magnus