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