From 3b29af27d7f82ae2c620ad25e3f93e8a644abcac Mon Sep 17 00:00:00 2001 From: YuviPanda Date: Fri, 26 Apr 2013 23:21:57 +0530 Subject: [PATCH] More complete RELEASE-CHECKLIST! --- RELEASE-CHECKLIST.md | 12 +++++++++++- 1 file changed, 11 insertions(+), 1 deletion(-) diff --git a/RELEASE-CHECKLIST.md b/RELEASE-CHECKLIST.md index 4c088a0e7..eaba36bbf 100644 --- a/RELEASE-CHECKLIST.md +++ b/RELEASE-CHECKLIST.md @@ -10,4 +10,14 @@ To prevent sad pandas, please check the following items before making a release: only need to test from the last database version, so should not be that hard! Do this on the final signed APK. You can use `adb install -r ` to install it different versions of it. -- Bump the version numbers in AndroidManifest.xml +- Bump the version numbers in `AndroidManifest.xml`. `versionCode` is monotonically + increasing integers. `versionName` is descriptive string for this version. +- Add the new release to the `CHANGELOG`. Make sure that the `CHANGELOG` additions + and the `AndroidManifest.xml` additions go together on the same commit. +- Add an appropriately named git tag, such as `v1.0beta8`. Don't forget to push + it to the repo :) +- Upload the new APK to the store using the dev console. Also modify the Changelog + in the store listing to contain changes for the last two releases. +- Email mobile-l with release announcement - short description of major new features + and then a copy of the CHANGELOG. Forward that to commons-l and wikitech-l with + a pithy note about how nobody reads mobile-l.