| 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, in rough order of priority: | 9 ### Required, in rough order of priority: |
| 10 * Identify new network bugs on the tracker. | 10 * Identify new network bugs on the tracker. |
| (...skipping 73 matching lines...) Expand 10 before | Expand all | Expand 10 after Loading... |
| 84 | 84 |
| 85 * The issue is assigned to an appropriate owner, and make sure to mark it | 85 * The issue is assigned to an appropriate owner, and make sure to mark it |
| 86 as "assigned" so the next triager doesn't run into it. | 86 as "assigned" so the next triager doesn't run into it. |
| 87 | 87 |
| 88 * If there is no more specific component for a bug, it should be | 88 * If there is no more specific component for a bug, it should be |
| 89 investigated by the triager until we have a good understanding of the | 89 investigated by the triager until we have a good understanding of the |
| 90 cause of the problem, and some idea how it should be fixed, at which point | 90 cause of the problem, and some idea how it should be fixed, at which point |
| 91 its status should be set to Available. Future triagers should ignore bugs | 91 its status should be set to Available. Future triagers should ignore bugs |
| 92 with this status, unless investigating stale bugs. | 92 with this status, unless investigating stale bugs. |
| 93 | 93 |
| 94 * Follow up on [Needs-Feedback issues for all components owned by the network st
ack team](https://bugs.chromium.org/p/chromium/issues/list?can=2&q=component%3AI
nternals%3ENetwork%2CUI%3EBrowser%3EDownloads+-component%3AInternals%3ENetwork%3
EDataProxy+-component%3AInternals%3ENetwork%3EDataUse+-component%3AInternals%3EN
etwork%3EVPN+Needs%3DFeedback&sort=-modified). | 94 * Follow up on [Needs-Feedback issues for all components owned by the network st
ack team](https://bugs.chromium.org/p/chromium/issues/list?q=component%3AInterna
ls%3ENetwork+-component%3AInternals%3ENetwork%3EDataProxy+-component%3AInternals
%3ENetwork%3EDataUse+-component%3AInternals%3ENetwork%3EVPN+Needs%3DFeedback&sor
t=-modified). |
| 95 | 95 |
| 96 * Remove label once feedback is provided. Continue to investigate, if | 96 * Remove label once feedback is provided. Continue to investigate, if |
| 97 the previous section applies. | 97 the previous section applies. |
| 98 | 98 |
| 99 * If the Needs-Feedback label has been present for one week, ping the | 99 * If the Needs-Feedback label has been present for one week, ping the |
| 100 reporter. | 100 reporter. |
| 101 | 101 |
| 102 * Archive after two weeks with no feedback, telling users to file a new | 102 * Archive after two weeks with no feedback, telling users to file a new |
| 103 bug if they still have the issue, with the requested information, unless | 103 bug if they still have the issue, with the requested information, unless |
| 104 the reporter indicates they'll provide data when they can. In that case, | 104 the reporter indicates they'll provide data when they can. In that case, |
| (...skipping 26 matching lines...) Expand all Loading... |
| 131 * Close obsolete bugs. | 131 * Close obsolete bugs. |
| 132 | 132 |
| 133 See [bug-triage-suggested-workflow.md](bug-triage-suggested-workflow.md) for | 133 See [bug-triage-suggested-workflow.md](bug-triage-suggested-workflow.md) for |
| 134 suggested workflows. | 134 suggested workflows. |
| 135 | 135 |
| 136 See [bug-triage-labels.md](bug-triage-labels.md) for labeling tips for network | 136 See [bug-triage-labels.md](bug-triage-labels.md) for labeling tips for network |
| 137 and non-network bugs. | 137 and non-network bugs. |
| 138 | 138 |
| 139 See [crash-course-in-net-internals.md](crash-course-in-net-internals.md) for | 139 See [crash-course-in-net-internals.md](crash-course-in-net-internals.md) for |
| 140 some help on getting started with about:net-internals debugging. | 140 some help on getting started with about:net-internals debugging. |
| OLD | NEW |