Performance/Bugzilla: Difference between revisions
Jump to navigation
Jump to search
(→Project Flag: Added expectations for resolution of prioritised performance bugs.) |
|||
| Line 8: | Line 8: | ||
* [https://bugzilla.mozilla.org/report.cgi?x_axis_field=cf_performance&y_axis_field=component&query_format=report-table&resolution=---&j_top=AND&f1=cf_performance&o1=isnotempty&v1=&f2=cf_performance&o2=nowordssubstr&v2=-%2C%3F&format=table&action=wrap Performance × Component] | * [https://bugzilla.mozilla.org/report.cgi?x_axis_field=cf_performance&y_axis_field=component&query_format=report-table&resolution=---&j_top=AND&f1=cf_performance&o1=isnotempty&v1=&f2=cf_performance&o2=nowordssubstr&v2=-%2C%3F&format=table&action=wrap Performance × Component] | ||
* [https://bugzilla.mozilla.org/report.cgi?x_axis_field=cf_performance&y_axis_field=priority&query_format=report-table&resolution=---&j_top=AND&f1=cf_performance&o1=isnotempty&v1=&f2=cf_performance&o2=nowordssubstr&v2=-%2C%3F&format=table&action=wrap Performance × Priority] | * [https://bugzilla.mozilla.org/report.cgi?x_axis_field=cf_performance&y_axis_field=priority&query_format=report-table&resolution=---&j_top=AND&f1=cf_performance&o1=isnotempty&v1=&f2=cf_performance&o2=nowordssubstr&v2=-%2C%3F&format=table&action=wrap Performance × Priority] | ||
* [https://bugzilla.mozilla.org/report.cgi?x_axis_field=cf_performance&y_axis_field=bug_severity&query_format=report-table&resolution=---&j_top=AND&f1=cf_performance&o1=isnotempty&v1=&f2=cf_performance&o2=nowordssubstr&v2=-%2C%3F&format=table&action=wrap Performance × Severity] | |||
= Project Flag = | = Project Flag = | ||
Revision as of 11:07, 6 July 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.