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 19:37:14 +0200
Message-ID: <[email protected]> (raw)
In-Reply-To: <[email protected]>
References: <[email protected]>
	<[email protected]>

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

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