aboutsummaryrefslogtreecommitdiffhomepage
path: root/site/dev/chrome
diff options
context:
space:
mode:
authorGravatar hcm <hcm@google.com>2016-09-22 12:47:14 -0700
committerGravatar Commit bot <commit-bot@chromium.org>2016-09-22 12:47:14 -0700
commit3d89a7c0d28c4b9312b10149037f2fdac5dc5985 (patch)
tree0e8e7fe6e571599a656f0f556629f62f8179f16c /site/dev/chrome
parent8c170971f182d47bc9af71fc88a607740d03dfd5 (diff)
Update Chrome section to include Skia roll/sheriff/bug info
Diffstat (limited to 'site/dev/chrome')
-rw-r--r--site/dev/chrome/index.md18
1 files changed, 17 insertions, 1 deletions
diff --git a/site/dev/chrome/index.md b/site/dev/chrome/index.md
index ba9dcdfa6f..d715304f32 100644
--- a/site/dev/chrome/index.md
+++ b/site/dev/chrome/index.md
@@ -1,5 +1,21 @@
Skia in Chrome
==============
+Changes to the Skia repository will be rolled into Chromium (and Blink) by the
+AutoRoll bot several times per day.
+
If you have a Skia change that needs to be tested in Chrome or Blink, or which
-requires associated changes in those repositories, this is the place for you.
+requires associated changes in those repositories, see the guides in this
+section for tips on execution.
+
+For problems in Chromium related to Skia rolls:
+
+ * Go to https://autoroll.skia.org. Login with google.com account and click
+ the STOP button to pause new rolls.
+ * Revert the offending DEPS roll.
+ * If an obvious owner cannot be found in the list of CLs, assign to the Skia
+ Sheriff, listed at the top of https://status.skia.org and as a reviewer
+ on the roll CL.
+ * If the Sheriff cannot be assigned, cc them and assign the issue to hcm@.
+
+For more tips on bug triage and labeling, see the [Issue Tracker page](../../user/issue-tracker/).