Re: Feature freeze progress report - Mailing list pgsql-hackers

From Chris Browne
Subject Re: Feature freeze progress report
Date
Msg-id 60k5vrpd97.fsf@dba2.int.libertyrms.com
Whole thread Raw
In response to Re: Feature freeze progress report  (Bruce Momjian <bruce@momjian.us>)
Responses Re: Feature freeze progress report  ("Andrew Dunstan" <andrew@dunslane.net>)
List pgsql-hackers
andrew@dunslane.net (Andrew Dunstan) writes:
> 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.

Well, Command Prompt set up a Bugzilla instance specifically so people
could track PG bugs.  If only someone took interest and started using
it...
-- 
"cbbrowne","@","linuxfinances.info"
http://cbbrowne.com/info/lisp.html
Do Roman paramedics refer to IV's as "4's"? 


pgsql-hackers by date:

Previous
From: Tom Lane
Date:
Subject: Re: strange buildfarm failures
Next
From: Alvaro Herrera
Date:
Subject: Re: strange buildfarm failures