From b35a09906cd118feffa7bb07bdab4754d75c2e86 Mon Sep 17 00:00:00 2001 From: Benoit Marty Date: Wed, 8 Jun 2022 10:23:19 +0200 Subject: [PATCH 1/3] Add checks to give the status of the PlayStore submission. --- .github/ISSUE_TEMPLATE/release.yml | 2 ++ 1 file changed, 2 insertions(+) diff --git a/.github/ISSUE_TEMPLATE/release.yml b/.github/ISSUE_TEMPLATE/release.yml index 7cb47fa952..63c5420051 100644 --- a/.github/ISSUE_TEMPLATE/release.yml +++ b/.github/ISSUE_TEMPLATE/release.yml @@ -54,6 +54,7 @@ body: - [ ] Copy the fastlane change to the GooglePlay console in the section en-GB. - [ ] Push to beta release to 100% of the users - [ ] Notify the F-Droid team so that they can schedule the publication on F-Droid + - [ ] The application is available to the PlayStore testers (live). Google can take between 1 hour and up to 7 days to approve the release. ### Once Live on PlayStore @@ -67,6 +68,7 @@ body: - [ ] Check the Android Element room for any reported issues on the new version - [ ] If all is OK, push to production and notify Markus (Bubu) to release the F-Droid version - [ ] Ping the Android public room and update its topic with the new available version + - [ ] The application is available to the PlayStore users (live). Google can take (again!) between 1 hour and up to 7 days to approve the release. ### Android SDK2 From 78da5017a94b243478923ba8b506ed18a0b055cb Mon Sep 17 00:00:00 2001 From: Benoit Marty Date: Wed, 8 Jun 2022 10:26:56 +0200 Subject: [PATCH 2/3] Update about the F-Droid release flow. --- .github/ISSUE_TEMPLATE/release.yml | 9 +++++++-- 1 file changed, 7 insertions(+), 2 deletions(-) diff --git a/.github/ISSUE_TEMPLATE/release.yml b/.github/ISSUE_TEMPLATE/release.yml index 63c5420051..7ee99196a4 100644 --- a/.github/ISSUE_TEMPLATE/release.yml +++ b/.github/ISSUE_TEMPLATE/release.yml @@ -53,20 +53,25 @@ body: - [ ] Check that the version codes are correct - [ ] Copy the fastlane change to the GooglePlay console in the section en-GB. - [ ] Push to beta release to 100% of the users - - [ ] Notify the F-Droid team so that they can schedule the publication on F-Droid + - [ ] Notify the F-Droid team [here](https://matrix.to/#/!LAAuJLQXYHjMNWKrCK:matrix.org?via=matrix.org&via=bubu1.eu&via=lant.uk) so that they can schedule the publication on F-Droid - [ ] The application is available to the PlayStore testers (live). Google can take between 1 hour and up to 7 days to approve the release. + - [ ] The application is available to the F-Droid users. ### Once Live on PlayStore - [ ] Ping the Android public room and update its topic - [ ] Add an entry in the internal diary + ### Once Live on F-Droid + + - [ ] Update the Android public room topic + ### After at least 2 days - [ ] Check the [rageshakes](https://github.com/matrix-org/element-android-rageshakes/issues) - [ ] Check the crash reports on the GooglePlay console - [ ] Check the Android Element room for any reported issues on the new version - - [ ] If all is OK, push to production and notify Markus (Bubu) to release the F-Droid version + - [ ] If all is OK, push to production - [ ] Ping the Android public room and update its topic with the new available version - [ ] The application is available to the PlayStore users (live). Google can take (again!) between 1 hour and up to 7 days to approve the release. From 0b3dfab9510c9c290fb7a4e7b18681a8ded97908 Mon Sep 17 00:00:00 2001 From: Benoit Marty Date: Wed, 8 Jun 2022 10:45:26 +0200 Subject: [PATCH 3/3] "beta" -> "open testing" PlayStore terminology and move step to update the topic once production is live to a dedicated section. Also update the diary only when production is live. --- .github/ISSUE_TEMPLATE/release.yml | 17 ++++++++++------- 1 file changed, 10 insertions(+), 7 deletions(-) diff --git a/.github/ISSUE_TEMPLATE/release.yml b/.github/ISSUE_TEMPLATE/release.yml index 7ee99196a4..f012900752 100644 --- a/.github/ISSUE_TEMPLATE/release.yml +++ b/.github/ISSUE_TEMPLATE/release.yml @@ -49,32 +49,35 @@ body: ### Once tested and validated internally - - [ ] Create a new beta release on the GooglePlay console and upload the 4 signed Apks. + - [ ] Create a new open testing release on the GooglePlay console and upload the 4 signed Apks. - [ ] Check that the version codes are correct - [ ] Copy the fastlane change to the GooglePlay console in the section en-GB. - - [ ] Push to beta release to 100% of the users + - [ ] Push the open testing release to 100% of the users - [ ] Notify the F-Droid team [here](https://matrix.to/#/!LAAuJLQXYHjMNWKrCK:matrix.org?via=matrix.org&via=bubu1.eu&via=lant.uk) so that they can schedule the publication on F-Droid - [ ] The application is available to the PlayStore testers (live). Google can take between 1 hour and up to 7 days to approve the release. - [ ] The application is available to the F-Droid users. - ### Once Live on PlayStore + ### Once open testing is live on PlayStore - [ ] Ping the Android public room and update its topic - - [ ] Add an entry in the internal diary ### Once Live on F-Droid - [ ] Update the Android public room topic - ### After at least 2 days + ### After at least 2 days (generally next Monday) - [ ] Check the [rageshakes](https://github.com/matrix-org/element-android-rageshakes/issues) - [ ] Check the crash reports on the GooglePlay console - [ ] Check the Android Element room for any reported issues on the new version - - [ ] If all is OK, push to production - - [ ] Ping the Android public room and update its topic with the new available version + - [ ] If all is OK, promote the open testing release to production. Generally using a 100% roll out, but can be a smaller value depending on the release content. - [ ] The application is available to the PlayStore users (live). Google can take (again!) between 1 hour and up to 7 days to approve the release. + ### Once production is live on PlayStore + + - [ ] Ping the Android public room and update its topic + - [ ] Add an entry in the internal diary + ### Android SDK2 The SDK2 and the sample app are released only when Element has been pushed to production.