kotovalexarian-likes-github/capistrano
1
0
Fork 0
mirror of https://github.com/capistrano/capistrano synced 2023-03-27 23:21:18 -04:00
Code Releases Activity

Update version number in README

Browse source 
Also add a step to the RELEASING document so that we are less likely to
forget this in the future.
This commit is contained in:
Matt Brictson 2016-07-20 19:14:01 -07:00
parent bd2952bea8
commit a1ce7a2112
2 changed files with 2 additions and 1 deletions
Show stats Download patch file Download diff file Expand all files Collapse all files

2
README.md
View file

@ -103,7 +103,7 @@ Add Capistrano to your project's Gemfile:
``` ruby ``` ruby
group :development do group :development do
gem "capistrano", "~> 3.4" gem "capistrano", "~> 3.5"
end end
``` ```

1
RELEASING.md
View file

@ -11,6 +11,7 @@
2. **Ensure all tests are passing by running `rake spec` and `rake features`.** 2. **Ensure all tests are passing by running `rake spec` and `rake features`.**
3. Determine which would be the correct next version number according to [semver](http://semver.org/). 3. Determine which would be the correct next version number according to [semver](http://semver.org/).
4. Update the version in `./lib/capistrano/version.rb`. 4. Update the version in `./lib/capistrano/version.rb`.
4. Update the version in the `./README.md` Gemfile example (`gem "capistrano", "~> X.Y"`).
5. Update the `CHANGELOG`. 5. Update the `CHANGELOG`.
6. Commit the changelog and version in a single commit, the message should be "Preparing vX.Y.Z" 6. Commit the changelog and version in a single commit, the message should be "Preparing vX.Y.Z"
7. Run `rake release`; this will tag, push to GitHub, and publish to rubygems.org. 7. Run `rake release`; this will tag, push to GitHub, and publish to rubygems.org.