Sha256: 34553c870481eb134d03c9851df2b77e1a4e7cce4ab0bf54c3b25e4ce30c5c3b

Contents?: true

Size: 467 Bytes

Versions: 14

Compression:

Stored size: 467 Bytes

Contents

For example assuming you are releasing fix to 0.8.18

1. Checkout 0-8-stable
2. Update tests, fix the bug and commit the changes.
3. Build & Release to RubyGems (Remember the version in version.rb should already be 0.8.19)
4. Create a tag 'v0.8.19' pointing to that commit. (`tag v0.8.19`)
5. Bump the version in 0-8-stable to 0.8.20 so it will be ready for the next patch level release.
6. Commit the version bump, and do a `git push --tags` so the new tag goes up

Version data entries

14 entries across 14 versions & 2 rubygems

Version Path
reactrb-0.8.8 path_release_steps.md
reactrb-0.8.7 path_release_steps.md
reactrb-0.8.6 path_release_steps.md
reactrb-0.8.5 path_release_steps.md
reactrb-0.8.4 path_release_steps.md
reactrb-0.8.3 path_release_steps.md
reactrb-0.8.1 path_release_steps.md
reactrb-0.8.0 path_release_steps.md
reactrb-0.7.42 path_release_steps.md
reactive-ruby-0.7.41 path_release_steps.md
reactive-ruby-0.7.40 path_release_steps.md
reactive-ruby-0.7.39 path_release_steps.md
reactive-ruby-0.7.38 path_release_steps.md
reactive-ruby-0.7.36 path_release_steps.md