96
edits
Performance/Triage: Difference between revisions
→How do I run a triage meeting?: Added info about what we should do with bugs that look like tasks.
No edit summary |
(→How do I run a triage meeting?: Added info about what we should do with bugs that look like tasks.) |
||
| Line 169: | Line 169: | ||
# Ask if others would prefer you to share your screen. This can be especially helpful for those new to triage. | # Ask if others would prefer you to share your screen. This can be especially helpful for those new to triage. | ||
# 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. | |||
#* 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 and 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): | ||