Adaway: add new version tag so fdroid will recognize the new version

[jawz101]

I asked on Reddit why they haven't updated their version and they said Adaway doesn't have a new version tag that would signal to them there is a new release.

Just thought I'd mention it

[ale5000-git]

+1

[PerfectSlayer]

Hi all,

The dev/beta versions are not intended for end users.
I mean, I am currently changing the database backend and settings are lost until I implement a migration feature. Is it really what you want for everyone?

But if you want to test it, you are welcome on the dev thread 😉

[ale5000-git]

@PerfectSlayer
Personally I think that is the user that must choose.

On F-Droid you can also distribute beta versions (tagged as beta) so only users that have enabled the option to get unstable versions in F-Droid will get them.

[PerfectSlayer]

Any pointer to the F-Droid documentation about a "beta" tag?

[jawz101]

Does this give the info?
https://f-droid.org/en/docs/
specifically
https://f-droid.org/en/docs/Build_Metadata_Reference/#Update-Check-Mode

And maybe this file needs updating somehow?
https://gitlab.com/fdroid/fdroiddata/blob/master/metadata/org.adaway.txt

[PerfectSlayer]

I already looked at the F-Droid documentation but I don't really find an easy way to publish beta on the market.
So I ask on the dedicated IRC channel:

[18:02] I'm the maintainer of an application distributed on F-Droid (so thanks to you !) and I looking for a way to push beta versions.
[18:03] Actually, I add tags to GitHub (vX.Y format) and it works well.
[18:04] But some users want more frequent update (so beta version). How can I tag some commit to publish beta version to your store?
[18:14] [18:15] [18:16] [18:17] [18:20] Okay, seems logic. Thanks for the tip!

It doesn't seem so easy (and might take few time for each build…).
Remember I don't have a whole team to handle all tasks 😅
So if we find an easy way, I can do it but for now I still focus on XDA dev thread (yep I know, even the OP is not updated with the dev build 😛 )