| OLD | NEW |
|---|
| 1 # Chrome Network Bug Triage | 1 # Chrome Network Bug Triage |
| 2 | 2 |
| 3 The Chrome network team uses a two day bug triage rotation. The main goals are | 3 The Chrome network team uses a two day bug triage rotation. The main goals are |
| 4 to identify and label new network bugs, and investigate network bugs when no | 4 to identify and label new network bugs, and investigate network bugs when no |
| 5 label seems suitable. | 5 label seems suitable. |
| 6 | 6 |
| 7 ## Responsibilities | 7 ## Responsibilities |
| 8 | 8 |
| 9 ### Required: | 9 ### Required: |
| 10 * Identify new crashers | 10 * Identify new crashers |
| 11 * Identify new network issues. | 11 * Identify new network issues. |
| 12 * Request data about recent Cr-Internals-Network issue. | 12 * Request data about recent Cr-Internals-Network issue. |
| 13 * Investigate each recent Cr-Internals-Network issue. | 13 * Investigate each recent Cr-Internals-Network issue. |
| 14 * Monitor UMA histograms and gasper alerts. | 14 * Monitor UMA histograms and Chirp/Gasper alerts. |
| 15 | 15 |
| 16 ### Best effort: | 16 ### Best effort: |
| 17 * Investigate unowned and owned-but-forgotten net/ crashers | 17 * Investigate unowned and owned-but-forgotten net/ crashers |
| 18 * Investigate old bugs | 18 * Investigate old bugs |
| 19 * Close obsolete bugs. | 19 * Close obsolete bugs. |
| 20 | 20 |
| 21 All of the above is to be done on each rotation. These responsibilities should | 21 All of the above is to be done on each rotation. These responsibilities should |
| 22 be tracked, and anything left undone at the end of a rotation should be handed | 22 be tracked, and anything left undone at the end of a rotation should be handed |
| 23 off to the next triager. The downside to passing along bug investigations like | 23 off to the next triager. The downside to passing along bug investigations like |
| 24 this is each new triager has to get back up to speed on bugs the previous | 24 this is each new triager has to get back up to speed on bugs the previous |
| (...skipping 35 matching lines...) Expand 10 before | Expand all | Expand 10 after Loading... |
| 60 lot of bugs incorrectly end up with the network label. | 60 lot of bugs incorrectly end up with the network label. |
| 61 | 61 |
| 62 * The issue is assigned to an appropriate owner. | 62 * The issue is assigned to an appropriate owner. |
| 63 | 63 |
| 64 * If there is no more specific label for a bug, it should be investigated | 64 * If there is no more specific label for a bug, it should be investigated |
| 65 until we have a good understanding of the cause of the problem, and some | 65 until we have a good understanding of the cause of the problem, and some |
| 66 idea how it should be fixed, at which point its status should be set to | 66 idea how it should be fixed, at which point its status should be set to |
| 67 Available. Future triagers should ignore bugs with this status, unless | 67 Available. Future triagers should ignore bugs with this status, unless |
| 68 investigating stale bugs. | 68 investigating stale bugs. |
| 69 | 69 |
| 70 * Monitor UMA histograms and gasper alerts. | 70 * Monitor UMA histograms and Chirp/Gasper alerts. |
| 71 | 71 |
| 72 * For each Gasper alert that fires, the triager should determine if the | 72 * For each Chirp and Gasper alert that fires, the triager should determine |
| 73 alert is real (not due to noise), and file a bug with the appropriate | 73 if the alert is real (not due to noise), and file a bug with the |
| 74 label if so. Note that if no label more specific than | 74 appropriate label if so. Note that if no label more specific than |
| 75 Cr-Internals-Network is appropriate, the responsibility remains with the | 75 Cr-Internals-Network is appropriate, the responsibility remains with the |
| 76 triager to continue investigating the bug, as above. | 76 triager to continue investigating the bug, as above. |
| 77 | 77 |
| 78 ### Best Effort (As you have time): | 78 ### Best Effort (As you have time): |
| 79 | 79 |
| 80 * Investigate unowned and owned but forgotten net/ crashers that are still | 80 * Investigate unowned and owned but forgotten net/ crashers that are still |
| 81 occurring (As indicated by | 81 occurring (As indicated by |
| 82 [go/chromecrash](https://goto.google.com/chromecrash)), prioritizing frequent | 82 [go/chromecrash](https://goto.google.com/chromecrash)), prioritizing frequent |
| 83 and long standing crashers. | 83 and long standing crashers. |
| 84 | 84 |
| 85 * Investigate old bugs, prioritizing the most recent. | 85 * Investigate old bugs, prioritizing the most recent. |
| 86 | 86 |
| 87 * Close obsolete bugs. | 87 * Close obsolete bugs. |
| 88 | 88 |
| 89 If you've investigated an issue (in code you don't normally work on) to an | 89 If you've investigated an issue (in code you don't normally work on) to an |
| 90 extent that you know how to fix it, and the fix is simple, feel free to take | 90 extent that you know how to fix it, and the fix is simple, feel free to take |
| 91 ownership of the issue and create a patch while on triage duty, but other tasks | 91 ownership of the issue and create a patch while on triage duty, but other tasks |
| 92 should take priority. | 92 should take priority. |
| 93 | 93 |
| 94 See [bug-triage-suggested-workflow.md](bug-triage-suggested-workflow.md) for | 94 See [bug-triage-suggested-workflow.md](bug-triage-suggested-workflow.md) for |
| 95 suggested workflows. | 95 suggested workflows. |
| 96 | 96 |
| 97 See [bug-triage-labels.md](bug-triage-labels.md) for labeling tips for network | 97 See [bug-triage-labels.md](bug-triage-labels.md) for labeling tips for network |
| 98 and non-network bugs. | 98 and non-network bugs. |
| OLD | NEW |
|---|
Chromium Code Reviews
Issue 1410883003:
Update triage documents with Chirp. (Closed)
Base URL: https://chromium.googlesource.com/chromium/src.git@master