sync version number in master with release

Update RELEASING with notes on how to not screw this up again.
ninja-build · Apr 8, 2013 · 9f1852f · 9f1852f
1 parent 76faa25
commit 9f1852f
Show file tree

Hide file tree

Showing 2 changed files with 8 additions and 7 deletions.
diff --git a/RELEASING b/RELEASING
@@ -1,9 +1,10 @@
 Notes to myself on all the steps to make for a Ninja release.
 
-1. git checkout release; git merge master
+1. update src/version.cc with new version (with ".git")
-2. fix version number in source (it will likely conflict in the above)
+2. git checkout release; git merge master
-3. fix version in doc/manual.asciidoc
+3. fix version number in src/version.cc (it will likely conflict in the above)
-4. rebuild manual, put in place on website
+4. fix version in doc/manual.asciidoc
-5. commit, tag, push
+5. rebuild manual, put in place on website
-6. construct release notes from prior notes
+6. commit, tag, push
+7. construct release notes from prior notes
    credits: git shortlog -s --no-merges REV..
diff --git a/src/version.cc b/src/version.cc
@@ -18,7 +18,7 @@
 
 #include "util.h"
 
-const char* kNinjaVersion = "1.1.0.git";
+const char* kNinjaVersion = "1.2.0.git";
 
 void ParseVersion(const string& version, int* major, int* minor) {
   size_t end = version.find('.');