mirror of https://github.com/ArcaneChat/android.git synced 2026-07-03 14:05:24 +02:00

Files

T

bjoern e784b01f37 make tracking core versions easier (#2152 )

* nicer commit messasge on updating core

this sets the commit message for updating core module to sth. as
`update deltachat-core-rust submodule to 'prepare 1.68 (#2844)'`
instead of always the same message `update deltachat-core-rust submodule`.

this makes it easier to track changes.

* add a hint to release checklist to include the used core version

2021-11-28 20:16:14 +01:00

2.8 KiB

Raw Blame History

Release checklist - generate APK

on the command-line:

update core rust submodule, if needed: $ ./scripts/update-core.sh depending on how much you trust in rust, you might want to do a ./scripts/clean-core.sh before building
$ ./ndk-make.sh

this will take some time - meanwhile we're doing some housekeeping:

update translations and local help: $ ./scripts/tx-pull-translations.sh $ ./scripts/create-local-help.sh
a) 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 b) add used core version to CHANGELOG.md c) add a device message to ConversationListActivity::onCreate() or remove the old one

in Android Studio:

bump version in build.gradle, update both, versionCode and versionName
if ./ndk-make.sh from step 2. is finished successfully: a) select "Build / Generate signed APK" (not: App Bundle as this would require uploading the signing key) b) select flavor gplayRelease with V1 signature enabled (needed for easy APK verification), V2 is optional

on success, the generated APK is at gplay/release/deltachat-gplay-release-VERSION.apk

Upload APK to get.delta.chat

$ ./scripts/upload-release.sh VERSION
a) Test the APK yourself. The "Testing checklist" gives some hints. b) Give the APK to testing groups.

Release on Play Store

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

a) open "Delta Chat/Release/Production" then "Create new release" and upload APK from above b) fill out "Release details/Release notes" (500 characters max), release name should be default ("123 (1.2.3)") c) click "Save" and then "Review release" d) rollout to 20% by default is fine

Release new F-Droid version

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 new Amazon Appstore version

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

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

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

2.8 KiB Raw Blame History