From 6f7ea464bb9161ce2e15deb97977886de152c12d Mon Sep 17 00:00:00 2001 From: Evan Martin Date: Wed, 11 Sep 2013 19:05:21 -0700 Subject: mark this 1.4.0.git, update RELEASING --- RELEASING | 18 ++++++++++++++---- src/version.cc | 2 +- 2 files changed, 15 insertions(+), 5 deletions(-) diff --git a/RELEASING b/RELEASING index 1110f0b..25926db 100644 --- a/RELEASING +++ b/RELEASING @@ -1,12 +1,22 @@ Notes to myself on all the steps to make for a Ninja release. +Push new release branch: 1. update src/version.cc with new version (with ".git") 2. git checkout release; git merge master 3. fix version number in src/version.cc (it will likely conflict in the above) 4. fix version in doc/manual.asciidoc -5. rebuild manual, put in place on website -6. commit, tag, push (don't forget to push --tags) -7. construct release notes from prior notes +5. commit, tag, push (don't forget to push --tags) +6. construct release notes from prior notes credits: git shortlog -s --no-merges REV.. -8. update home page mention of latest version. +Release on github: +1. (haven't tried this yet) + https://github.com/blog/1547-release-your-software + +Make announcement on mailing list: +1. copy old mail + +Update website: +(note to self: website is now in github.com/martine/martine.github.io) +1. rebuild manual, put in place on website +2. update home page mention of latest version. diff --git a/src/version.cc b/src/version.cc index 18fa96a..1406d91 100644 --- a/src/version.cc +++ b/src/version.cc @@ -18,7 +18,7 @@ #include "util.h" -const char* kNinjaVersion = "1.3.0.git"; +const char* kNinjaVersion = "1.4.0.git"; void ParseVersion(const string& version, int* major, int* minor) { size_t end = version.find('.'); -- cgit v0.12