upstream-mirrors/OpenTracks
1
0
Fork 1
mirror of https://codeberg.org/OpenTracksApp/OpenTracks.git synced 2026-10-11 21:43:05 +02:00
Code Issues Packages Projects Releases Wiki Activity

Reproducible build: update release documentation.

Browse Source 
Part of #418.
This commit is contained in:
Dennis Guse
2024-12-27 16:31:58 +01:00
parent df0d3ce600
commit 3ce0e2cede
1 changed files with 19 additions and 27 deletions
Download Patch File Download Diff File Expand all files Collapse all files
README_RELEASE.md
+19 -27
View File
@@ -2,39 +2,31 @@
## Craft new releases ## Craft new releases
1. Get next _version code_ (main): `git rev-list HEAD --count main` 1. Execute use `RELEASE.sh`.
2. Decide on _version name_ (semantic versioning) 2. Push to Github
3. Manually update _version code_ and _version name_ in `build.gradle` 3. Create release on Github (incl. changelog)
4. Create changelog (`_version code_.txt`) This actually creates a tag that is later used by F-Droid
5. Create commit with all changes 4. Pull from Github
6. Tag newly create commit with _version name_ (e.g., v3.2.1) 5. Build reproducible release and attach to release
7. Push commits and tags to public repository 6. ... wait until reproducibility is verified by F-Droid
8. Add changelog to tag (Github releases)
## F-Droid Two releases will be created:
Application id: de.dennisguse.opentracks * Application id: `de.dennisguse.opentracks` (irreproducible)
* Application id: `de.dennisguse.opentracks.playstore` (reproducible)
It if it properly tagged F-Droid takes care of building the app and publishing. For F-Droid the build status can be found [here](https://monitor.f-droid.org/builds/build).
Usually, it takes two days before the update is published (build, signed, and published).
The recent build activity can be found [here](https://monitor.f-droid.org/builds/build) ## Reproducible builds
## Google Play Store A lot of detailed information can be found [here](https://f-droid.org/docs/Reproducible_Builds/)
Application id: `de.dennisguse.opentracks.playstore`
Requirement: `gem install fastlane` Technical requirements:
* Must be build using OpenJDK17
1. Build signed apk
(requires keystore)
2. Upload signed apk to [Google Play Console](https://play.google.com/apps/publish)
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 (localization)
Translations of the OpenTracks are handled in Translations of the OpenTracks are handled in
Weblate: [https://hosted.weblate.org/projects/opentracks/](https://hosted.weblate.org/projects/opentracks) Weblate: [https://hosted.weblate.org/projects/opentracks/](https://hosted.weblate.org/projects/opentracks).
.
## Google Play Store
Supported languages: https://support.google.com/googleplay/android-developer/table/4419860