RELEASING document update

GitHub shows the message on a tag in the releases section.
dk1234567 · Sep 28, 2015 · 4313541 · 4313541
1 parent e30a63f
commit 4313541
Showing 1 changed file with 2 additions and 2 deletions.
diff --git a/RELEASING.md b/RELEASING.md
@@ -4,8 +4,8 @@
 2. Update `NEWS.md` to reflect the changes since last release.
 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.
-4. Tag the release: `git tag vVERSION`
-5. Push changes: `git push --tags`
+4. Tag the release: `git tag vVERSION -m "Release vVERSION"`
+5. Push changes: `git push && git push --tags`
 6. Build and publish the gem:
 
    ```bash