This repository was archived by the owner on Apr 1, 2020. It is now read-only.
-
Notifications
You must be signed in to change notification settings - Fork 300
Release Process
Bryan Phelps edited this page Dec 15, 2018
·
6 revisions
This is a checklist documenting our release process:
-
Get latest master:
git checkout mastergit pull origin master
-
Checkout the
stagingbranchgit checkout staging
-
Merge
mastertostaginggit merge master
-
Create release branch (
release/x.x.x) off of staging- Version needs to match the
package.jsonversion
- Version needs to match the
-
Draft release notes to a file
-
Push
stagingand therelease/x.x.xbranches -
In the GitHub UI, Create a new release, based on the
release/x.x.xbranch -
While the release is building, create a PR on master:
- Bump
package.jsonmaster
- Bump
-
Validate the output build, and run the following validations
- Test language server on each platform
- Test INTL keyboard on each platform
-
Once the release is validated:
- Switch from pre-release to latest
- Update artifact links in
Release-Process.mdin the wiki - Update artifacts in our blob storage for the
community.jsonbuild
-
Bring in the PR on master
-
Update site documents in oni-docs by pulling in the Wiki.
-
Once we are OK with the release, merge the
release/x.x.xbranch intostable.