2013-02-01 18:31:46 +00:00
|
|
|
Notes to myself on all the steps to make for a Ninja release.
|
|
|
|
|
|
2013-09-12 02:05:21 +00:00
|
|
|
Push new release branch:
|
2014-06-27 20:15:57 +00:00
|
|
|
1. Consider sending a heads-up to the ninja-build mailing list first
|
2014-06-27 20:29:16 +00:00
|
|
|
2. update src/version.cc with new version (with ".git"), then
|
|
|
|
|
git commit -a -m 'mark this 1.5.0.git'
|
2014-06-27 20:15:57 +00:00
|
|
|
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)
|
2014-06-27 21:11:23 +00:00
|
|
|
git commit -a -m v1.5.0; git push origin release
|
|
|
|
|
git tag v1.5.0; git push --tags
|
|
|
|
|
# Push the 1.5.0.git change on master too:
|
|
|
|
|
git checkout master; git push origin master
|
2014-06-27 20:15:57 +00:00
|
|
|
7. construct release notes from prior notes
|
2013-02-01 18:31:46 +00:00
|
|
|
credits: git shortlog -s --no-merges REV..
|
2013-05-21 22:46:30 +00:00
|
|
|
|
2013-09-12 02:05:21 +00:00
|
|
|
Release on github:
|
2014-06-27 20:15:57 +00:00
|
|
|
1. https://github.com/blog/1547-release-your-software
|
2015-11-11 21:34:13 +00:00
|
|
|
Add binaries to https://github.com/ninja-build/ninja/releases
|
2013-09-12 02:05:21 +00:00
|
|
|
|
|
|
|
|
Make announcement on mailing list:
|
|
|
|
|
1. copy old mail
|
|
|
|
|
|
|
|
|
|
Update website:
|
2015-03-25 19:19:14 +00:00
|
|
|
1. Make sure your ninja checkout is on the v1.5.0 tag
|
2015-11-11 21:34:13 +00:00
|
|
|
2. Clone https://github.com/ninja-build/ninja-build.github.io
|
2016-04-27 20:27:45 +00:00
|
|
|
3. In that repo, `./update-docs.sh`
|
2015-03-25 19:19:14 +00:00
|
|
|
4. Update index.html with newest version and link to release notes
|
|
|
|
|
5. git commit -m 'run update-docs.sh, 1.5.0 release'
|
|
|
|
|
6. git push origin master
|
