Releases

[IzzySoft]

Might I suggest you use the Github release system instead of hosting the archives inside the repo? Easy to do, short instructions can be found in the Github help: Creating Releases. If apart from tagging you also attach the files there, that makes them easier to find.

As for the Android .apk files: I'm a bit irritated that v2.0.7 should be the very first version (especially with a v1.1.5 lying next to it):

package: name='org.qtproject.example.YourFriendlyDNS' versionCode='1' versionName='1.0' platformBuildVersionName='8.1.0'

Could you please take care to increase versionCode with each new release, and have versionName reflect the real one? Otherwise this causes trouble/confusion on the users' end.

Thanks in advance!

[softwareengineer1]

Hello IzzySoft thanks your feedback is welcomed! Even before you mentioned this I was seeing github projects and wondering why I wasn't doing that myself, but thanks for actually getting me to do it!

I also added the android manifest and such files, which I could then control the version that is being output: Now it's :<manifest package="org.freedombasedsoftware.YourFriendlyDNS" xmlns:android="http://schemas.android.com/apk/res/android" android:versionName="2.1.1" android:versionCode="2" android:installLocation="auto">

Also added version information in the qmake file, so that the correct version should be there even on other than android too.

The latest version is the best so far, v2.1.1 and as it has all three DNSCrypt protocols supported (DNSCrypt, DNS over HTTPS, and DNS over TLS)

I should have been releasing as there'd be a 1.1.9 (the premium version of 1.x, before any type encryption at all was added) verson for you. I could always go back pull that version and rebuild it too, let me know if you think I should or just continue onward from here!

Thanks Izzy!

[IzzySoft]

Thanks for your response – and glad to see you're now tagging releases! And especially updating versionCode now. Could you also attach the APK files "plainly" (i.e. the pure *.apk, not inside a *.zip – see e.g. here for what I mean)? Then my auto-updater could grab them automatically whenever you make a new release, and place that into my repo – so all your users could use the F-Droid client to stay up-to-date (see here).

Also: is it (still) necessary to have the Debug flag set?

As for older versions: Thanks, but no need. If the always latest is available, that's fine for me – so yes, "just continue onward from here" 😉

[maju6406]

hi @softwareengineer1 if 2.1.3 is ready could you push out a new release?

[licaon-kter]

Also maybe bump versionCode to 4 for 2.1.3 ;)

[IzzySoft]

@softwareengineer1 ^^?? 🙏

[IzzySoft]

As it currently stands, your app is not (yet) on F-Droid – and no longer up-to-date in my repo. The latter is caused by your attaching ZIP files inside the release description instead of APK files in the "attachments". Could you please get that fixed?

[IzzySoft]

Ah, well, there wasn't even an update… Are you still maintaining this, @softwareengineer1? Are you even still active yourself?

[IzzySoft]

@softwareengineer1 any word? Uncertainty is unnerving – but we won't declare a horse dead if it's still running just because we cannot see it, so… any word would be appreciated. Thanks in advance!