1Skia in Chrome 2============== 3 4Changes to the Skia repository will be rolled into Chromium by the AutoRoll bot 5several times per day. 6 7If you have a Skia change that needs to be tested in Chrome, or which requires 8associated changes in that repository, see the guides in this section for tips 9on execution. 10 11For problems in Chromium related to Skia rolls: 12 13 * Go to https://autoroll.skia.org/r/skia-autoroll. Login with google.com 14 account and click the STOP button to pause new rolls. 15 * Revert the offending DEPS roll. 16 * If an obvious owner cannot be found in the list of CLs, assign to the Skia 17 Sheriff, listed at the top of https://status.skia.org and as a reviewer 18 on the roll CL. 19 * If the Sheriff cannot be assigned, cc them and assign the issue to hcm@. 20 21For more tips on bug triage and labeling, see the [Issue Tracker page](../../user/issue-tracker/). 22 23Branching for Chrome 24-------------------- 25 26Every 6 weeks, we cut a new branch in Skia to reflect the new release branch in 27Chrome, eg. [refs/heads/chrome/m75](https://skia.googlesource.com/skia/+/chrome/m75). 28This process is simplified by running [tools/chrome_release_branch](https://skia.googlesource.com/skia/+/7a5b6ec0f6c01d3039e3ec30de6f8065ffc8aac4/tools/chrome_release_branch.py'). 29This script handles creation of the branch itself, as well as associated 30housekeeping like updating the Chrome milestone number for the next release, 31setting up the [commit queue]('https://skia.googlesource.com/skia/+/infra/config/commit-queue.cfg') 32for the new branch. For example: 33 34 tools/chrome_release_branch <commit hash> 35 36