Skip to content

Commit

Permalink
Use v#.#.# convention for OSS release commits
Browse files Browse the repository at this point in the history
This keeps us in line with tools such as
https://github.com/tpope/git-bump and lets us use tools to auto-promote
releases when we have a consistent interface.
  • Loading branch information
Dan Croak committed Jul 7, 2014
1 parent 4ba47b5 commit bae91a2
Showing 1 changed file with 1 addition and 1 deletion.
2 changes: 1 addition & 1 deletion protocol/open-source/README.md
Original file line number Diff line number Diff line change
Expand Up @@ -10,6 +10,6 @@ Releasing a Ruby Gem
* Run `bundle install` to update `Gemfile.lock`.
* Run the test suite.
* Edit `NEWS`, `Changelog`, or `README` files if relevant.
* Commit changes like "Bump to 2.1.0".
* Commit changes. Use the convention "v2.1.0" in your commit message.
* Run `rake release`, which tags the release, pushes the tag
to GitHub, and pushes the gem to Rubygems.org.

0 comments on commit bae91a2

Please sign in to comment.