A Modest Proposal
There’s been considerable discussion in various places about the auto-resolution of UNCO bugs, and the longstanding desire to have a READY state, with arguments on both sides as to whether the local hack for Bugzilla is worth the effort. To quote, er, someone: “Bugzilla was created to serve the needs of mozilla.org. We need to make that it continues to do so.” These changes would involve local hacks, some of which I’m sure could be lifted from Red Hat’s Bugzilla code or other places.
- Provide a means to get more people involved on the ground level of bug triage by making it easier to do useful things. This solution is threefold, starting with simplifying the initial process to confirming that the bug is reproducable and not an obvious dupe, making canconfirm easier to get and giving it the additional ability to mark WFM or DUP, and granting that priv far more widely.
- Free up more experienced and knowledgable QA people to work on a smaller set of bugs and drive bugs into a fixable state.
- Help developers by creating a pool of bugs that are ready to be fixed, with appropriate testcases/design specs in place.
This requires workflow and thus code-level changes to bugzilla. This is a scary thought for some, but we need to be willing to let mozilla.org’s needs drive Bugzilla work, at least in part. One thing is that canconfirm needs to be able to mark bugs as DUPLICATE and WORKSFORME.
Thanks to help from Mike Beltzner, master of the flowchart, and feedback from a few others, I’ve put together a modified workflow for dealing with bugs in such a way that we can achieve the desired outcomes. This mitigates the need for periodic expiry, but I think we may still want to expire bugs after a few months if still unconfirmed and abandoned.
Please check this out, and comment here for now, and we can wiki up the results.