1 Notes to myself on all the steps to make for a Ninja release.
3 Push new release branch:
4 1. Consider sending a heads-up to the ninja-build mailing list first
5 2. update src/version.cc with new version (with ".git"), then
6 git commit -a -m 'mark this 1.5.0.git'
7 3. git checkout release; git merge master
8 4. fix version number in src/version.cc (it will likely conflict in the above)
9 5. fix version in doc/manual.asciidoc
10 6. commit, tag, push (don't forget to push --tags)
11 git commit -a -m v1.5.0; git push origin release
12 git tag v1.5.0; git push --tags
13 # Push the 1.5.0.git change on master too:
14 git checkout master; git push origin master
15 7. construct release notes from prior notes
16 credits: git shortlog -s --no-merges REV..
19 1. https://github.com/blog/1547-release-your-software
20 Add binaries to https://github.com/martine/ninja/releases
22 Make announcement on mailing list:
26 (note to self: website is now in github.com/martine/martine.github.io)
27 1. rebuild manual, put in place on website
28 2. update home page mention of latest version.