Lines Matching +full:network +full:- +full:based
1 # Chrome Network Bug Triage
3 The Chrome network team uses a two day bug triage rotation. The goal is to
5 based rather than objective based. Sheriffs are expected to spend the majority
11 …m/issues/list?sort=pri%20-stars%20-opened&q=status%3Aunconfirmed%2Cuntriaged%20-Needs%3DFeedback%2…
16 * Changing the bug status - marking the bug Available, or closing it.
17 * Removing the `Internals>Network` component or subcomponent.
18 * Adding the label `Network-Triaged` (when there are multiple components).
22 * Remove the `Internals>Network` component or subcomponent if it belongs
29 it `Type-Bug-Security`.
33 [bisect-builds-py](https://www.chromium.org/developers/bisect-builds-py). To
37 * Mark it as `Needs-Feedback` and request more information if needed.
39 outside of networking, further network triage may not be possible. In those
41 `Network-Triaged` label to the bug, and add a comment explaining which team
42 should triage further. Adding the `Network-Triaged` serves to filter the
44 * Avoid spending time deep-diving into ambiguous issues when you suspect it is
45 an out of scope server or network problem, and is not clearly high priority
49 * Add the `Needs-Feedback` label
52 * Point them to `chrome://net-export` and the
53 [NetLog Viewer](https://netlog-viewer.appspot.com/).
58 Please collect and attach a chrome://net-export log.
60 https://chromium.org/for-testers/providing-network-details
63 [crash-course-in-net-internals.md](crash-course-in-net-internals.md) for an
65 * Move to a subcomponent of `Internals>Network` if appropriate. See
66 [bug-triage-labels.md](bug-triage-labels.md) for an overview of the components.
68 ID](https://goto.google.com/network_triage_internal#dealing-with-a-crash-id)
70 crashers](https://goto.google.com/network_triage_internal#investigating-crashers)
72 ## 2. Follow-up on issues with the Needs-Feedback label
75 bugs](https://bugs.chromium.org/p/chromium/issues/list?sort=-modified%20-modified&q=Needs%3DFeedbac…
78 the same steps as (1) to re-triage based on the new information.
79 * If the bug had the `Needs-Feedback` label for over 30 days, and the
85 …omium.org/p/chromium/issues/list?sort=pri%20-stars%20-opened&q=Pri%3A0%2C1%20-has%3Aowner%20-label…
94 …Looking for new crashers](https://goto.google.com/network_triage_internal#looking-for-new-crashers)
98 On the final day of your rotation, send a brief summary to net-dev@chromium.org
104 Not all of the subcomponents of `Interals>Network` are handled by this rotation.
109 Internals>Network
110 Internals>Network>Auth
111 Internals>Network>Cache
112 Internals>Network>Cache>Simple
113 Internals>Network>DNS
114 Internals>Network>Connectivity
115 Internals>Network>DomainSecurityPolicy
116 Internals>Network>FTP
117 Internals>Network>HTTP2
118 Internals>Network>Logging
119 Internals>Network>Proxy
120 Internals>Network>QUIC
121 Internals>Network>ReportingAndNEL
122 Internals>Network>SSL
125 The rest of the `Internals>Network` subcomponents are out of scope,
129 Internals>Network>Certificate
130 Internals>Network>CertTrans
131 Internals>Network>Cookies
132 Internals>Network>DataProxy
133 Internals>Network>DataUse
134 Internals>Network>DoH
135 Internals>Network>EV
136 Internals>Network>Library
137 Internals>Network>NetInfo
138 Internals>Network>NetworkQuality
139 Internals>Network>TrustTokens
140 Internals>Network>VPN
152 * Owners for the network bug triage rotation can find instructions on
154 [here (internal-only)](https://goto.google.com/net-triage-setup).
157 Dashboard](https://chromiumdash.appspot.com/components/Internals/Network?project=Chromium)
166 …rm Team SLOs](https://docs.google.com/document/d/18ylPve6jd43m8B7Dil6xmS4G9MHL2_DhQon72je-O9o/edit)