During each of the release processes the release owner will be the touch point, has to be aware of possible SDK updates, new bugs etc...

When code freeze starts, the release owner has to perform this process, which will create the release branch from a baseBranch generating a new one with the format: release/vName.

• In Mobile UI library:

  • Create a release branch with the next release version name X.X.X-SNAPSHOT (ie:1.0.0-SNAPSHOT).
  • In develop increment release version name to the next one X.X.X-SNAPSHOT (ie: 1.0.1-SNAPSHOT).

• Launch Release start job in Github Actions with the parameters:

  • Use workflow from develop.
  • Release version name: the new release version X.X.X-RC (ie:3.1.0-RC).
  • Development version name: the next development version which will remain on develop X.X.X-DEV (ie: 3.1.1-DEV).

• In Capture app:

  • In release branch update mobile-ui version to it's release version with a pull request.
  • In develop branch update mobile-ui version to it's development version with a pull request.

• Launch Build Release Candidate job in Github Actions to generate Release Candidate APK and share it in #android-testing-troubleshooting slack channel.

• In Slack, in the #android-app-dev channel, write a message informing that the release has started.