-
Notifications
You must be signed in to change notification settings - Fork 20
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Releases #9
Comments
Quick update: I have not overlooked this, but am super busy right now. |
Thanks for the headsup, @tfg13 – you've got my full sympathy! I'm quite familiar with such situations myself 😇 |
PS: would you mind attaching the |
The .apk is right there in releases/stable - and always has been :) |
@tfg13 then I must be blind: Do you see an |
Aaaah, you talked about the github releases page. Anyway, fixed |
Ah, So find it here. For now I'm picking the 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 😉 Thanks a lot so far! Guess as soon as time permits I'll give your app (Android + Linux) a try myself. Looks very promising! |
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 😸
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.
The text was updated successfully, but these errors were encountered: