DAVdroid 1.1.1.1
add yield points to allow processing of groups with many contactsAdd a changelog in the release page on github
-
Hi
Currently, there isn’t a simple way to see the changes to your program. You should use the github release page for it. An example of what it can look :
https://github.com/mpv-player/mpv/releasesYamakaky
-
What do you mean? Changes are already listed in the tags, i.e. the Releases page of DAVdroid. It’s even linked from the Fdroid description
-
In the example @Yamakaky gave the changes are visible directly from the releases page.
I am not sure how it is done. Maybe using the RELEASE_NOTES file https://github.com/mpv-player/mpv/blob/v0.6.2/RELEASE_NOTES
I could not find the github documentation for that feature.
-
https://github.com/blog/1547-release-your-software
Release notes can be edited in the Github GUI on https://github.com/bitfireAT/davdroid/tags. Would be interesting if they could be added via a RELEASE_NOTES file. Otherwise, all release info would stay at Github and not be reproducible if DAVdroid would move to another service.
-
Thansk for the pointer @rfc2822. I did not know this github feature.
A solution would be to have a RELEASE_NOTES or Changelog or History (or whatever) file and copy-paste the head of it in github release notes. So the data is not locked in github only.
-
Oh, sorry, I didn’t see that in the release page, the release comments are hidden by default ^^
-
In the F-Droid app on Android, there’s a link to the changelog page at https://github.com/bitfireAT/davdroid/releases, which opens that page listing each new version with, currently, no information. It would be nice, in principle, to have a brief description of changes there.
-
A solution would be to have a RELEASE_NOTES or Changelog or History (or whatever) file and copy-paste the head of it in github release notes. So the data is not locked in github only.
Until now, I was too lazy for that. Maybe we will introduce this file. Until then, please stick with the release comments in the tag notes.
-
The releases are built from the version tag by Github, as soon as one “drafts a new release”. I’ll do so in future and add the signed APK as a binary, too (for archiving purposes).