Re: bugs that have not been replied-to on list - Mailing list pgsql-bugs

From Magnus Hagander
Subject Re: bugs that have not been replied-to on list
Date
Msg-id i2g9837222c1004181429t816edafck9a04d8a834325955@mail.gmail.com
Whole thread Raw
In response to Re: bugs that have not been replied-to on list  (Tom Lane <tgl@sss.pgh.pa.us>)
Responses Re: bugs that have not been replied-to on list  (Robert Haas <robertmhaas@gmail.com>)
List pgsql-bugs
On Sun, Apr 18, 2010 at 23:14, Tom Lane <tgl@sss.pgh.pa.us> wrote:
> Jaime Casanova <jcasanov@systemguards.com.ec> writes:
>> On Sun, Apr 18, 2010 at 3:59 PM, Robert Haas <robertmhaas@gmail.com> wro=
te:
>>> On Sun, Apr 18, 2010 at 3:47 PM, Greg Sabino Mullane <greg@turnstep.com=
> wrote:
>>>> Bugzilla is the worst form of bug tracking out there, except for
>>>> all the others.
>>>
>>> One of these days, I am going to write a @$#! bug tracker.
>
>> after seen the commitfest app, i can swear the bug tracker you write
>> should be cool
>
> ... actually, what about minimally modifying the commitfest app to turn
> it into a bug tracker?
>
> We keep complaining that none of the existing trackers would integrate
> well with our workflow. =A0ISTM what we basically need is something that
> would index the pgsql-bugs archives to show what the current open issues
> are. =A0The commitfest app is dang close to that already.

Let's not do that without thinking really careful about  it. The
commitfest app is good at what it does precisely because it's designed
to do just that, and nothing more (or less). Twisting it into doing
other things may make things worse rather than better.

That said, basing something off the same ideas can certainly work.

--=20
 Magnus Hagander
 Me: http://www.hagander.net/
 Work: http://www.redpill-linpro.com/

pgsql-bugs by date:

Previous
From: Tom Lane
Date:
Subject: Re: bugs that have not been replied-to on list
Next
From: John R Pierce
Date:
Subject: Re: bugs that have not been replied-to on list