Deployment Process

Deferred release management and CI is mostly handled by Fastlane. See our README for a current list of commands.

Release Strategy

1. Releases generally happen off master. Prerelease versions can happen off a prerelease branch, but not a feature branch.
2. Bump the version number:
   • For a prerelease: bundle exec fastlane bump_version pre:beta.4
     • Prerelease tags are tag.n according to semver, such as rc.1 or beta.8
   • For a release: bundle exec fastlane bump_version bump:minor
     • These may be combined. Bumps of major, minor, and patch are supported.
3. Commit and pull request that change onto the target branch.
4. One merged, create a new GitHub Release pointing to the tip of the target branch.
   • Tag names should be the semantic version name output by bump_version, such as 3.0.0 or 2.7.1-beta.1. Note there is no prefixing v.
   • Give a descriptive version title, such as "v4.0 Beta 2: You're A Smart Developer"
   • Provide useful release notes citing the issue and PR numbers where necessary.
   • Make sure a prerelease version is marked as such.
5. git pull locally.
6. pod trunk push