Release process

As the release process is getting more and more complex, here is a handy list to assist any person performing it:

• Update the translations from Crowdin
  • Upload new strings for translation
  • Download translations made since the last build
• Update the version number in build.gradle
• Update the changelog in the app.
• Build the new signed .apk for distribution
• Create a new Tag in source control after committing all changes, naming it the next version number.

Publishing the binaries

The app is to be published on

• Releases on GitHub: create a Release on GitHub with the latest .apk file. Copy the changelog items.
• Google Play (developer console)
• Amazon (developer console)
• Update the demo app with the latest build.

Release Notes

• Milestone on GitHub. Set the current version number in the version page on GitHub. A version contains all the linked issues on GitHub.
• Twitter
• www.moneymanagerex.org

Schedule

The suggested release schedule is

• weekly, for Beta versions
• monthly, for Release versions but it will depend on the number and type of changes contained.