public inbox for [email protected]  

help / color / mirror / Atom feed

From: Alvaro Herrera <[email protected]>
To: Andrew Dunstan <[email protected]>
Cc: Tom Lane <[email protected]>
Cc: Josh Berkus <[email protected]>
Cc: [email protected]
Subject: Re: Feature freeze progress report
Date: Wed, 2 May 2007 09:28:29 -0400
Message-ID: <[email protected]> (raw)
In-Reply-To: <[email protected]>
References: <[email protected]>
	<[email protected]>
	<[email protected]>
	<[email protected]>

Andrew Dunstan wrote:
> 
> 
> Tom Lane wrote:
> >So in a roundabout way we come back
> >to the idea that we need a bug tracker (NOT a patch tracker), plus
> >people putting in the effort to make sure it stays a valid source
> >of up-to-date info.  Without the latter it won't really be useful.
> 
> Hallelujah Brother!

Amen

> BTW, a bug tracker can be used as a patch tracker, although the reverse 
> isn't true. For example, the BZ people use BZ that way, in fact - most 
> patches arrive as attachments to bugs. And trackers can be used just as 
> well for tracking features as well as bugs.

The pidgin (previously known as Gaim) guys also use it that way.  They
add a bug for each thing they want to change, even new features, and
track the patches in there.  Then they have a list of issues that should
be solved for each release, so it's easy to see which ones are still
missing using their Trac interface.

http://developer.pidgin.im/roadmap

So the status email that Tom sent yesterday would be a very simple thing
to generate, just looking at the "bugs to fix" page.

I'm not saying we should use Trac, mainly because I hate how it
(doesn't) interact with email.  But it does say that a bug tracker can
be useful to us.

-- 
Alvaro Herrera                                http://www.CommandPrompt.com/
The PostgreSQL Company - Command Prompt, Inc.

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