-
Notifications
You must be signed in to change notification settings - Fork 233
Release Process
jtlan edited this page Apr 25, 2015
·
10 revisions
- Pull the latest
develop. Cut the release branch fromdevelop:git co -b release-{VERSION}. - Push release branch to Github.
- Regression pass.
- If necessary, create hotfixes and merge them into the release branch.
- Run the release script on the release branch locally (
grunt release:minororgrunt release:patch, as necessary). - Push the resulting commit to the release branch.
- Merge the release branch into
developandmasterusing Pull Requests. It's best to add " --> develop" or " --> master" to the end of the Pull Request title so it's easy to tell them apart from the Pull Requests page.
- Create the release (aimed at
master), tagged {VERSION}. Add release notes based on Release Changes page. Attach plottable.zip:
