Adhere to best practices of library maintaince

[grote]

I am using this library with Seedvault and I am struggling to keep it up to date. What would help me would be semantic versioning and proper releases instead of the commit based main branch snapshots via jitpack.

Then introducing breaking changes only in major versions and ideally maintaining the last stable version for some time would be nice. Bonus points for migration guides from one major version to the other.

Especially the ktor work seems to introduce quite some churn at the moment. But there's places where I was using for example ResourceType.COLLECTION and now having a hard time finding where that moved to.

[rfc2822]

We'll finish the Ktor rewrite in DAVx⁵ soon, and also take the time to bring dav4jvm to a good condition again – with only the Ktor dependency.

I agree to your suggestions (especially the releases vs snapshot), but I don't know how much we can manage to do. We'll discuss and try to improve that.

For us it would also be useful to know who is actually using the library and how (own fork vs actually use the upstream dav4jvm), because currently it seems that it's rarely used, and then for instance migration guides seem a bit too much. Maybe a "Who's using the library" section in the README could additionally motivate better practices.

[abaker]

I'm using the library for tasks.org on both android and desktop

[grote]

I totally understand that this library is for use in DavX5 and we are lucky it even exists as Free Software, so if you wanted to accommodate other users without too much extra effort, using semantic versioning and tagging releases again would already help.