Bugzilla workflow thoughts

[braddr at puremagic.com]

In article <e0408v$ba5$1 at digitaldaemon.com>, Walter Bright says...
>
>Don't spend time on this bug, I already have it fixed. -Walter 

Please, anyone working on a bug, be it Walter or one of us out here in the
peanut gallery, be sure to move the state of a bug from NEW to ASSIGNED and make
sure it's assigned to you.

It's helpful to know that someone else is spending time diagnosing a bug so
others can either talk with that person first or divert their attention
elsewhere.

Not that there's a lot of redundant work going on, but there's few enough of
with little enough time that it'd be good to make that time as effective as it
can be.

from Unknown:
> Do we have anyone who is expected to verify bugs?  Typically, from all 
> the bugzilla's I've worked with, bugs are marked fixed and, ideally, 
> verified (or reopened) as such by QA before a release is made.
> 
> Maybe this is too much red tape, but it would seem logical to QA the 
> bugs after releases, at least.  IMHO.

It'd be nice if the original filer could take on that job.  I'll try to do some
as time permits.  That said, for most of the projects I've been a part of,
resolved is pretty much a terminal condition unless someone notices a problem or
disagrees with the resolution and reopens, which is pretty rare.

Later,
Brad