https://github.com/orgs/organicmaps/discussions/4515
Weblate works fine. There is no longer a need to maintain a
homegrown, non-standard translation toolchain.
Categories are not in Weblate yet, but they weren't supported by
the previous toolkit too. This issue can be addressed later.
Signed-off-by: Roman Tsisyk <roman@tsisyk.com>
1. Restore the original simple version of `configure.sh`
Restores 08e37f4 "Refactor configure.sh"
Reverts b87ee95b "Fixed configure.sh script and gh actions"
2. Use GitHub Secrets instead of a private git repository to enhance
security standards and ensure credentials are encrypted and safely
managed.
3. Document credentials used by GitHub Actions in docs/CREDENTIALS.md
4. Include `network_security_config.xml` directly into the repo
as it has nothing sensitive.
5. Include Apple WWDR intermediate certificates directly into the repo
as they are not sensitive and publicly available.
https://developer.apple.com/help/account/reference/wwdr-intermediate-certificates
6. Add `private.h` in the repository since it does not differ from
`private_defaults.h`.
Signed-off-by: Roman Tsisyk <roman@tsisyk.com>
Tag Android with `YYYY.MM.DD-x-android` instead of `YYYY.MM.DD-x-android`
to trigger F-Droid pipeline when the release candidate is published.
It typically takes 4-5 days for F-Droid to process submissions. Any
defective release candidates can be withdrawn from the queue by submitting
a merge request to fdroid/data.
Note: Published GitHub releases are still tagged as "pre-release".
See 9520fd8c "Update the Google Play release procedure"
See https://gitlab.com/fdroid/fdroiddata/-/merge_requests/15000
Signed-off-by: Roman Tsisyk <roman@tsisyk.com>
Allows to test how fonts are rendered on Linux.
Setting QT_QPA_PLATFORM=offscreen environment var is required on non-GUI servers.
Signed-off-by: Alexander Borsuk <me@alex.bio>
Before all new Google Play releases were published for phased 10% rollout
in the Production track. Now, a new Google Play release is initially
uploaded into "Closed Beta" track for 100% rollout and then promoted into
"Production" track after testing. The "Closed Beta" track (misleadingly
called "alpha" in the code) is invite-only and currently contains about
~1k users imported Firebase App Tester databases. Invited users can opt in
to install new pre-release versions for testing directly via Google Play.
Android releases are now initially tagged with `YYYY.MM.DD-x-android-rc`
(release-candidate) tags instead of `YYYY.MM.DD-x-android`. The production
`YYYY.MM.DD-x-android` tag is added after promotion in Google Play. This
kicks-off the F-Droid process as well. Huawei's version remains unpublished
until Android gets a green light in Google Play.
This change has two primary outcomes:
1. Users now can receive pre-production ("rc") via Google Play.
This change uses invite-only "Closed Beta" track, but it can be
changed to "Open Beta" track later.
2. Android versions in Google Play are now published after pre-production
testing in a separate track in Google Play. Meanwhile, Google Play
runs Monkey for free in such tracks and sends useful pre-prod reports.
There are no changes in Firebase App Tester - it works as usual. The primary
difference between App Tester and Google Play Open/Closed Beta is that
AppTester uses "app.organicmaps.beta" applicationId while Google Play uses
"app.organicmaps" id. This efficiently means that versions from App Testers
can be installed in parallel with Google Play, while Google Play's
Open/Closed version update the production app.
Please don't get confused with the word "beta" used in different places.
Google Play Open/Closed Beta actually will receive only pre-production
quality builds. App Tester probably can continue to be used both for
pre-production and ad-hoc experiemental version ("alpha"?).
Signed-off-by: Roman Tsisyk <roman@tsisyk.com>
The debug mode occasionally fails on random asserts which are not very
critical for the production. The debug mode also does not have R8 enabled,
which causes certain bugs to leak into production. Use Beta instead.
This PR also removes virtual x86_64 devices from the list because they fail
randomly during rendering due to inconsistency of OpenGL emulation.
Signed-off-by: Roman Tsisyk <roman@tsisyk.com>
