AndroidCupsPrint icon indicating copy to clipboard operation
AndroidCupsPrint copied to clipboard

New release on f-droid

Open macearl opened this issue 6 years ago • 17 comments

Hi, as there are tons of issues recently closed it would be great if you could build a new release apk, or mark a branch as a new release (whatever makes fdroid build a new version)

I've installed your app on quite a few devices (most of them are not mine) and it would make it a lot easier to update them if i could just tell people to refresh their f-droid repositories instead of making them uninstall the app and reinstall a self build one instead.

cheers

macearl avatar Sep 06 '18 23:09 macearl

I have some commits pending, I'll push them in a few minutes. I'll release a beta with that. Once it's stable I'll push it to prod.

However f-droid is taking me a lot of time and sweat, and I use some proprietary dependencies (on top of my head Crashlytics, don't know if there are more) so I guess that's not a simple push to get a release on f-droid.

If you are knowledgeable about f-droid, feel free to fork/PR for f-droid and I'll merge.

BenoitDuffez avatar Sep 06 '18 23:09 BenoitDuffez

OK now everything should be automatic. I have a cron job that runs at 2am every day (beta.sh) which makes a new RC release on beta branch, based off of the last commit on develop.

So any commit sent to develop will be released as a RC in the beta branch.
My CI server builds the beta branch and uploads it to the Play Store, so it will be triggered by the 2am cron job if there are some new commits on develop.

So basically any commit pushed to develop will be published as beta on the Play Store the next day.

And last, any merge to master will result in a non-RC release and a production build.

So for today I have bumped the version to 1.5.0 (from 1.4.0) and the build that will be made today will be 1.5.0-RC1. If another commit comes by later on, it will create 1.5.0-RC2, and so on.
The merge on master will generate the 1.5.0 final.

I hope that's what you wanted. Sorry about f-droid but I don't have time to merge on that branch.

BenoitDuffez avatar Sep 07 '18 00:09 BenoitDuffez

OK that went well! Subscribe to the beta version of the app on the Play Store to receive all what I just pushed. :)

screen shot 2018-09-07 at 02 11 40

BenoitDuffez avatar Sep 07 '18 00:09 BenoitDuffez

Thanks, i will give it a try, sadly i am not familiar with F-Droids build process

macearl avatar Sep 07 '18 14:09 macearl

If @BenoitDuffez could update 8the fdroid branch}(https://github.com/BenoitDuffez/AndroidCupsPrint/tree/fdroid), we (at F-Droid) might be able to build an update. Master includes some proprietary libraries which are not permitted in #F-Droid (like Crashlytics). Alternatively, if Crashlytics could be replaced by ACRA or Matomo, a separate branch might not even be required …

IzzySoft avatar Jan 24 '19 12:01 IzzySoft

Pull requests welcome.

BenoitDuffez avatar Jan 24 '19 19:01 BenoitDuffez

Sigh well… unfortunately, not being a developer, I cannot help with that… But good to know you're open to it!

IzzySoft avatar Jan 24 '19 19:01 IzzySoft

No worries, not everyone is. Now that you mentioned this issue, it's a little bit higher in the list (at least in my head!). Unfortunately I can't allow as much time as I want on this project.

BenoitDuffez avatar Jan 24 '19 19:01 BenoitDuffez

Yes, I know that problem – one can fork a project, but not the developer (they can "spawn", but it takes several years for productive results 🤣 )…

So I take it the Debian way: it's available when it's ready. Thanks!

IzzySoft avatar Jan 25 '19 17:01 IzzySoft

can you please relook into the issue thank you

leela52452 avatar Jul 05 '19 11:07 leela52452

I don't have time. I will accept pull requests.

BenoitDuffez avatar Jul 12 '19 03:07 BenoitDuffez

I tried to solve the problem with my PR but please have a look at it if it fits right.....

jugendhacker avatar Nov 20 '19 00:11 jugendhacker

OK I have attempted to update my gitlab repo and merge it to gitlab.com:fdroiddata/master with the newest 1.5.0 release, pointing to the latest commit of the f-droid branch of this repo.

Here it is: https://gitlab.com/fdroid/fdroiddata/merge_requests/5967/pipelines

My branch on that repo (on gitlab) was 18k commits behind, I attempted to rebase my work and update the yml. The pipeline passed, but I have zero idea whether what I did was good or not.

Anyway if someone has a good knowledge of how fdroid works, please hint me or submit PR here or on the gitlab repo.

BenoitDuffez avatar Nov 21 '19 04:11 BenoitDuffez

@BenoitDuffez thanks for the effort. Perhaps you shouldn't have marked it as WIP ? I think that's why it received no comments/attention from the F Droid guys..

doronbehar avatar Nov 22 '19 10:11 doronbehar

So you've made a fdroid branch, great...but you add non-FOSS Crashlytics to it? Why?

licaon-kter avatar Mar 02 '20 23:03 licaon-kter

I didn't add non FOSS to the branch: I didn't remove it from the master branch. This app on production on the play store has crashlytics.

Why? I think I made it pretty clear in all the recent issues that I don't have time to invest in this project.

It's FOSS, you are free to clone it, remove what you don't like and install whatever you want on your device.

BenoitDuffez avatar Mar 03 '20 01:03 BenoitDuffez

@BenoitDuffez FYI https://gitlab.com/fdroid/fdroiddata/-/merge_requests/6420

licaon-kter avatar Mar 03 '20 10:03 licaon-kter