diff options
| author | Nico Weber <nicolasweber@gmx.de> | 2014-06-27 20:15:57 (GMT) |
|---|---|---|
| committer | Nico Weber <nicolasweber@gmx.de> | 2014-06-27 20:15:57 (GMT) |
| commit | 7c231a3d0d800bfc2602da097b34d1edca2f600f (patch) | |
| tree | 6b315019f78bc36afb1651796613324e6feecd7a /RELEASING | |
| parent | 6fa4beb8b991f7f22966df6c90ff776cac60c833 (diff) | |
| download | Ninja-7c231a3d0d800bfc2602da097b34d1edca2f600f.zip Ninja-7c231a3d0d800bfc2602da097b34d1edca2f600f.tar.gz Ninja-7c231a3d0d800bfc2602da097b34d1edca2f600f.tar.bz2 | |
mark this 1.5.0.git, update RELEASING
Diffstat (limited to 'RELEASING')
| -rw-r--r-- | RELEASING | 17 |
1 files changed, 9 insertions, 8 deletions
@@ -1,17 +1,18 @@ Notes to myself on all the steps to make for a Ninja release. Push new release branch: -1. update src/version.cc with new version (with ".git") -2. git checkout release; git merge master -3. fix version number in src/version.cc (it will likely conflict in the above) -4. fix version in doc/manual.asciidoc -5. commit, tag, push (don't forget to push --tags) -6. construct release notes from prior notes +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 +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) +7. construct release notes from prior notes credits: git shortlog -s --no-merges REV.. Release on github: -1. (haven't tried this yet) - https://github.com/blog/1547-release-your-software +1. https://github.com/blog/1547-release-your-software + Add binaries to https://github.com/martine/ninja/releases Make announcement on mailing list: 1. copy old mail |