Re: Feature freeze progress report

From: Chris Browne <cbbrowne(at)acm(dot)org>
To: pgsql-hackers(at)postgresql(dot)org
Subject: Re: Feature freeze progress report
Date: 2007-05-02 13:27:00
Message-ID: 60k5vrpd97.fsf@dba2.int.libertyrms.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers pgsql-www

andrew(at)dunslane(dot)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"?

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Alvaro Herrera 2007-05-02 13:28:29 Re: Feature freeze progress report
Previous Message Heikki Linnakangas 2007-05-02 13:26:39 Sequential scans

Browse pgsql-www by date

  From Date Subject
Next Message Alvaro Herrera 2007-05-02 13:28:29 Re: Feature freeze progress report
Previous Message Andrew Dunstan 2007-05-02 12:33:32 Re: Feature freeze progress report