From: Nico Weber <nicolasweber@gmx.de>
Date: Fri, 27 Jun 2014 20:29:16 +0000 (-0700)
Subject: expand RELEASING a bit
X-Git-Tag: v1.5.1^2~3^2
X-Git-Url: http://review.tizen.org/git/?a=commitdiff_plain;h=8308c70801caa8e97657cff08f1b895241f30e96;p=platform%2Fupstream%2Fninja.git

expand RELEASING a bit
---

diff --git a/RELEASING b/RELEASING
index c4973b2..c251dd8 100644
--- a/RELEASING
+++ b/RELEASING
@@ -2,11 +2,17 @@ Notes to myself on all the steps to make for a Ninja release.
 
 Push new release branch:
 1. Consider sending a heads-up to the ninja-build mailing list first
-2. update src/version.cc with new version (with ".git"), commit to master
+2. update src/version.cc with new version (with ".git"), then
+       git commit -a -m 'mark this 1.5.0.git'
 3. git checkout release; git merge master
 4. fix version number in src/version.cc (it will likely conflict in the above)
 5. fix version in doc/manual.asciidoc
 6. commit, tag, push (don't forget to push --tags)
+       git commit -a -m v1.5.0
+       git tag v1.5.0
+       git push --tags
+       git checkout master
+       git push origin master  # Push the 1.5.0.git change on master too
 7. construct release notes from prior notes
    credits: git shortlog -s --no-merges REV..