AuroraMiddleware/skia2
1
0
Fork 0
Code Issues Pull Requests Projects Releases Wiki Activity
ddc21485cb
skia2/site/dev/chrome/index.md
Eric Boren 264000254c [docs] Update documentation for branching process 
Document new chrome_release_branch script.

No-Try: true
Docs-Preview: https://skia.org/?cl=209418
Bug: skia:8932
Change-Id: Ic38840f6e8ecac309e6bd7669dd2b110ff586401
Reviewed-on: https://skia-review.googlesource.com/c/skia/+/209418
Commit-Queue: Eric Boren <borenet@google.com>
Reviewed-by: Ravi Mistry <rmistry@google.com>
2019-04-22 16:46:33 +00:00

1.6 KiB
Raw Blame History

Skia in Chrome

Changes to the Skia repository will be rolled into Chromium by the AutoRoll bot several times per day.

If you have a Skia change that needs to be tested in Chrome, or which requires associated changes in that repository, see the guides in this section for tips on execution.

For problems in Chromium related to Skia rolls:

  • Go to https://autoroll.skia.org/r/skia-autoroll. 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.

Branching for Chrome

Every 6 weeks, we cut a new branch in Skia to reflect the new release branch in Chrome, eg. refs/heads/chrome/m75. This process is simplified by running tools/chrome_release_branch. This script handles creation of the branch itself, as well as associated housekeeping like updating the Chrome milestone number for the next release, setting up the commit queue for the new branch. For example:

tools/chrome_release_branch <commit hash>