1Notes to myself on all the steps to make for a Ninja release. 2 3Push new release branch: 41. Run afl-fuzz for a day or so and run ninja_test 52. Consider sending a heads-up to the ninja-build mailing list first 63. Make sure branches 'master' and 'release' are synced up locally 74. Update src/version.cc with new version (with ".git"), then 8 git commit -am 'mark this 1.5.0.git' 95. git checkout release; git merge master 106. Fix version number in src/version.cc (it will likely conflict in the above) 117. Fix version in doc/manual.asciidoc (exists only on release branch) 128. commit, tag, push (don't forget to push --tags) 13 git commit -am v1.5.0; git push origin release 14 git tag v1.5.0; git push --tags 15 # Push the 1.5.0.git change on master too: 16 git checkout master; git push origin master 179. Construct release notes from prior notes 18 credits: git shortlog -s --no-merges REV.. 19 20Release on github: 211. https://github.com/blog/1547-release-your-software 22 Add binaries to https://github.com/ninja-build/ninja/releases 23 24Make announcement on mailing list: 251. copy old mail 26 27Update website: 281. Make sure your ninja checkout is on the v1.5.0 tag 292. Clone https://github.com/ninja-build/ninja-build.github.io 303. In that repo, `./update-docs.sh` 314. Update index.html with newest version and link to release notes 325. git commit -m 'run update-docs.sh, 1.5.0 release' 336. git push origin master 34