I've noticed from time to time that bugs get left in "bad" states--instead of being set to "assigned" when someone can reproduce a reporter's bug, the bug is set to "verified", as so forth--so I tried to put together this guide based on my observations of how Patrick and Ed have run Bugzilla and manage bugs (so corrections welcome, as always ) so we can all refer to it, and there's a easy source of "received knowledge" for anyone else who wants to start helping with bug triage in the future....
There's an attempt at a diagram, too, for the visual learners--but JKT is really the master of OmniGraffle, not me
The life-cycle stuff probably should end up on its own page to make the page not so long and whatnot, but right now the draft Bugzilla Guide has all the bugzilla-related stuff all in one place
Smokey _________________ "[...] whether the duck drinks hot chocolate or coffee is irrelevant." -- ovvldc and sardisson in the NeoWiki
Joined: May 25, 2003 Posts: 4752 Location: Santa Barbara, CA
Posted: Thu Oct 13, 2005 7:50 am Post subject:
That's actually a really nice thing to have. We have problems with trying to track down procedures or practices for the changes to a state over a bug's lifetime in my real job, much less here Thanks for the great writeup!
(sorry, practicing my 1337 speek. well, actually i am practicing to make fun of leet speek, because, well, it is funny. besides, we all know w3rd is the only word with a number in it.)
that's great man, thanks again for all the work you do on the wiki.
You cannot post new topics in this forum You cannot reply to topics in this forum You cannot edit your posts in this forum You cannot delete your posts in this forum You cannot vote in polls in this forum You cannot attach files in this forum You cannot download files in this forum