User Story
Currently, on F-Droid, for every new version of Probe, four separate releases are published. All have the correct version tag (e.g. 6.0.1), but are for different CPU architectures (x86, x86_64, armeabi-v7a, arm64-v8a):
Instead, these four should all be bundled into one release.
The problem with the current method is that F-Droid automatically marks the latest stable release as "recommended", in this case the x86, release, which causes clients to fail to install on any other architecture, as they simply grab this recommended release. As example, here's DuckduckGo, which does publish all four at once:
I'm not sure exactly how you handle F-droid releases, but since this second example is the intended method, I imagine it shouldn't be too hard to adjust.
Additional Context
Screenshots from the F-droid webpages:
Code of Conduct
User Story
Currently, on F-Droid, for every new version of Probe, four separate releases are published. All have the correct version tag (e.g.
6.0.1), but are for different CPU architectures (x86,x86_64,armeabi-v7a,arm64-v8a):Instead, these four should all be bundled into one release.
The problem with the current method is that F-Droid automatically marks the latest stable release as "recommended", in this case the
x86, release, which causes clients to fail to install on any other architecture, as they simply grab this recommended release. As example, here's DuckduckGo, which does publish all four at once:I'm not sure exactly how you handle F-droid releases, but since this second example is the intended method, I imagine it shouldn't be too hard to adjust.
Additional Context
Screenshots from the F-droid webpages:
Code of Conduct