Re: Feature freeze progress report

From: Andrew Dunstan <andrew(at)dunslane(dot)net>
To: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
Cc: Josh Berkus <josh(at)agliodbs(dot)com>, pgsql-hackers(at)postgresql(dot)org
Subject: Re: Feature freeze progress report
Date: 2007-05-02 12:33:32
Message-ID: 4638851C.9060308@dunslane.net
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers pgsql-www

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!

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.

cheers

andrew

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Alvaro Herrera 2007-05-02 13:18:31 Re: strange buildfarm failures
Previous Message Andrew Dunstan 2007-05-02 12:27:00 Re: Feature freeze progress report

Browse pgsql-www by date

  From Date Subject
Next Message Chris Browne 2007-05-02 13:27:00 Re: Feature freeze progress report
Previous Message Bruce Momjian 2007-05-02 12:11:12 Re: Feature freeze progress report