Re: PostgreSQL's bug tracker - Mailing list pgsql-general

From Magnus Hagander
Subject Re: PostgreSQL's bug tracker
Date
Msg-id 6BCB9D8A16AC4241919521715F4D8BCE6C7A8D@algol.sollentuna.se
Whole thread Raw
In response to PostgreSQL's bug tracker  (J B <jbwellsiv@gmail.com>)
Responses Re: PostgreSQL's bug tracker  (Tino Wildenhain <tino@wildenhain.de>)
Re: PostgreSQL's bug tracker  (Martijn van Oosterhout <kleptog@svana.org>)
List pgsql-general
> > I have thought about that, however I would at least at some
> level want
> > a blessing. For example, if we did that would we do it with
> pgFoundry
> > bug tracking? Or would we use Trac? Or Bugzilla?
>
> I think the main thing that's killed previous proposals in
> this line is that we could never get a consensus on which bug
> tracker to use.
> Personally I'd be OK with Bugzilla, since I use it at Red Hat
> already, but I know that some hate it violently.
>
> There are also a set of issues involved in integrating any
> such project with the pgsql-bugs list, which in the
> estimation of many of us is not broken and does not need fixing.

Or integrating them with the web. Not sure if any of the "popular
bugtrackers" support that today, or if they all want to "be their own
site" that we'd link to. That'd work, of course, but it'd be nicer to
get something that actually looks like a part of the site. Without too
much work of course ;-)


> Old-timers will recall that we already had one bad experience
> with an early open-source bug tracker, which has left people
> a bit shy of the concept too.  I think a large part of that
> had to do with confusion between the purposes of bug
> *reporting* and bug *tracking*.  A mailing list does very
> well for reporting issues that might be bugs, but not so well
> for tracking the status of acknowledged bugs.

I think having an "open tracker" is definitly bad. It'll end up like a
lot of the sf.net projcets that have it - thousands of open tickets for
things that are not bugs, that nobody has the time to take care of.
Which makes it more or less worthless for tracking, and also makes the
project look really bad (hey, they have thousands of bugs!)

So we'd either want a tracker that is not open for direct submittions
(mail -> pgsql-bugs, and then have somebody move it into the tracker
once it's confirmed. Or some way where submitted issues don't show up in
the bug list until somebody has verified them (but they have to go out
to the list, of course, so ppl know it should be done).

Not sure which of the packages provide that, but I'm sure somebody else
knows.

//Magnus

pgsql-general by date:

Previous
From: Tino Wildenhain
Date:
Subject: Re: PostgreSQL's bug tracker
Next
From: Tino Wildenhain
Date:
Subject: Re: PostgreSQL's bug tracker