Skip to content

Latest commit

 

History

History
37 lines (22 loc) · 1.27 KB

RELEASE-PROCESS.md

File metadata and controls

37 lines (22 loc) · 1.27 KB
Raw

Creating a Release

Assume all feature branches have been merged into the develop branch (including an updated CHANGELOG).

  1. Pull develop and master branches from github.

  2. Ensure babble-go version in the babble build.gradle file is a released version of babble-go. If it isn't (i.e. it references a git commit) then check if there is a suitable release. If there is, adjust the babble-go version, run all the tests and create a commit.

  3. Merge develop into master (this should be a fast forward merge)

  4. Run all tests, confirm they pass. If they pass, a release can be created.

  5. Update the CHANGELOG - replace "UNRELEASED" with version and date e.g. "v0.6.0 (December 20, 2019)".

  6. Update version, versionName and versionCode in the babble build.gradle file. NOTE: there are THREE parameters here, all of which must be incremented.

  7. Update versionName and versionCode in the sample build.gradle.

  8. Update the version number in the Quickstart section of README.md.

  9. Create a git commit - e.g. "Bumped version to 0.2.6".

  10. Create a git tag e.g. "v0.2.6"

  11. Merge master into develop (this should be a fast forward merge).

  12. Push the develop and master branches and tags to github.

  13. Upload to bintray gradlew bintrayUpload.

  14. Upload sample app to Google Play.