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

Files

T

bjoern eb1a544e93 bump to 1.26.2 (#2159 )

* bump to 1.26.2 using core70

(1.26.0 and 1.26.1 were not released,
however, there may be nightlies or other builds around)

* adapt release-checklist.md to new VERSION_ANDROID on deltachat-pages

* even more release-checklist hints

2021-12-02 01:13:37 +01:00

3.1 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 c) if you want to use upload-testrun.sh, generate a debug apk additionally at "Build / Build Bundle(s)/APK / Build APK(s)"

on success, the generated APK is at gplay/release/deltachat-gplay-release-VERSION.apk and can be uploading for testing using: $ ./scripts/upload-testrun.sh VERSION The "Testing checklist" gives some hints about what should be always tested.

Upload APK to get.delta.chat

$ ./scripts/upload-release.sh VERSION
bump VERSION_ANDROID (without leading v) on https://github.com/deltachat/deltachat-pages/blob/master/_includes/download-boxes.html

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

3.1 KiB Raw Blame History