I installed the app from F-Droid App Store and now Iām wondering why Google Play Store offers version 3.29.2. The latest stable release in F-Droid as well as in github is 3.29.1. As far as I can see the next targeted version in github seems to be 3.30. There is no version/tag 3.29.2. So, where does Googleās version come from?
I noticed this too. Actually, it is not the first time GooglePlay-version of Android NC-client is ahead of github/f-droid.
What is even more interesting, there was some 3.29.2 branch on github, but is now empty, and work continues on 3.29.3 instead (RC1). Looking back into history, release sub-numbers were not skipped usually, so why now? Was 3.29.2 released with some bug and then pulled back?
As an Open Source product, how can we vet the code that went into these āorphanedā Google Play releases? Itās very weird to me that the binary release that gets automatically offered to most clients is ahead of the source.
It appears 3.29.2 did not have an (artificial) tag added at release time associated with the relevant final commit. There is, however, an associated PR for the release: Bump to 3.29.2 by tobiasKaminsky Ā· Pull Request #13261 Ā· nextcloud/android Ā· GitHub
All 3.29.x releases are within the stable-3.29 branch.
Great! The next question is: why thereās no associated GitHub release or F-Droid version bump?
Just a wild guess, but maybe the changes in 3.29.2 were only relevant to the Google Play version?
If you compare 3.29.3 and 3.29.1, there werenāt that many big changes in between, aside from this one, which only affected the the Google Play version.
1 Like