From 8308c70801caa8e97657cff08f1b895241f30e96 Mon Sep 17 00:00:00 2001 From: Nico Weber Date: Fri, 27 Jun 2014 13:29:16 -0700 Subject: expand RELEASING a bit --- RELEASING | 8 +++++++- 1 file changed, 7 insertions(+), 1 deletion(-) 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.. -- cgit v0.12