Release Testing Process: Info for Mobile Developers

When we're cutting a release, it's important for us to do what we can to make sure everything works.

Here are suggested procedures for mobile:

1. Follow the instructions in Building for Release until there is an iOS ipa on TestFlight and an apk/aab in Beta Release for Android.
2. Write a message to the #mobile channel in Slack explaining that the release is available. Include the version number there, so folks can make sure they get the right one down. Ask everyone in the channel to please pull down the latest. Tell them what changes to look for.
3. If these people find something wrong, they should open an issue with the Bug Report template here. That template includes a checklist for all the information that should be in the issue to reproduce any problems.
4. Folks should label their issue with the mobile app release number (for example, 2.6.1).
5. After a day or two of this, the mobile dev can go in, check on these issues, determine which ones are related to the new code and/or which must be addressed immediately, and remove the mobile app release number label from all the others.
6. The mobile dev can then begin work on the remaining labeled issues and re-upload to TestFlight and Android Beta.

Repeat these steps until the app is satisfactory, at which point we promote Android to prod and request manual review in iOS.