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 |
(...skipping 78 matching lines...) Expand 10 before | Expand all | Expand 10 after Loading... |
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. |
| 99 |
| 100 See [crash-course-in-net-internals.md](crash-course-in-net-internals.md) for |
| 101 some help on getting started with about:net-internals debugging. |
OLD | NEW |