Re: Bug tracker tool we need
Tom Lane <tgl@sss.pgh.pa.us>
From: Tom Lane <tgl@sss.pgh.pa.us>
To: Magnus Hagander <magnus@hagander.net>
Cc: Robert Haas <robertmhaas@gmail.com>, Jay Levitt <jay.levitt@gmail.com>, Alex <ash@commandprompt.com>, Dimitri Fontaine <dimitri@2ndquadrant.fr>, Alvaro Herrera <alvherre@commandprompt.com>, Peter Eisentraut <peter_e@gmx.net>, Greg Smith <greg@2ndquadrant.com>, Pg Hackers <pgsql-hackers@postgresql.org>
Date: 2012-04-18T05:52:32Z
Lists: pgsql-hackers
Magnus Hagander <magnus@hagander.net> writes: > On Wed, Apr 18, 2012 at 04:30, Tom Lane <tgl@sss.pgh.pa.us> wrote: >> So when I read Andrew's recent suggestion that we use >> Bugzilla, my immediate reaction was "egad, can't we do better?". >> Maybe we can't :-(. > Personally, I'd say we *already* do better than that... Just meditating a little ... one of my big beefs with Bugzilla is that it shows basically a historical record of how a bug was discovered and dealt with. While that surely has, er, historical value, it's not that useful to read when you want to know which bug matches your symptoms, what the possible consequences are, which versions it was fixed in, etc. One particularly nasty point is that (AFAIK) it's impossible to delete or edit incorrect comments, only to add new ones. I wonder whether a better model would be a wiki page per bug, with an editable description and some links to reports, commits, etc. Not but what I hate every wiki I've ever used too ... but at least they let you fix the information when it's wrong or unhelpful. regards, tom lane