Skip to content

Latest commit

 

History

History
40 lines (29 loc) · 1.41 KB

README_RELEASE.md

File metadata and controls

40 lines (29 loc) · 1.41 KB
Raw

OpenTracks: Developer information

Craft new releases

  1. Get next version code (main): git rev-list HEAD --count main
  2. Decide on version name (semantic versioning)
  3. Manually update version code and version name in build.gradle
  4. Create changelog (_version code_.txt)
  5. Create commit with all changes
  6. Tag newly create commit with version name (e.g., v3.2.1)
  7. Push commits and tags to public repository
  8. Add changelog to tag (Github releases)

F-Droid

Application id: de.dennisguse.opentracks

It if it properly tagged F-Droid takes care of building the app and publishing. Usually, it takes two days before the update is published (build, signed, and published).

The recent build activity can be found here

Google Play Store

Application id: de.dennisguse.opentracks.playstore

Requirement: gem install fastlane

  1. Build signed apk (requires keystore)
  2. Upload signed apk to Google Play Console
  3. Update store meta data (e.g., description and screenshots) fastlane metadata (requires API key configured in Appfile)

Supported languages: https://support.google.com/googleplay/android-developer/table/4419860

Translations (localization)

Translations of the OpenTracks are handled in Weblate: https://hosted.weblate.org/projects/opentracks/ .