From: Chris Browne <cbbrowne@acm.org>
Subject: Re: Feature freeze progress report
Date: Wed, 02 May 2007 13:27:00 +0000
Organization: cbbrowne Computing Inc
Lines: 21
Message-ID: <60k5vrpd97.fsf@dba2.int.libertyrms.com>
References: <200705012309.l41N9O908241@momjian.us>
	<200705012151.51915.josh@agliodbs.com>
	<5678.1178083185@sss.pgh.pa.us> <4638851C.9060308@dunslane.net>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
User-Agent: Gnus/5.1007 (Gnus v5.10.7) XEmacs/21.4.20 (linux)
Cancel-Lock: sha1:ZiRJ/aflL726jcCfq76TxuqTKfA=
To: pgsql-hackers@postgresql.org

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"?