Skip to content

Latest commit

 

History

History
17 lines (17 loc) · 1.18 KB

RELEASING.md

File metadata and controls

17 lines (17 loc) · 1.18 KB

Releasing

When a release branch is ready to be merged into master and in turn deployed to the Play Store. In the release branch:

  1. Update CHANGELOG.md
  • Add title with the release versionName
  • Add list of commits since last release in date descending order, not including any merge commits or release notes related commits
  1. Update listing metadata with what was added to CHANGELOG.md
  2. Commit changes git commit -am '{versionName} release notes'
  3. Create a PR into master, review, merge and close the old release branch if all is OK
  4. Create a new release branch off latest master git checkout -b {versionName}
  5. Bump versionName in app/build.gradle to match new branch name
  6. Update previous CHANGELOG.md entry to append title with the build commit of that release
  7. Commit changes git commit -am 'bump versionName and add commit hash to {versionName} release notes'
  8. Tag and push
  • If the build was a public release tag its build commit git tag -a {versionName} {previous merge commit}
  • Push it git push && git push --tags
  1. Branch off here to work on feature relevant to this release