Mirrors/Unciv
1
0
Fork 0
mirror of https://github.com/yairm210/Unciv.git synced 2025-02-20 19:56:51 +01:00
Code Issues Packages Projects Releases Wiki Activity

Update From-code-to-deployment.md (#6638)

Browse Source 
Better link for the F-Droid Monitor and a hint what to expect
This commit is contained in:
SomeTroglodyte 2022-04-30 23:12:42 +02:00 committed by GitHub
parent ac2f31f553
commit f668f65bb3
No known key found for this signature in database
GPG Key ID: 4AEE18F83AFDEB23
1 changed files with 1 additions and 1 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

2
docs/Developers/From-code-to-deployment.md
View File

@ -32,7 +32,7 @@ When I'm ready to release a new version I:
- Send an announcement on the Discord server of the version release and release notes via webhook
- Pack, Sign, and Upload a new APK to the Google Play Console at 10% rollout
- The F-Droid bot checks periodically if we added a new tag. When it recognizes that we did, it will update the [yaml file here](https://gitlab.com/fdroid/fdroiddata/blob/master/metadata/com.unciv.app.yml)
- When the bot next runs and sees that there's a version it doesn't have a release for, it will attempt to build the new release. The log of the build will be added [here](https://monitor.f-droid.org/builds/running), and the new release will eventually be available [here](https://f-droid.org/en/packages/com.unciv.app/)
- When the bot next runs and sees that there's a version it doesn't have a release for, it will attempt to build the new release. The log of the build will be added [here](https://monitor.f-droid.org/builds/build) (search for Unciv, there's a log link like this: `https://monitor.f-droid.org/builds/log/com.unciv.app/<appCodeNumber>`), and the new release will eventually be available [here](https://f-droid.org/en/packages/com.unciv.app/)
## About Google Play publishing