summaryrefslogtreecommitdiff
path: root/ninja/RELEASING
diff options
context:
space:
mode:
Diffstat (limited to 'ninja/RELEASING')
-rw-r--r--ninja/RELEASING18
1 files changed, 14 insertions, 4 deletions
diff --git a/ninja/RELEASING b/ninja/RELEASING
index 1110f0b57b0..25926dbc6aa 100644
--- a/ninja/RELEASING
+++ b/ninja/RELEASING
@@ -1,12 +1,22 @@
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. rebuild manual, put in place on website
-6. commit, tag, push (don't forget to push --tags)
-7. construct release notes from prior notes
+5. commit, tag, push (don't forget to push --tags)
+6. construct release notes from prior notes
credits: git shortlog -s --no-merges REV..
-8. update home page mention of latest version.
+Release on github:
+1. (haven't tried this yet)
+ https://github.com/blog/1547-release-your-software
+
+Make announcement on mailing list:
+1. copy old mail
+
+Update website:
+(note to self: website is now in github.com/martine/martine.github.io)
+1. rebuild manual, put in place on website
+2. update home page mention of latest version.