LanXchange icon indicating copy to clipboard operation
LanXchange copied to clipboard

Releases

Open IzzySoft opened this issue 9 years ago • 7 comments

Just a pointer: To make releases (and their downloads) easier accessible, consider using Github's release system – see Creating Releases in the Github help system. Placed there, the files can be downloaded directly (i.e. without an intermediate page where one has to select "raw" to get the real file), and you can put notes for each release (e.g. a change log of some release-specific hints). Moreover, when placed there I can offer to include your Android app with my F-Droid compatible repo for folks without Playstore access :smile_cat:

In case you're afraid of "additional workload": It's pretty easy. As easy as creating a tag and attaching the files. A source tarball and ZIP is automatically created by Github then. So usually, not much more than a minute.

IzzySoft avatar Mar 04 '17 19:03 IzzySoft

Quick update: I have not overlooked this, but am super busy right now. Will look into it ASAP. Wanted to get rid of the old HP for downloads anyway.

tfg13 avatar Mar 07 '17 21:03 tfg13

Thanks for the headsup, @tfg13 – you've got my full sympathy! I'm quite familiar with such situations myself :innocent:

IzzySoft avatar Mar 07 '17 22:03 IzzySoft

PS: would you mind attaching the .apk to releases/ as well, for folks outside the playstore? I could then offer to provide it via my repo for convenience.

IzzySoft avatar Dec 11 '17 14:12 IzzySoft

The .apk is right there in releases/stable - and always has been :)

tfg13 avatar Dec 12 '17 14:12 tfg13

@tfg13 then I must be blind:

screenshot

Do you see an .apk file there?

IzzySoft avatar Dec 12 '17 15:12 IzzySoft

Aaaah, you talked about the github releases page. I was talking about the directory with the same name, where the apk has been forever: https://github.com/tfg13/LanXchange/tree/master/releases/stable

Anyway, fixed

tfg13 avatar Dec 12 '17 21:12 tfg13

Ah, </confusion> – yeah, there it is! My bad: it's even linked from the README as I see now, writing up the metadata :blush: But why is it that that directory has v1.50 while the release page only shows v1.41?

So find it here. For now I'm picking the .apk from inside the repo, as that seems to be the newer one. If tag and app version match, the releases/ page of course is prefered.

Btw: From a quick look it seems your app should match the inclusion citeria of the official F-Droid repo. Shall I file an RFP (Request For Packaging) for you there? The official repo is a much more prestiguous place. Getting your app from there makes many folks feeling much safer :wink:

Thanks a lot so far! Guess as soon as time permits I'll give your app (Android + Linux) a try myself. Looks very promising!

IzzySoft avatar Dec 12 '17 22:12 IzzySoft