The following Cover Mobile Development for both iOS and Android SimplyE Apps
GitFlow
1. Run Ktlint
2. Create feature branch using task number
3. Create pull request
4. Complete pull request template
5. Github tags
6. Single approval
QA Process
Release Process
Mobile Release Process v1.2
Last edited: 2/12/2019
In an effort to standardized the mobile release process, follow the steps below for a predictable rollout out new versions of SimplyE mobile applications.
Android
1. Get the sign off from QA for the build from QA Manager
2. Based on commit history, construct text to be shown in the Whats new field on Google Play. This text should be approved by Risa Wolf in Jira ticket.
3. Check with Risa Wolf to see if there are any new screenshots that should be added to the Google Play listing.
4. Increment version name and number, tag release branch in Github.
5. Run Fastlane commands to upload build to Goolge Play Beta , enter approved "Whats new" text and new approved screenshots. Use the the release version as the internal release name.
6. Resolve any new Google Play Console errors or warnings.
7. Run beta for 3 days, if there are issues, fix the issues and start again from Step 1 otherwise if there are no issues promote beta to production with Risa Wolf signing off.
8. Respond to any negative Google Play Store reviews where their specific issues have been addressed in the latest release.
iOS
1. Get the sign off from QA for the build from QA Manager
2. Based on commit history, construct text to be shown in the Whats new field on App Store. This text should be approved by Risa Wolf in a Jira ticket.
3. Check with Risa Wolf to see if there are any new screenshots that should be added to the App Store listing.
4. Increment the build number in Xcode and archive the project
5. Upload the app to the app store
6. Once the new build has completed processing, add the appropriate test group to the build, add the approved Whats new text as the test information, and Submit the app for review to notify the testers.
7. Expire any the previous TestFlight builds
8. Run beta for 3 days, if there are issues, fix the issues and start again from Step 1.
9. Run beta for 3 days, if there are no issues copy the approved "Whats new" text as the description, and check with Risa Wolf for any new screenshots that should be add to the App Store listing.
10. With Risa Wolf sign off, submit the tested build for review.
11. Respond to any negative App Store reviews where their specific issues have been addressed in the latest release.
