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
The release process today can be a bit confusing; challenges come up because we have two different platforms that are not always in sync (iOS/Android), and both of those require approvals from the Apple App Store and the Google Play Store, respectively. The Release processes, along with some other technical documentation, can be found by the Mobile team here.
Pre-Release Steps
Three to five working days before the targeted release date, depending on the size of the release (bug fix or feature), a code freeze goes into effect where no new additions are added to the codebase.
After all tickets for the release have been merged into develop, create a new release branch, e.g. git checkout -b release/3.6.0 and push it upstream.
Verify all unit tests are passing
Verify all tickets have been moved into the Ready for QA state in Jira. The completed tickets serve as the basis for QA release notes notifying QA of what tickets should be tested.
Create pull request against master from the release branch.
Create QA build/release candidate and upload to Firebase, Google notifies testers that the build is available
(iOS Only) Stage release candidate in App Store Connect and set to manual release
Current State Release Steps
iOS
Get the sign off from QA for the build from Joseph Dalton
Based on commit history and completed Jira tickets, construct text to be shown in the What’s new field in the App Store. This text should be approved by Risa Wolf in Jira ticket or official email for visibility.
Check with Risa Wolf to see if there are any new screenshots that should be added to the App Store listing.
Add the approved Whats new text to the App Store listing.
With product team approval, manually release previously approved production build in the App Store.
Notify #Simplified channel in the NYPL Digital Slack workspace that the release has gone out.
Android
Get the sign off from QA for the build from Joseph Dalton
Based on commit history and completed Jira tickets, construct text to be shown in the What’s new field on Google Play. This text should be approved by Risa Wolf in Jira ticket or official email for visibility.
Check with Risa Wolf to see if there are any new screenshots that should be added to the Google Play listing.
Increment version name and number, tag release branch in Github.
With product team approval, run Fastlane commands to upload the build to Google Play, enter approved Whats new text and any new approved screenshots. Use the release version as the internal release name.
Resolve any new Google Play Console errors or warnings.
Notify #Simplified channel in the NYPL Digital Slack workspace that the release has gone out.
Post Release
Merge release branch into master
Monitor Crashlytics
Monitor email error reports
Respond to any negative Google Play Store / Apple App Store reviews where their specific issues have been addressed in the latest release.
