| OLD | NEW |
|---|
| 1 The Chrome network team uses a two day bug triage rotation. The main goals are | 1 The Chrome network team uses a two day bug triage rotation. The main goals are |
| 2 to identify and label new network bugs, and investigate network bugs when no | 2 to identify and label new network bugs, and investigate network bugs when no |
| 3 label seems suitable. | 3 label seems suitable. |
| 4 | 4 |
| 5 Responsibilities | 5 Responsibilities |
| 6 | 6 |
| 7 To be done on each rotation. These responsibilities should be tracked, and | 7 To be done on each rotation. These responsibilities should be tracked, and |
| 8 anything left undone at the end of a rotation should be handed off to the next | 8 anything left undone at the end of a rotation should be handed off to the next |
| 9 triager. The downside to passing along bug investigations like this is each new | 9 triager. The downside to passing along bug investigations like this is each new |
| 10 triager has to get back up to speed on bugs the previous triager was | 10 triager has to get back up to speed on bugs the previous triager was |
| 11 investigating. The upside is that triagers don't get stuck investigating issues | 11 investigating. The upside is that triagers don't get stuck investigating issues |
| 12 after their time after their rotation, and it results in a uniform, predictable | 12 after their time after their rotation, and it results in a uniform, predictable |
| 13 two day commitment for all triagers. | 13 two day commitment for all triagers. |
| 14 | 14 |
| 15 Primary Responsibilities: | 15 Primary Responsibilities: |
| 16 * Identify new crashers that are potentially network related. You should check | 16 * Identify new crashers that are potentially network related. You should check |
| 17 the most recent canary, the previous canary (if the most recent less than a | 17 the most recent canary, the previous canary (if the most recent less than a |
| 18 day old), and any of dev/beta/stable that were released in the last couple | 18 day old), and any of dev/beta/stable that were released in the last couple |
| 19 of days, for each platform. File Cr-Internals-Network bugs on the tracker | 19 of days, for each platform. File Cr-Internals-Network bugs on the tracker |
| 20 when new crashers are found. | 20 when new crashers are found. |
| 21 * Identify new network bugs, both on the bug tracker and on the crash server. | 21 * Identify new network bugs, both on the bug tracker and on the crash server. |
| 22 All Unconfirmed issues filed during your triage rotation should be scanned, | 22 All Unconfirmed issues filed during your triage rotation should be scanned, |
| 23 and, for suspected network bugs, a network label assigned. A triager is | 23 and, for suspected network bugs, a network label assigned. A triager is |
| 24 responsible for looking at bugs reported from noon PST / 3:00 pm EST of the | 24 responsible for looking at bugs reported from noon PST / 3:00 pm EST of the |
| 25 last day of the previous triager's rotation until the same time on the last | 25 last day of the previous triager's rotation until the same time on the last |
| 26 day of his rotation. | 26 day of their rotation. |
| 27 * Request data about recent unassigned Cr-Internals-Network bugs from reporters. | 27 * Request data about recent unassigned Cr-Internals-Network bugs from reporters. |
| 28 "Recent" means issues updated in the past week or so. | 28 "Recent" means issues updated in the past week or so. |
| 29 * Investigate each recent (New comment within the past week or so) | 29 * Investigate each recent (New comment within the past week or so) |
| 30 Cr-Internals-Network issue until you can do one of the following: | 30 Cr-Internals-Network issue until you can do one of the following: |
| 31 * Mark it as WontFix (working as intended, obsolete issue) or a duplicate. | 31 * Mark it as WontFix (working as intended, obsolete issue) or a duplicate. |
| 32 * Mark it as a feature request. | 32 * Mark it as a feature request. |
| 33 * Remove the Cr-Internals-Network label, replacing it with at least one more | 33 * Remove the Cr-Internals-Network label, replacing it with at least one more |
| 34 specific network label or non-network label. Promptly adding non-network | 34 specific network label or non-network label. Promptly adding non-network |
| 35 labels when appropriate is important to get new bugs in front of someone | 35 labels when appropriate is important to get new bugs in front of someone |
| 36 familiar with the relevant code, and to remove them from the next triager's | 36 familiar with the relevant code, and to remove them from the next triager's |
| (...skipping 15 matching lines...) Expand all Loading... |
| 52 * Investigate old bugs, prioritizing the most recent. | 52 * Investigate old bugs, prioritizing the most recent. |
| 53 * Close obsolete bugs. | 53 * Close obsolete bugs. |
| 54 | 54 |
| 55 If you've investigated an issue (in code you don't normally work on) to an | 55 If you've investigated an issue (in code you don't normally work on) to an |
| 56 extent that you know how to fix it, and the fix is simple, feel free to take | 56 extent that you know how to fix it, and the fix is simple, feel free to take |
| 57 ownership of the issue and create a patch while on triage duty, but other tasks | 57 ownership of the issue and create a patch while on triage duty, but other tasks |
| 58 should take priority. | 58 should take priority. |
| 59 | 59 |
| 60 See bug-triage-suggested-workflow.txt for suggested workflows. | 60 See bug-triage-suggested-workflow.txt for suggested workflows. |
| 61 See bug-triage-labels.txt for labeling tips for network and non-network bugs. | 61 See bug-triage-labels.txt for labeling tips for network and non-network bugs. |
| OLD | NEW |
|---|
Chromium Code Reviews
Issue 935333002:
Update from https://crrev.com/316786 (Closed)
Base URL: git@github.com:domokit/mojo.git@master