chromium/src
0
Fork 0
Code Activity

Misc changes to network bug triage documentation.

Browse Source 
NOTRY=true

Change-Id: Id8f7a70e5a840a2d9e0483be1a005d7dcc399efa
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2368447
Commit-Queue: Eric Roman <eroman@chromium.org>
Reviewed-by: Zhongyi Shi <zhongyi@chromium.org>
Cr-Commit-Position: refs/heads/master@{#800876}
This commit is contained in:
Eric Roman
2020-08-23 18:14:38 +00:00
committed by Commit Bot
parent 1d2c48dea3
commit 4ad6aed7b8
1 changed files with 11 additions and 9 deletions

20
net/docs/bug-triage.md

@ -10,22 +10,26 @@ of their two days working on bug triage/investigation.
Look through [this list of untriaged
bugs](https://bugs.chromium.org/p/chromium/issues/list?sort=pri%20-stars%20-opened&q=status%3Aunconfirmed%2Cuntriaged%20-Needs%3DFeedback%20-Label%3ANetwork-Triaged%20component%3DInternals%3ENetwork%2CInternals%3ENetwork%3ECache%2CInternals%3ENetwork%3ESSL%2CInternals%3ENetwork%3EQUIC%2CInternals%3ENetwork%3EAuth%2CInternals%3ENetwork%3EHTTP2%2CInternals%3ENetwork%3EProxy%2CInternals%3ENetwork%3ELibrary%2CInternals%3ENetwork%3ELogging%2CInternals%3ENetwork%3EConnectivity%2CInternals%3ENetwork%3EDomainSecurityPolicy%2CInternals%3ENetwork%3ETrustTokens%2CInternals%3ENetwork%3EFilters%2CInternals%3ENetwork%3EFTP%2CInternals%3ENetwork%3ESDCH).
* Go through them in the given order (top to bottom).
The link sorts them by priority and then recency.
* The goal is to move them out of the untriaged bug queue and give them a priority.
The goal is for this query to be empty. Bugs can be removed from the triage queue
by doing any of the following:
* Changing the bug status - marking the bug Available, or closing it.
* Removing the `Internals>Network` component or subcomponent.
* Adding the label `Network-Triaged` (when there are multiple components).
For each bug try to:
* Remove the `Internals>Network` component if it belongs elsewhere
* Remove the `Internals>Network` component or subcomponent if it belongs
elsewhere
* Dupe it against an existing bug
* Close it `WontFix` if appropriate
* Close it as `WontFix`.
* Give the bug a priority. Refer to [this (internal) document for guidelines](https://goto.google.com/xnzwn)
* If the bug is a potential security issue (Allows for code execution from remote
site, allows crossing security boundaries, unchecked array bounds, etc) mark
it `Type-Bug-Security`.
* If the bug has privacy implications mark it with component `Privacy`.
* Mark it as a feature request or task if appropriate
* Ask the reporter to narrow down regressions, possibly by using
* Set the type to `Task` or `Feature` when it is not a bug.
* Pay extra attention to possible regressions. Ask the reporter to narrow down using
[bisect-builds-py](https://www.chromium.org/developers/bisect-builds-py). To
view suspicious changelists in a regression window, you can use the Change Log
form on [OmahaProxy](https://omahaproxy.appspot.com/)
@ -70,8 +74,6 @@ crashers](https://goto.google.com/network_triage_internal#investigating-crashers
Look through [this list of Needs=Feedback
bugs](https://bugs.chromium.org/p/chromium/issues/list?sort=pri%20-modified&q=Needs%3DFeedback%20component%3DInternals%3ENetwork%2CInternals%3ENetwork%3ECache%2CInternals%3ENetwork%3ESSL%2CInternals%3ENetwork%3EQUIC%2CInternals%3ENetwork%3EAuth%2CInternals%3ENetwork%3EHTTP2%2CInternals%3ENetwork%3EProxy%2CInternals%3ENetwork%3ELibrary%2CInternals%3ENetwork%3ELogging%2CInternals%3ENetwork%3EConnectivity%2CInternals%3ENetwork%3EDomainSecurityPolicy%2CInternals%3ENetwork%3ETrustTokens%2CInternals%3ENetwork%3EFilters%2CInternals%3ENetwork%3EFTP%2CInternals%3ENetwork%3ESDCH).
* Go through them in the given order (top to bottom).
The link sorts them by priority and then recency.
* If the requested feedback was provided, review the new information and repeat
the same steps as (1) to re-triage based on the new information.
* If the bug had the `Needs-Feedback` label for over a week and the