This repository has been archived by the owner on Apr 1, 2020. It is now read-only.
-
Notifications
You must be signed in to change notification settings - Fork 298
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 master
git pull origin master
-
Checkout the
staging
branchgit checkout staging
-
Merge
master
tostaging
git merge master
-
Create release branch (
release/x.x.x
) off of staging- Version needs to match the
package.json
version
- Version needs to match the
-
Draft release notes to a file
-
Push
staging
and therelease/x.x.x
branches -
In the GitHub UI, Create a new release, based on the
release/x.x.x
branch -
While the release is building, create a PR on master:
- Bump
package.json
master
- 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.md
in the wiki - Update artifacts in our blob storage for the
community.json
build
-
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.x
branch intostable
.