Confirmed users
2,177
edits
Performance/Triage: Difference between revisions
Updated guidelines for new pending-needinfo value of performance impact project flag.
(→Performance triage: update query to not exclude needinfos) |
(Updated guidelines for new pending-needinfo value of performance impact project flag.) |
||
| Line 148: | Line 148: | ||
# Open the [[#Performance triage|first triage query]] to show bugs nominated for triage or in the Core::Performance component without the performance impact project flag set. The bugs are sorted from oldest to newest. For each bug in the list, follow these steps: | # Open the [[#Performance triage|first triage query]] to show bugs nominated for triage or in the Core::Performance component without the performance impact project flag set. The bugs are sorted from oldest to newest. For each bug in the list, follow these steps: | ||
#* Bugs that look like tasks that were filed by members of the Performance team will generally need to be moved to the Core::Performance Engineering component. | #* Bugs that look like tasks that were filed by members of the Performance team will generally need to be moved to the Core::Performance Engineering component. | ||
#* For defects: Determine if the bug is reproducible and actionable. If not, add a needinfo for the reporter asking for more information and move onto the next bug. We have a [[#New bug|template]] that you can modify as needed. | #* For defects: Determine if the bug is reproducible and actionable. If not, add a needinfo for the reporter asking for more information, set the performance impact project flag to pending-needinfo, and then move onto the next bug. We have a [[#New bug|template]] that you can modify as needed. | ||
#* For all bugs (including enhancements): | #* For all bugs (including enhancements): | ||
#** Set the [[#How do I determine the performance impact project flag?|performance impact project flag]]. | #** Set the [[#How do I determine the performance impact project flag?|performance impact project flag]]. | ||
#** Add the appropriate [[#How do I determine the performance keywords?|performance keywords]]. | #** Add the appropriate [[#How do I determine the performance keywords?|performance keywords]]. | ||
#** Move the bug to the correct [[#How do I determine the correct Bugzilla component?|Bugzilla component]]. | #** Move the bug to the correct [[#How do I determine the correct Bugzilla component?|Bugzilla component]]. | ||
# Open the [[#Performance triage (pending needinfo)|second triage query]] to show bugs that | # Open the [[#Performance triage (pending-needinfo)|second triage query]] to show bugs that are waiting further information to determine the performance impact. The bugs are sorted from oldest to newest. For each bug in the list, follow these steps: | ||
#* If the | #* If the performance impact project flag was set to pending-needinfo less than 2 weeks ago, move onto the next bug. | ||
#* If the | #* If the performance impact project flag was set to pending-needinfo more than 2 weeks ago but less than 2 months ago, consider adding a needinfo for either: another reporter of the issue, someone with access to the appropriate platform(s) to attempt to reproduce the issue, or a relevant subject matter expert. | ||
#* If the | #* If the performance impact project flag was set to pending-needinfo more than 2 months ago, close the bug as inactive. You can modify the [[#No response from reporter|inactive bug template]] as needed. | ||
# If time permits, open the [[#Recently opened bugs with performance keywords in the summary|third triage query]] to show recently opened bugs with performance related keywords in the summary. If any of these look like performance bugs, they can either be triaged the same way as bugs in the initial query or they can be [[#Bugzilla|nominated for triage]] in a subsequent meeting. | # If time permits, open the [[#Recently opened bugs with performance keywords in the summary|third triage query]] to show recently opened bugs with performance related keywords in the summary. If any of these look like performance bugs, they can either be triaged the same way as bugs in the initial query or they can be [[#Bugzilla|nominated for triage]] in a subsequent meeting. | ||
| Line 164: | Line 164: | ||
== How do I determine the performance impact project flag? == | == How do I determine the performance impact project flag? == | ||
The [[../Bugzilla#Project Flag|performance impact project flag]] is used to indicate a bug’s relationship to the performance of our products. It can be applied to all bugs, and not only defects. The [[#Triage calculator|triage calculator]] should be used to help determine the most appropriate value for this flag. In addition to setting the performance impact project flag, make sure to use the “Copy Bugzilla Comment” button and paste this as a comment on the bug. | The [[../Bugzilla#Project Flag|performance impact project flag]] is used to indicate a bug’s relationship to the performance of our products. It can be applied to all bugs, and not only defects. The [[#Triage calculator|triage calculator]] should be used to help determine the most appropriate value for this flag. In addition to setting the performance impact project flag, make sure to use the “Copy Bugzilla Comment” button and paste this as a comment on the bug. | ||
If you do not have enough information to set the performance impact project flag, open a needinfo request against an appropriate individual (such as a reporter), and set the performance impact project flag to pending-needinfo. | |||
For more information about what this flag, and it's settings mean see this [https://blog.mozilla.org/performance/2022/11/07/understanding-performance-impact/ blog post]. | For more information about what this flag, and it's settings mean see this [https://blog.mozilla.org/performance/2022/11/07/understanding-performance-impact/ blog post]. | ||