summaryrefslogtreecommitdiff
diff options
context:
space:
mode:
authorGiuseppe Bilotta <giuseppe.bilotta@gmail.com>2010-07-02 13:32:42 +0200
committerGiuseppe Bilotta <giuseppe.bilotta@gmail.com>2010-07-02 13:32:42 +0200
commite35798356b89ba49809f5621ccce9fd5bb447b95 (patch)
treeaa4dd5de37d7ba5b6e1f6ab538e648ca9b143511
parent25e644cd2e226e624579149400207a9d003a32a2 (diff)
Release checklist
We sometimes skip releases for such a long time that we forget what exactly we have to do, and in what order. Let's keep this list in view and up-to-date
-rw-r--r--release-checklist16
1 files changed, 16 insertions, 0 deletions
diff --git a/release-checklist b/release-checklist
new file mode 100644
index 00000000..3b5473d3
--- /dev/null
+++ b/release-checklist
@@ -0,0 +1,16 @@
+Pre-release checklist:
+ * Update .po files (rake updatepo). Remember to add any new po(t) files.
+
+Release checklist:
+ * prepare a changelog from git shortlog
+ * tag the release with (./tag-release <version>). The script takes care of everything, including building the package
+ * git push, with tags
+ * upload packages to website's download folder
+ * update milestones and versions on the website
+ * prepare announcement on the website (use the changelog prepared before)
+ * change the website front page
+ * update the IRC topic
+ * [jsn] upload the gem (gem push rbot-<version>.gem)
+ * [jsn] update release info on rubyforge (needs release notes and changelog, take from announcement)
+ * [jsn] update release info on freshmeat (needs changes summary, see above)
+ * write a journal entry on ohloh.net about #rbot <version> being released