Hello everyone, after our discussions and the clarifications from anarcat, it seems that the only sensible way to solve this is by trying to inform the end-user as much as possible to help her/him make an informed decision whether they should use the 0.x software or wait for the 1.0 version.
On future compat-breaking updates, I will take care to copy any relevant parts from upstream changelog to a NEWS.Debian file, to make sure they pop up during installation / get e-mailed to the admin, although that does of course not cover new installations. I have already split the Debian-READMEs into source[1] and end-user[2] and I tried to find a sensible wording for both. If you have better ideas, send patches! (feel free to spawn new branches on the collab-maint repository) Under the assumption that the enduser can be expected to at least read README.Debian, (upstream) README.rst, and NEWS.Debian upon updates, I believe that it should be appropriate to post stuff there. Please state whether you think this (write README and hope user actually reads it) is an appropriate solution to the compatibility problem, meaning we could close the bug this way. Cheers - Danny [1]: https://anonscm.debian.org/cgit/collab-maint/borgbackup.git/tree/debian/README.source [2]: https://anonscm.debian.org/cgit/collab-maint/borgbackup.git/tree/debian/README.Debian
