summaryrefslogtreecommitdiffstats
path: root/RELEASING
diff options
context:
space:
mode:
authorNico Weber <nicolasweber@gmx.de>2014-06-27 20:29:16 (GMT)
committerNico Weber <nicolasweber@gmx.de>2014-06-27 20:29:16 (GMT)
commit8308c70801caa8e97657cff08f1b895241f30e96 (patch)
treefbe5fb84a86685b557d62970627086af63b67ccb /RELEASING
parent7c231a3d0d800bfc2602da097b34d1edca2f600f (diff)
downloadNinja-8308c70801caa8e97657cff08f1b895241f30e96.zip
Ninja-8308c70801caa8e97657cff08f1b895241f30e96.tar.gz
Ninja-8308c70801caa8e97657cff08f1b895241f30e96.tar.bz2
expand RELEASING a bit
Diffstat (limited to 'RELEASING')
-rw-r--r--RELEASING8
1 files changed, 7 insertions, 1 deletions
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..