README.md in release-conductor-0.0.5 vs README.md in release-conductor-0.0.6
- old
+ new
@@ -51,9 +51,26 @@
Deploy your application like normal and the tickets should be marked.
## TODO
+## To publish a new version: (0.0.5 in this example)
+
+1. fix the bug
+2. update version.rb
+3. git commit -a -m "0.0.5 <my-comment-there>"
+4. git tag 0.0.5
+5. git push --tags
+6. gem build release-conductor.gemspec
+7. gem push push release-conductor-0.0.5.gem
+
+## To upgrade CODE to use the new version of the gem
+
+1. git checkout code-dev
+2. bundle update release-conductor
+3. git commit -a -m "@wip upgrading release-conductor gem"
+4. git woe minor (OR, merge the new Gemfile.lock into all the branches that need it)
+
## Contributing
1. Fork it
2. Create your feature branch (`git checkout -b my-new-feature`)
3. Commit your changes (`git commit -am 'Add some feature'`)