Confirmed users, Bureaucrats and Sysops emeriti
722
edits
Firefox/IterativeDevelopment: Difference between revisions
→Backlog Triage
GavinSharp (talk | contribs) |
|||
| Line 55: | Line 55: | ||
<p> </p> | <p> </p> | ||
===Backlog Triage=== | ===Backlog Triage=== | ||
====Triage Guidelines==== | |||
These guidelines should help determine whether a bug should be included in the Firefox desktop team's backlog. | |||
These are guidelines, not strict rules. Ultimately the decision rests on the judgement of the triage teams, and exceptions are possible. They should however be uncommon. | |||
To be included in the Firefox desktop backlog, a bug should: | |||
* be in an actionable state | |||
** for defects, the problem is ready for engineering or UX: diagnosis, measurement, design, or fixing | |||
** for feature requests or enhancements, it means that there's a clear problem statement or suggestion | |||
* have a difficulty/user-impact ratio low enough that we can reasonably expect to spend time fixing the bug within the next 6 months | |||
** this is a judgement call, obviously, and so the triage teams will need to learn to make these decisions over time | |||
* be within the general area of ownership/responsibility of the Firefox team (engineering and UX) | |||
** this means e.g. platform bugs that are outside of our area of expertise/ownership should generally not be added to our backlog | |||
<p> </p> | <p> </p> | ||
'''Triage Backlog:''' [https://bugzilla.mozilla.org/show_bug.cgi?id=981530 View Bugzilla] | '''Triage Backlog:''' [https://bugzilla.mozilla.org/show_bug.cgi?id=981530 View Bugzilla] | ||