Releases and Packages

[ghost]

1. I would suggest to use the Release feature https://github.com/astarub/campus_app/releases as it makes it easier to keep track of the progress towards a new version and the planned features.
2. It would be nice to have a downloadable APK File with those releases to install the App without the need for Play or Appstore.
3. In the long run it would be awesome to see the App being included in F-Droid.

[C4s4r]

Point 1 and 2 go hand-in-hand, as we want to include APK-files in the GitHub releases.
If I remember correctly, @domai-tb was planning to work on the integration of GitHub releases in our workflow.

F-Droid releases are on our internal backlog, but this is currently handled with low priority.

[domai-tb]

Yes, im allready worked on a release workflow for GitHub and it is nearly done. Currently we use Codemagic as CI/CD tool to manage our release to the official Google and Apple Store, which would lead to inconsistency in the version numbers. Codemagic pulls the current release number from the store and automatically increase the build number, so the GitHub workflow should do the same.

The current workflow of PR #42 is just using the current date to name the APK-files. So we could get the current build number by setup the Codemagic Google Play CLI-Tool inside the workflow (or changing our current CI/CI-pipeline, what is currently unplaned). But feel free to add your input!

A F-Droid release is also planned but theire we are facing similiar issues. As mentioned above, Codemagic is managing our build number. So first we have to get ot from their and than publishing this repository to the official F-Droid Store by doing a pull request. We didn't find a straigth-forward way to do so, so thats the reason why their is no F-Droid release yet.

Cheers, :Domai

[MixColumns]

Anything new on this?

[domai-tb]

Unfortunately, no one has continued to work on it so far.