yetangitu/deltachat
1
0
Fork 0
mirror of https://github.com/deltachat/deltachat-android.git synced 2025-10-03 01:39:18 +02:00
Code Issues Releases Wiki Activity
deltachat/RELEASE.md

5.4 KiB
Raw Blame History

Android Release Checklist

Generate APKs

  1. update core:

    ./scripts/update-core.sh               # shows used branch
./scripts/update-core.sh BRANCH_OR_TAG # update to tag or 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"):

  1. update CHANGELOG.md from https://github.com/deltachat/deltachat-core-rust/blob/main/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.
    in case previous entries of the changelog refer to betas or to not officially released versions, the entries can be summarized. this makes it easier for the end user to follow changes by showing major changes atop

  2. 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.

  3. bump versionCode and versionName (no leading "v") in build.gradle

  4. 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

  1. 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.

  1. 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/:

  1. a) open "Delta Chat/Release/Production" then "Create new release" and upload APK from above
    b) fill out "Release details/Release notes" (500 chars), add the line "These features will roll out over the coming days. Thanks for using Delta Chat!"; 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

  1. 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.

  2. 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:

  1. a) for "Delta Chat", select "Add upcoming version" on the left b) at "Step 1 / Existing file(s)" hit "Replace", upload the APK from above c) on the "Step 1" page, add "Release notes" from CHANGELOG.md, hit "Next" d) on "Step 2" page: "Does your app collect or transfer user data to third parties?" -> No, then "Next" e) on "Step 3" page: "Next" f) on "Step 4" page: "Submit app"

Release on Huawei AppGallery

on https://developer.huawei.com/consumer/en/appgallery:

  1. a) go to "Upload your app / Android / Delta Chat / Update", again "Update" upper right b) "Manage Packages / Upload", upload the APK from above c) Update "App Information / New Features" d) Hit "Submit"; on the next page, confirm version and language

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