mnalis/apps-android-commons
1
0
Fork 0
mirror of https://github.com/commons-app/apps-android-commons.git synced 2025-10-26 20:33:53 +01:00
Code Issues Projects Releases Packages Wiki Activity Actions 1

Updated the RELEASE-CHECKLIST

Browse source
This commit is contained in:
YuviPanda 2013-04-26 23:09:40 +05:30
parent d9b19fd54b
commit 2602f60be4
1 changed files with 5 additions and 3 deletions
Download patch file Download diff file Expand all files Collapse all files

8
RELEASE-CHECKLIST.md
View file

@ -2,10 +2,12 @@ To prevent sad pandas, please check the following items before making a release:
- Make sure that the APP POINTS TO COMMONS. This is very important, and should be - Make sure that the APP POINTS TO COMMONS. This is very important, and should be
ensured. The variables to check are `API_URL`, `IMAGE_URL_BASE`, `HOME_URL` and ensured. The variables to check are `API_URL`, `IMAGE_URL_BASE`, `HOME_URL` and
`EVENTLOG_WIKI`, in `CommonsApplication.java`. Preferred way to do this is to have `EVENTLOG_WIKI`, in `CommonsApplication.java`. There is a patch for this named
a staved `git stash` that applies these, and then apply them (and make a branch) `upload-to-commons.patch` in the root directory
before pushing them out
- Check for database schema migrations. If you modified the `DATABASE_VERSION` in - Check for database schema migrations. If you modified the `DATABASE_VERSION` in
`DBOpenHelper`, ensure that you have appropriately written recursive migrations `DBOpenHelper`, ensure that you have appropriately written recursive migrations
in your appropriate `onUpgrade` methods. **Test** this before pushing out! You in your appropriate `onUpgrade` methods. **Test** this before pushing out! You
only need to test from the last database version, so should not be that hard! 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 <apk>` to install
it different versions of it.
- Bump the version numbers in AndroidManifest.xml