-
Notifications
You must be signed in to change notification settings - Fork 52
Release process
Beth Skurrie edited this page Jan 15, 2015
·
6 revisions
-
Open
CHANGELOG.md
and summarize the changes made since the last release (hopefully better than the individual commit messages). The history can be grabbed with a simple git command (assuming the last version was 1.3.0:$ git log v1.3.0..HEAD
-
Edit the version in
lib/webmachine/version.rb
. -
Commit both files (commit message is just a suggestion).
$ git add RELEASE_NOTES.md lib/webmachine/version.rb $ git commit -m "Version 1.3.1"
-
Tag the release, preferably using a signed annotation.
$ git tag -a -s -u $GPGKEY -m "Version 1.3.1" v1.3.1
-
Push the commit and tag.
$ git push origin; git push origin --tags
-
If this is a new major or minor release, push a new stable branch, otherwise merge the commit into the stable branch (or master, depending on where you made the commit).
$ git push origin HEAD:1.3-stable # or $ git checkout 1.3-stable; git merge master; git push origin
-
Build the gem. Looking at the output, ensure no transient artifacts (bundler gems, etc) are included.
$ bundle exec rake clobber_package gem
-
Release the gem.
$ bundle exec rake release
-
YOU'RE DONE!