Performance/Bugzilla: Difference between revisions
Jump to navigation
Jump to search
(→Project Flag: Added expectations for resolution of prioritised performance bugs.) |
|||
Line 10: | Line 10: | ||
= Project Flag = | = Project Flag = | ||
We have a '''Performance''' project flag used for triage nomination and prioritisation. Anyone can nominate bugs for triage, but only members of the [[#Groups|perf-triage-team group]] can prioritise or mark bugs as unrelated to performance. | We have a '''Performance''' project flag used for triage nomination and prioritisation. Anyone can (re)nominate bugs for triage, but only members of the [[#Groups|perf-triage-team group]] can prioritise or mark bugs as unrelated to performance. | ||
{| class="wikitable" | |||
|- | |||
! Value !! Description | |||
|- | |||
| <code>[https://bugzilla.mozilla.org/buglist.cgi?f1=cf_performance&o1=equals&v1=%3F&resolution=---&query_format=advanced ?]</code> || Add bug to triage queue. | |||
|- | |||
| <code>[https://bugzilla.mozilla.org/buglist.cgi?f1=cf_performance&o1=equals&v1=-&resolution=---&query_format=advanced -]</code> || Bug is not related to performance. | |||
|- | |||
| <code>[https://bugzilla.mozilla.org/buglist.cgi?f1=cf_performance&o1=equals&v1=P1&resolution=---&query_format=advanced P1]</code> || Bug has a severe impact on the product quality and experience. These bugs should ideally be resolved within 3-6 months. | |||
|- | |||
| <code>[https://bugzilla.mozilla.org/buglist.cgi?f1=cf_performance&o1=equals&v1=P2&resolution=---&query_format=advanced P2]</code> || Bug has a noticable impact for a number of users. These bugs should ideally be resolved within 6-12 months. | |||
|- | |||
| <code>[https://bugzilla.mozilla.org/buglist.cgi?f1=cf_performance&o1=equals&v1=P3&resolution=---&query_format=advanced P3]</code> || Bug has a noticable performance impact but affects a group of users small enough, or the impact is low enough that it should be resolved in accordance with other priorities. | |||
|} | |||
= Keywords = | = Keywords = |
Revision as of 10:28, 28 June 2022
Workflows
Queries
Reports
Project Flag
We have a Performance project flag used for triage nomination and prioritisation. Anyone can (re)nominate bugs for triage, but only members of the perf-triage-team group can prioritise or mark bugs as unrelated to performance.
Value | Description |
---|---|
? |
Add bug to triage queue. |
- |
Bug is not related to performance. |
P1 |
Bug has a severe impact on the product quality and experience. These bugs should ideally be resolved within 3-6 months. |
P2 |
Bug has a noticable impact for a number of users. These bugs should ideally be resolved within 6-12 months. |
P3 |
Bug has a noticable performance impact but affects a group of users small enough, or the impact is low enough that it should be resolved in accordance with other priorities. |
Keywords
- perf A bug that affects speed or responsiveness. (For memory use issues, use "memory-footprint" or "memory-leak" instead.)
- perf-alert Associated with a performance alert.
- perf:responsiveness The issue affects the promptness of the browser’s response to user input.
- perf:resource-use The issue affects resource use excessively: cpu, gpu, ram, disk access, power, etc.
- perf:pageload The issue affects the initial loading of websites.
- perf:frontend The issue affects the browser front-end (i.e. the Firefox UI.)
- perf:animation The issue affects the smoothness of animations.
- perf:startup The issue affects application startup.