diff options
Diffstat (limited to 'ninja/RELEASING')
| -rw-r--r-- | ninja/RELEASING | 17 |
1 files changed, 8 insertions, 9 deletions
diff --git a/ninja/RELEASING b/ninja/RELEASING index da4dbdd0f73..5f51b736e35 100644 --- a/ninja/RELEASING +++ b/ninja/RELEASING @@ -1,20 +1,19 @@ Notes to myself on all the steps to make for a Ninja release. Push new release branch: -1. Run afl-fuzz for a day or so (see HACKING.md) and run ninja_test -2. Consider sending a heads-up to the ninja-build mailing list first -3. Make sure branches 'master' and 'release' are synced up locally -4. Update src/version.cc with new version (with ".git"), then +1. Consider sending a heads-up to the ninja-build mailing list first +2. Make sure branches 'master' and 'release' are synced up locally +3. update src/version.cc with new version (with ".git"), then git commit -am 'mark this 1.5.0.git' -5. git checkout release; git merge master -6. Fix version number in src/version.cc (it will likely conflict in the above) -7. Fix version in doc/manual.asciidoc (exists only on release branch) -8. commit, tag, push (don't forget to push --tags) +4. git checkout release; git merge master +5. fix version number in src/version.cc (it will likely conflict in the above) +6. fix version in doc/manual.asciidoc (exists only on release branch) +7. commit, tag, push (don't forget to push --tags) git commit -am 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 -9. Construct release notes from prior notes +8. construct release notes from prior notes credits: git shortlog -s --no-merges REV.. Release on github: |