Chromium Code Reviews
chromiumcodereview-hr@appspot.gserviceaccount.com (chromiumcodereview-hr) | Please choose your nickname with Settings | Help | Chromium Project | Gerrit Changes | Sign out
(571)

Unified Diff: net/docs/bug-triage-suggested-workflow.md

Issue 1836343002: Tweak network doc wording, fix link, and make order in workflow match (Closed) Base URL: https://chromium.googlesource.com/chromium/src.git@master
Patch Set: Created 4 years, 9 months ago
Use n/p to move between diff chunks; N/P to move between comments. Draft comments are only viewable by you.
Jump to:
View side-by-side diff with in-line comments
Download patch
« net/docs/bug-triage.md ('K') | « net/docs/bug-triage.md ('k') | no next file » | no next file with comments »
Expand Comments ('e') | Collapse Comments ('c') | Show Comments Hide Comments ('s')
Index: net/docs/bug-triage-suggested-workflow.md
diff --git a/net/docs/bug-triage-suggested-workflow.md b/net/docs/bug-triage-suggested-workflow.md
index a54d0085d4b969362cfb2ce7bbe00fce9669ec42..9be9f3c1a8024643236d86308b1e270293744550 100644
--- a/net/docs/bug-triage-suggested-workflow.md
+++ b/net/docs/bug-triage-suggested-workflow.md
@@ -29,6 +29,24 @@
* If non-network causes also seem possible, attach those components as well.
+## Investigate UMA notifications
+
+For each alert that fires, determine if it's a real alert and file a bug if so.
+
+* Don't file if the alert is coincident with a major volume change. The volume
+ at a particular date can be determined by hovering the mouse over the
+ appropriate location on the alert line.
+
+* Don't file if the alert is on a graph with very low volume (< ~200 data
+ points); it's probably noise, and we probably don't care even if it isn't.
+
+* Don't file if the graph is really noisy (but eyeball it to decide if there is
+ an underlying important shift under the noise).
+
+* Don't file if the alert is in the "Known Ignorable" list:
+ * SimpleCache on Windows
+ * DiskCache on Android.
+
## Investigating component=Internals>Network bugs
* It's recommended that while on triage duty, you subscribe to the
@@ -107,24 +125,6 @@
subcomponent applies, or only the Internals>Network>HTTP subcomponent
applies, and there's no clear owner), try to figure out the exact cause.
-## Investigate UMA notifications
-
-For each alert that fires, determine if it's a real alert and file a bug if so.
-
-* Don't file if the alert is coincident with a major volume change. The volume
- at a particular date can be determined by hovering the mouse over the
- appropriate location on the alert line.
-
-* Don't file if the alert is on a graph with very low volume (< ~200 data
- points); it's probably noise, and we probably don't care even if it isn't.
-
-* Don't file if the graph is really noisy (but eyeball it to decide if there is
- an underlying important shift under the noise).
-
-* Don't file if the alert is in the "Known Ignorable" list:
- * SimpleCache on Windows
- * DiskCache on Android.
-
## Looking for new crashers
1. Go to [go/chromecrash](https://goto.google.com/chromecrash).
« net/docs/bug-triage.md ('K') | « net/docs/bug-triage.md ('k') | no next file » | no next file with comments »

Powered by Google App Engine
This is Rietveld 408576698