F-Droid: submit to fdroiddata and fix release-tag versionCode hygiene #143

Open
opened 2026-07-02 15:55:07 +00:00 by JMR-dev · 0 comments
JMR-dev commented 2026-07-02 15:55:07 +00:00 (Migrated from github.com)

The F-Droid groundwork is done (#16, merged): fastlane metadata (fastlane/metadata/android/en-US/), the license audit + anti-feature review (none to declare) in docs/fdroid-compliance.md, and an fdroiddata metadata template at docs/fdroid/org.libremail.app.yml. F-Droid builds from source and signs its own builds, so there is no keystore/upload step. This ticket tracks the remaining human submission steps.

Steps (human)

  • Fix version-tag hygiene: #16 found tags v0.1.0 and v0.2.0 both map to versionCode 1. F-Droid's tag-based UpdateCheckMode needs a versionCode bump per release tag — establish the scheme and cut a clean tagged release (shared with the signing/versioning ticket).
  • Verify a clean-room build from the tag yields an installable APK with no secrets.properties (confirmed in docs/fdroid-compliance.md §3) and no proprietary/Google/Firebase deps.
  • Fork fdroiddata, add metadata/org.libremail.app.yml from the committed template (docs/fdroid/org.libremail.app.yml); run fdroid readmeta, fdroid lint, and a local test build.
  • Open the merge request to fdroiddata (the RFP / packaging request) and respond to reviewer feedback until accepted.
  • (Optional) Add F-Droid listing graphics/screenshots under fastlane/metadata/android/en-US/images/.

Acceptance

  • App accepted into fdroiddata and building on F-Droid's pipeline with the documented anti-feature list (ideally none).

Dependencies

Groundwork #16 (done). Independent of the signing/secrets ticket (F-Droid signs its own builds).

The F-Droid **groundwork is done** (#16, merged): fastlane metadata (`fastlane/metadata/android/en-US/`), the license audit + anti-feature review (none to declare) in `docs/fdroid-compliance.md`, and an fdroiddata metadata **template** at `docs/fdroid/org.libremail.app.yml`. F-Droid builds from source and signs its own builds, so there is **no keystore/upload step**. This ticket tracks the remaining **human** submission steps. ## Steps (human) - [ ] Fix version-tag hygiene: #16 found tags `v0.1.0` and `v0.2.0` both map to `versionCode 1`. F-Droid's tag-based UpdateCheckMode needs a **versionCode bump per release tag** — establish the scheme and cut a clean tagged release (shared with the signing/versioning ticket). - [ ] Verify a **clean-room build** from the tag yields an installable APK with no `secrets.properties` (confirmed in `docs/fdroid-compliance.md` §3) and no proprietary/Google/Firebase deps. - [ ] Fork **fdroiddata**, add `metadata/org.libremail.app.yml` from the committed template (`docs/fdroid/org.libremail.app.yml`); run `fdroid readmeta`, `fdroid lint`, and a local test build. - [ ] Open the **merge request** to fdroiddata (the RFP / packaging request) and respond to reviewer feedback until accepted. - [ ] (Optional) Add F-Droid listing graphics/screenshots under `fastlane/metadata/android/en-US/images/`. ## Acceptance - App accepted into fdroiddata and building on F-Droid's pipeline with the documented anti-feature list (ideally none). ## Dependencies Groundwork #16 (done). Independent of the signing/secrets ticket (F-Droid signs its own builds).
Sign in to join this conversation.
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: JMR-dev/LibreMail#143