sk program is fetched into the Skia repo by:
The release-branch subcommand automates several tasks done on each Skia release. It is safe to run as it only creates Gerrit CLs to be reviewed and makes no permanent changes. It does the following:
include/core/SkMilestone.hin the main branch. Example: http://review.skia.org/661110
Run as so:
./sk release-branch <release branch name>
./sk release-branch chrome/m113
release-branch works by creating CLs – which eventually merge into their target branches. Once this is done, running a second time will fail as the changes have already been made and
release-branch treats empty CLs as an error. To enable testing run with the
./sk release-branch --allow-empty chrome/m113
After running, if all goes well, new CLs will be in the outgoing section of https://skia-review.googlesource.com in your name. Some steps are smart enough to know that the change is already made and will not produce a new CL. As this is a test, they can be deleted once verified.
sk are automatically pulled into Skia via an autoroller. Skia's
fetch-sk retrieves the
sk version from the DEPS file and pulls that version down from CIPD for the correct platform.
sk in the final days before a Skia branch without first coordinating with the Skia release manager. Skia is branched alongside Chrome, and the Chrome branch schedule can be found at https://chromiumdash.appspot.com/schedule.