Tom Lane wrote:
Jaime Casanova <jcasa...@systemguards.com.ec> writes:
On Sun, Apr 18, 2010 at 3:59 PM, Robert Haas <robertmh...@gmail.com> wrote:
On Sun, Apr 18, 2010 at 3:47 PM, Greg Sabino Mullane <g...@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. ISTM what we basically need is something that
would index the pgsql-bugs archives to show what the current open issues
are. The commitfest app is dang close to that already.
hmm - isn't that basically the implementation I proposed upthread?
As in have a (hyptothetical) tracker being subscribed to -bugs (and
maybe the other lists in the future as well) so the workflow would look
like this:
1a. if somebody submits a request through the webform the tracker
assigns an id and can automatically track all responses on the list
1b. if somebody submits directly to -bugs we could either have the
tracker automatically create an id and track it or we could have a
trivial interface to take a message-id and import on demand
2a. we can simply have the tracker export a dashboard status of:
*) stuff that had no reply too (which is one of the open questions)
*) if a commit has the bug id we could have it autoclose/autotrack that
as well
2b. for the case of "not a bug"/"added to TODO"/"works as
intended"/"pgadmin"/"JDBC" - we would either have to do a trival web
interface to claim so or people could send status updates inline in the
mail(at least the BZ emailinterface can take commands like "@close
NOTABUG" or whatever)
2c. if a bug gets a reply but will never result in a solution per 2a or
2b we could add other dashboard as in "bug replied but no conclusion yet"
Implementing this on our own (if that is about the workflow we want) is
probably not even a lot of work, but we could also use an existing
solution just as the backend engine and do the frontends ourselfs.
Stefan
--
Sent via pgsql-bugs mailing list (pgsql-bugs@postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-bugs
