On Tue, Apr 17, 2012 at 19:59, Greg Smith <greg@2ndquadrant.com> wrote:
> On 04/17/2012 09:20 AM, Jay Levitt wrote:
> Let's pick a real example from the last week of my life, where having a bug
> tracker would have helped me out. This appears in a log:
>
> ERROR: missing chunk number 0 for toast value 1167375 in pg_toast_2619
>
> What I should be able to do here is search the bug tracker for these words
> and have it spit out an issue that looks like this
I'm snipping the actual usecase, because it's nice and deatailed, but.
I think this cleraly outlines that we need to remember that there are
*two* different patterns that people are trying tosolve with the
bugtracker.
One is the simple "someone reported a bug. track until someone fixes
it to make sure we don't miss it. Possibly even flag who is currently
working on/responsible for this bug".
The other one is for the *outsider* (sorry, Greg, in this scenario you
get to represent an outsider for once). Who comes in and wants to know
if the problem he/she has exists before, if it's fixed, and in which
versions it's fixed in.
There is some overlap, but the general usecase is drastically
different. And we do a decent enough job of the first one today,
partially because we have a few people who are very good at
remembering these things and then finding them in the list archives.
It works. However, we do very bad on the second one, IMHO.
Any tool we'd go for should aim to cover *both* usecases.
--
Magnus Hagander
Me: http://www.hagander.net/
Work: http://www.redpill-linpro.com/
