This issue is about getting a Lockwise Android 4.0.2 out of the door. Lockwise is a little bit different than our other Android products and requires few manual steps. https://github.com/mozilla-lockwise/lockwise-android/blob/master/docs/releases.md I have already uploaded the signed build that Bitrise generates to the GitHub release: https://github.com/mozilla-lockwise/lockwise-android/releases/tag/release-v4.0.2 I think what needs to happen next is this: * RelMan manually uploads that APK to the Play Store and publishes to the Internal Test Track * QA Can do a sign off of this build * We promote the build as usual to the production track.
Bug 1677556 Comment 0 Edit History
Note: The actual edited comment in the bug view page will always show the original commenter’s name and original timestamp.
This issue is about getting a Lockwise Android 4.0.2 out of the door. Lockwise is a little bit different than our other Android products and requires few manual steps. https://github.com/mozilla-lockwise/lockwise-android/blob/master/docs/releases.md I have already uploaded the signed build that Bitrise generates to the GitHub release: https://github.com/mozilla-lockwise/lockwise-android/releases/tag/release-v4.0.2 I think what needs to happen next is this: * RelMan manually uploads that APK to the Play Store and publishes to the Internal Test Track * QA Can do a sign off of this build * We promote the build as usual to the production track. * Upload the `app-mapping.txt` in the "Android vitals" and "Deobfuscation files" section * Upload the `app-mapping.txt` and `AndroidManifest.xml` to Sentry I can take care of the Sentry configuration.