diff options
| author | Evan Martin <martine@danga.com> | 2013-02-17 19:22:37 (GMT) |
|---|---|---|
| committer | Evan Martin <martine@danga.com> | 2013-02-17 19:22:37 (GMT) |
| commit | 52ae6ddb18c02fd06535574c265f4acc5b97dd4a (patch) | |
| tree | 077c8ccb85ad91fe18b4e37072503298ae29e8bd /RELEASING | |
| parent | d56f995ef0b86e46f87e596a87f16b4d636968f5 (diff) | |
| download | Ninja-52ae6ddb18c02fd06535574c265f4acc5b97dd4a.zip Ninja-52ae6ddb18c02fd06535574c265f4acc5b97dd4a.tar.gz Ninja-52ae6ddb18c02fd06535574c265f4acc5b97dd4a.tar.bz2 | |
add versioning notes to features in the manual
This helps guide which ninja version to depend on.
Diffstat (limited to 'RELEASING')
| -rw-r--r-- | RELEASING | 7 |
1 files changed, 4 insertions, 3 deletions
@@ -3,7 +3,8 @@ Notes to myself on all the steps to make for a Ninja release. 1. git checkout release; git merge master 2. fix version number in source (it will likely conflict in the above) 3. fix version in doc/manual.asciidoc -4. rebuild manual, put in place on website -5. commit, tag, push -6. construct release notes from prior notes +4. grep doc/manual.asciidoc for XXX, fix version references +5. rebuild manual, put in place on website +6. commit, tag, push +7. construct release notes from prior notes credits: git shortlog -s --no-merges REV.. |