On Sun, Apr 18, 2010 at 5:29 PM, Magnus Hagander <magnus@hagander.net> wrot=
e:
> 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> wr=
ote:
>>>> On Sun, Apr 18, 2010 at 3:47 PM, Greg Sabino Mullane <greg@turnstep.co=
m> 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 =A0it. 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.
I don't think the code is terribly hard to write no matter how we do
it, and if that means I have to write it, oh well. What is
frustrating about the current process is that ~5% of the bugs don't
get a response. How are we going to fix that problem?
...Robert
