forked from flutter-team-archive/engine
-
Notifications
You must be signed in to change notification settings - Fork 0
Release process
Ian Hickson edited this page Aug 16, 2016
·
64 revisions
- Pick a revision (i.e., git hash in this repository) to release. The revision must have been green on the Linux Engine and Mac Engine bots on the waterfall.
- Land a pull request in flutter.git that updates engine.version to that git hash. As with all pull requests, you should wait for Travis to give you a green light before landing.
- Watch the waterfall to make sure it doesn't go red.
- Watch the cocoon dashboard (if you are not a Googler, get one to do this for you) to make sure no tests fail.
If anything fails, immediately roll back the engine release.