Performance/Triage: Difference between revisions
Jump to navigation
Jump to search
No edit summary |
|||
| Line 22: | Line 22: | ||
* determine if the bug is a performance issue | * determine if the bug is a performance issue | ||
* assign a priority using the [[../Bugzilla#Project Flag|performance flag]] | * assign a priority using the [[../Bugzilla#Project Flag|performance flag]] | ||
* assign | * assign appropriate [[../Bugzilla#Keywords|keywords]] | ||
* move the bug to the most suitable component | * move the bug to the most suitable component | ||
Revision as of 20:14, 1 March 2022
Resources
- Performance/Bugzilla
- Triage query: https://mzl.la/perf-triage-query
- Priority calculator: https://codepen.io/mstange/pen/eYeWrGr
- Triage rotation: https://mozilla.github.io/perf-triage/
Nomination
To nominate a bug for triage, set the Performance flag in Bugzilla to ?
This can be found by clicking Show Advanced Fields followed by Set bug flags when entering a new bug:
Or by expanding the Tracking section when editing an existing bug:
Triage Process
The goals of the triage process are:
- determine if the bug is a performance issue
- assign a priority using the performance flag
- assign appropriate keywords
- move the bug to the most suitable component
The calculator is a good way to find the right priority.
Sometimes the information isn't enough to make a decision, in that case we can "need info" the reporter asking for more data, for example an export of `about:support` or a performance profile, or simply more information about the steps to reproduce.