ReleaseEngineering/Bugzilla/Triage
Guiding principles for releng bug triage
The RelEng team keeps bugs in three general buckets:
- untriaged: new bugs that are not yet assigned;
- triaged: bugs assigned to RelEng team members; and,
- future: bugs moved to the Release Engineering:Future component (see below).
Individual team members handle their own bugs in different ways. Most team members will switch bugs from NEW to ASSIGNED when they begin working on them. Some may even set the Priority flag. If they do use the Priority field, the Priority levels have these generally accepted meanings:
- P1: blocker bug, other bugs are on hold until this is fixed;
- P2: In progress;
- P3: Next up, planning to work on it within 2 weeks; and,
- P4-P5: non-critical work
My bug got classified to Release Engineering:Future. What does that mean?
Currently, the "Future" component is described in Bugzilla as "For longer term projects that have been agreed should be done, but have no immediate plans to so. These are not be part of the regular recurring triage. Advanced planning and placeholder goals for next quarter also go here."
This is pretty accurate, but what does it actually mean:
- Triaged bugs with no immediate owners go here.
- Sadly, most enhancement bugs end up here unless they will make the core release process better, more streamlined, etc..
- Bugs that are blocked on longer term projects in other groups go here until there is something for RelEng to do.
- Advanced planning and placeholder goals for next quarter (or later) also go here. That's pretty self-explanatory.