Re: No Issue Tracker - Say it Ain't So! - Mailing list pgsql-hackers
From | Robert Haas |
---|---|
Subject | Re: No Issue Tracker - Say it Ain't So! |
Date | |
Msg-id | CA+TgmobcvdUQ-JGbwZ3mnTz-0u3azdz48=iK1m6_PAJ7iq0hrA@mail.gmail.com Whole thread Raw |
In response to | Re: No Issue Tracker - Say it Ain't So! (Merlin Moncure <mmoncure@gmail.com>) |
Responses |
Re: No Issue Tracker - Say it Ain't So!
(Magnus Hagander <magnus@hagander.net>)
Re: No Issue Tracker - Say it Ain't So! (Tom Lane <tgl@sss.pgh.pa.us>) Re: No Issue Tracker - Say it Ain't So! (Andrew Dunstan <andrew@dunslane.net>) |
List | pgsql-hackers |
On Wed, Sep 30, 2015 at 10:44 AM, Merlin Moncure <mmoncure@gmail.com> wrote: > I'm not trolling in any way. I'm just challenging you to back up your > blanket assertions with evidence. For example, you're assertion that > mailing lists are insufficient is simply stated and expected to be > taken on faith: *How* is it insufficient and *what* do things like in > the new world? Be specific: glossing over these details doesn't > really accomplish anything and avoids the careful examination that may > suggest small tweaks to the current processes that could get similar > results with a lot less effort. In this entire massive thread, so far > only Josh has come up with what I'd consider to be actionable problem > cases. I think that the mailing list is pretty much just as good as a bug tracker would be for finding the discussion about some particular bug. I mean, our web site has all the mails from the email thread, and that's where the discussion is, and if that discussion were in a bug tracker it wouldn't have any more information than what is on the email thread. The email thread also usually contains a message indicating whether a fix was committed. Where the mailing list is less adequate is: - If you want to see a list of all the bugs by status, you have to review every thread individually. It would be useful to have a way to filter out the bug reports that turn out not to be really bugs vs. the ones that are real bugs which have been fixed vs. the ones that are real bugs that have not been fixed. Associating status with each bug number would make this easier. - Bug numbers are sometimes preserved in commit messages, but they never make it into release notes. This actually seems like something we could improve pretty easily and without a lot of extra work (and also without a bug tracker). If every committer makes a practice of putting the bug number into the commit message, and the people who write the release notes then transcribe the information there, I bet that would be pretty useful to a whole lotta people. -- Robert Haas EnterpriseDB: http://www.enterprisedb.com The Enterprise PostgreSQL Company
pgsql-hackers by date: