OLD | NEW |
1 # Chrome Network Bug Triage : Suggested Workflow | 1 # Chrome Network Bug Triage : Suggested Workflow |
2 | 2 |
3 [TOC] | 3 [TOC] |
4 | 4 |
5 ## Looking for new crashers | 5 ## Looking for new crashers |
6 | 6 |
7 1. Go to [go/chromecrash](https://goto.google.com/chromecrash). | 7 1. Go to [go/chromecrash](https://goto.google.com/chromecrash). |
8 | 8 |
9 2. For each platform, look through the releases for which releases to | 9 2. For each platform, look through the releases for which releases to |
10 investigate. As per bug-triage.txt, this should be the most recent canary, | 10 investigate. As per bug-triage.txt, this should be the most recent canary, |
(...skipping 70 matching lines...) Expand 10 before | Expand all | Expand 10 after Loading... |
81 browser crash) and attach the most specific internals-network label that's | 81 browser crash) and attach the most specific internals-network label that's |
82 applicable. If there isn't an applicable narrower label, a clear owner for | 82 applicable. If there isn't an applicable narrower label, a clear owner for |
83 the issue, or there are multiple possibilities, attach the internals-network | 83 the issue, or there are multiple possibilities, attach the internals-network |
84 label and proceed with further investigation. | 84 label and proceed with further investigation. |
85 | 85 |
86 * If non-network causes also seem possible, attach those labels as well. | 86 * If non-network causes also seem possible, attach those labels as well. |
87 | 87 |
88 ## Investigating Cr-Internals-Network bugs | 88 ## Investigating Cr-Internals-Network bugs |
89 | 89 |
90 * It's recommended that while on triage duty, you subscribe to the | 90 * It's recommended that while on triage duty, you subscribe to the |
91 Cr-Internals-Network label. To do this, go to the issue tracker and click on | 91 Internals>Network component (but not its subcomponents). To do this, go |
92 [Subscriptions](https://code.google.com/p/chromium/issues/subscriptions). | 92 to the issue tracker and then click "Saved Queries". |
93 Enter "Cr-Internals-Network" and click submit. | 93 Add a query with these settings: |
| 94 * Saved query name: Network Bug Triage |
| 95 * Project: chromium |
| 96 * Query: component=Internals>Network |
| 97 * Subscription options: Notify Immediately |
94 | 98 |
95 * Look through uncomfirmed and untriaged Cr-Internals-Network bugs, | 99 * Look through uncomfirmed and untriaged Cr-Internals-Network bugs, |
96 prioritizing those updated within the last week. [Use this issue tracker | 100 prioritizing those updated within the last week. [Use this issue tracker |
97 query](https://code.google.com/p/chromium/issues/list?can=2&q=Cr%3DInternals-N
etwork+-status%3AAssigned+-status%3AStarted+-status%3AAvailable+&sort=-modified)
. | 101 query](https://code.google.com/p/chromium/issues/list?can=2&q=Cr%3DInternals-N
etwork+-status%3AAssigned+-status%3AStarted+-status%3AAvailable+&sort=-modified)
. |
98 | 102 |
99 * If more information is needed from the reporter, ask for it and add the | 103 * If more information is needed from the reporter, ask for it and add the |
100 Needs-Feedback label. If the reporter has answered an earlier request for | 104 Needs-Feedback label. If the reporter has answered an earlier request for |
101 information, remove that label. | 105 information, remove that label. |
102 | 106 |
103 * While investigating a new issue, change the status to Untriaged. | 107 * While investigating a new issue, change the status to Untriaged. |
(...skipping 131 matching lines...) Expand 10 before | Expand all | Expand 10 after Loading... |
235 reproduced or really understood: | 239 reproduced or really understood: |
236 * If it's over a year old, go ahead and mark the issue as Archived. | 240 * If it's over a year old, go ahead and mark the issue as Archived. |
237 * Otherwise, ask reporters if the issue is still present, and attach | 241 * Otherwise, ask reporters if the issue is still present, and attach |
238 the Needs-Feedback label. | 242 the Needs-Feedback label. |
239 | 243 |
240 * Old unconfirmed or untriaged Cr-Internals-Network issues can be investigated | 244 * Old unconfirmed or untriaged Cr-Internals-Network issues can be investigated |
241 just like newer ones. Crashers should generally be given higher priority, | 245 just like newer ones. Crashers should generally be given higher priority, |
242 since we can verify if they still occur, and then newer issues, as they're | 246 since we can verify if they still occur, and then newer issues, as they're |
243 more likely to still be present, and more likely to have a still responsive | 247 more likely to still be present, and more likely to have a still responsive |
244 bug reporter. | 248 bug reporter. |
OLD | NEW |