From e35798356b89ba49809f5621ccce9fd5bb447b95 Mon Sep 17 00:00:00 2001 From: Giuseppe Bilotta Date: Fri, 2 Jul 2010 13:32:42 +0200 Subject: 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 --- release-checklist | 16 ++++++++++++++++ 1 file changed, 16 insertions(+) create mode 100644 release-checklist 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 ). 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-.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 being released -- cgit v1.2.3