Re: Feature freeze progress report

From: "Andrew Dunstan" <andrew(at)dunslane(dot)net>
To: "Chris Browne" <cbbrowne(at)acm(dot)org>
Cc: pgsql-hackers(at)postgresql(dot)org
Subject: Re: Feature freeze progress report
Date: 2007-05-02 19:59:35
Message-ID: 62073.75.177.135.163.1178135975.squirrel@www.dunslane.net
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers pgsql-www

Chris Browne wrote:
> 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...

I lost interest last time around when it seemed clear to me that there was
not enough traction.

Maybe there is this time around.

The effort Tom mentions above is crucial to success.

cheers

andrew

In response to

Browse pgsql-hackers by date

  From Date Subject
Next Message Magnus Hagander 2007-05-02 20:12:49 Optimization in convert_string_datum?
Previous Message Heikki Linnakangas 2007-05-02 19:58:26 Re: Sequential scans

Browse pgsql-www by date

  From Date Subject
Next Message Dave Page 2007-05-02 20:32:19 Re: Feature freeze progress report
Previous Message Joshua D. Drake 2007-05-02 18:27:24 Re: Feature freeze progress report