# Android Release Checklist


## Generate APKs

1. update core:
   ```
   ./scripts/update-core.sh        # shows used branch
   ./scripts/update-core.sh BRANCH # update to latest commit of branch
   ./scripts/clean-core.sh         # helps on weird issues, do also "Build / Clean"
   ./scripts/ndk-make.sh
   ```

2. update translations and local help:
   ```
   ./scripts/tx-pull-translations.sh
   ./scripts/create-local-help.sh  # requires deltachat-pages checked out at ../deltachat-pages
   ```

the following steps are done in a PR called `prep-VERSION` (no leading "v"):

3. update `CHANGELOG.md`
   from <https://github.com/deltachat/deltachat-core-rust/blob/master/CHANGELOG.md>
   and <https://github.com/deltachat/deltachat-android/pulls?q=is%3Apr+is%3Aclosed+sort%3Aupdated-desc>.
   avoid technical terms, library versions etc. the changelog is for the end user.
   do not forget to update/mention used core version and release month.

4. add a device message to `ConversationListActivity::onCreate()` or remove the old one.
   do not repeat the CHANGELOG here: write what really is the ux outcome
   in a few lines of easy speak without technical terms.
   if there is time for a translation round, do `./scripts/tx-push-source.sh`
   **ping tangible translators** and start over at step 2.

5. bump `versionCode` _and_ `versionName` (no leading "v") in `build.gradle`

6. build APKs:
   a) generate debug APK at "Build / Build Bundle(s)/APK / Build APK(s)"  
   b) generate release APK at "Build / Generate Signed Bundle or APK",
      select "APK", add keys, flavor `gplayRelease`


## Push Test Releases

7. a) `./scripts/upload-beta.sh VERSION` uploads both APKs to testrun.org and drafts a message.  
   b) add things critically to be tested to the message (this is not the changelog nor the device message)  
   c) post the message to relevant testing channels, **ping testers**  
   d) make sure, the `prep-VERSION` PR **gets merged**

On serious deteriorations, **ping devs**, make sure they get fixed, and start over at step 1.


## Release on get.delta.chat

Take care the APK used here and in the following steps
are binary-wise the same as pushed to testers and not overwritten by subsequent builds.

8. a) `./scripts/upload-release.sh VERSION`  
   b) do a PR to bump `VERSION_ANDROID` (without leading `v`) on
      `https://github.com/deltachat/deltachat-pages/blob/master/_includes/download-boxes.html`  
   c) make sure, **the PR gets merged**
      and the correct APK is finally available on get.delta.chat

only afterwards, push the APK to stores. **consider a blog post.**


## Release on Play Store

on <https://play.google.com/apps/publish/>:

9. a) open "Delta Chat/Release/Production"
      then "Create new release" and upload APK from above  
   b) fill out "Release details/Release notes" (500 characters, summary can be reused for F-Droid),
      release name should be default ("123 (1.2.3)")  
   c) click "Next", set "Rollout Percentage" to 1% (later 2%, 5%, 10%, 20%, 50%, 100%),
      click "Start rollout to Production"


## Release on F-Droid

10. Add "4" at the end of versionCode to calculate F-Droid version code number.
    E.g. for versionCode 456 you get number 4564
    (this version conversion is due to `VercodeOperation` in
    <https://gitlab.com/fdroid/fdroiddata/blob/master/metadata/com.b44t.messenger.yml>
    metadata file, see <https://f-droid.org/docs/Build_Metadata_Reference/#VercodeOperation> for
    documentation)  
    Add `metadata/en-US/changelogs/4564.txt` file with a changelog for F-Droid.
    The changelog must not be longer than 500 characters.

11. make sure, everything is pushed, then:  
    $ git tag v1.2.1; git push --tags
    
F-Droid picks on the tags starting with "v" and builds the version.
This may take some days.


## Release on Amazon Appstore

on <https://developer.amazon.com/dashboard>:

12. a) for "Delta Chat", select tab "Add upcoming version"  
    b) at "App Information" hit "Edit" abottom and then "Replace APK" atop,
       upload the APK from above
    c) on the same tab, add "Release notes" from CHANGELOG.md, "Save"  
    d) hit "Submit app" at the upper right corner


## Releases on Apklis, Passkoocheh

These stores are not under our control.
On important updates **ping store maintainers** and ask to update.


## Testing checklist

Only some rough ideas, ideally, this should result into a simple checklist
that can be checked before releasing.
However, although it would be nice to test "everything", we should keep in mind
that the test should be doable in, say, 10~15 minutes.
- create new account with (one of?): gmail, yandex, other
  or (?) test an existing account
- send and receive a message
- create a group
- do a contact verification
- join a group via a qr scan
