-
Notifications
You must be signed in to change notification settings - Fork 221
Release Process
Benjamin Lee edited this page Apr 19, 2017
·
10 revisions
- On the latest
develop
, check out a new branch (e.g.release/v3.1.0
). Bump thepackage.json
andbower.json
version. - Commit with a message like "preparing release 3.1.0" and send a PR -- example at https://github.com/palantir/plottable/pull/3249
- Draft up release notes. When the PR is green and things look good, merge the PR.
- Create a new Github release at https://github.com/palantir/plottable/releases.
- Tag it with the same version (e.g. "v3.1.0"), and put in the release notes.
- Review release notes to make sure everything looks good.
- Publish the release. CircleCI will build and publish to NPM for us.
- Tag and publish the next pre-release (e.g. "v3.2.0-dev") on the release commit (likely still develop). CircleCI will publish to NPM for us.