canmove, Confirmed users, Bureaucrats and Sysops emeriti
4,751
edits
TestEngineering/Performance/Triage Process: Difference between revisions
Jump to navigation
Jump to search
TestEngineering/Performance/Triage Process (view source)
Revision as of 15:04, 24 February 2020
, 24 February 2020Clarify priority for mentored bugs
(Update for monday triage and less often failures) |
(Clarify priority for mentored bugs) |
||
| Line 6: | Line 6: | ||
* If it is not clear how to proceed on the bug, or if further input is necessary from stakeholders, add the whiteboard entry '''[perftest:triage]'''. Those bugs will be discussed in the next [https://docs.google.com/document/d/1SeMijarFsdtm-mrxkIQzV4y1PHcJN72JDPWOlxJ7u-A/edit#heading=h.v37yirv4o0rn triage meeting]. | * If it is not clear how to proceed on the bug, or if further input is necessary from stakeholders, add the whiteboard entry '''[perftest:triage]'''. Those bugs will be discussed in the next [https://docs.google.com/document/d/1SeMijarFsdtm-mrxkIQzV4y1PHcJN72JDPWOlxJ7u-A/edit#heading=h.v37yirv4o0rn triage meeting]. | ||
* Bugs without a priority set should move to P3 by default, which means it will be fixed at some point. Only set P2 if the bug blocks current OKRs. | * Bugs without a priority set should move to P3 by default, which means it will be fixed at some point. Only set P2 if the bug blocks current OKRs. | ||
* Check regularly for mentored bugs, and set needinfo if there wasn’t a reply from the contributor for more than a week. Never set a person as assignee, given that this will be done by Phabricator itself when the initial patch gets submitted. Reset the assignee and set the bug to new if no further response comes in within a week. | * Check regularly for mentored bugs, and set needinfo if there wasn’t a reply from the contributor for more than a week. Never set a person as assignee, given that this will be done by Phabricator itself when the initial patch gets submitted. Reset the assignee and set the bug to new if no further response comes in within a week. Also leave the priority as is and don't change it to P1 if such a bug gets assigned. | ||
* When you start working on a bug, set its priority to P1 and assign yourself. | * When you start working on a bug, set its priority to P1 and assign yourself. | ||
* When you stop working on a bug or when it is blocked by another one, reset the priority to its original value, and unassign yourself. | * When you stop working on a bug or when it is blocked by another one, reset the priority to its original value, and unassign yourself. | ||