Commit db1ebd13 by Tute Costa

Adjustments to RELEASING document

parent 14356d7e
...@@ -4,13 +4,13 @@ Releasing paperclip ...@@ -4,13 +4,13 @@ Releasing paperclip
2. Update `NEWS` to reflect the changes since last release. 2. Update `NEWS` to reflect the changes since last release.
3. Commit changes. There shouldn’t be code changes, and thus CI doesn’t need to 3. Commit changes. There shouldn’t be code changes, and thus CI doesn’t need to
run, you can then add “[ci skip]” to the commit message. run, you can then add “[ci skip]” to the commit message.
4. Tag the release: `git tag vVERSION` 4. Tag the release: `git tag -m 'vVERSION' vVERSION`
5. Push changes: `git push --tags` 5. Push changes: `git push --tags`
6. Build and publish the gem: 6. Build and publish the gem:
```bash ```bash
gem build paperclip.gemspec gem build paperclip.gemspec
gem push paperclip-*.gem gem push paperclip-VERSION.gem
``` ```
7. Announce the new release, making sure to say “thank you” to the contributors 7. Announce the new release, making sure to say “thank you” to the contributors
......
Markdown is supported
0% or
You are about to add 0 people to the discussion. Proceed with caution.
Finish editing this message first!
Please register or to comment