There are some severe issues. That’s one reason why Canary is up to 2.0.4.34. On balance, even with possible regressions from new changes, I think progress has been made. For a next-release fix, look at:
v2.0.4.17-2.0.4.17_canary_2019-04-11 where the parallel uploads author fixed this bug in backend files:
Fixed an issue where index files were not generated, thanks @seantempleton
and there has been at least one more index file bug that happened whenever an upload retry happened.
v2.0.4.31-2.0.4.31_canary_2019-10-19
Fixed a retry error where uploaded
dindex-files would reference non-existingdblockfiles, thanks @warwickmm
and there are some more. You can read through the release notes if you want to see what’s happened.
It will always be the case that latest stable is missing features such as this that are still in development. How else could it possibly be done? Well, one path would be for the test team to get internal Canary to beat on for awhile, but there is no test team (volunteers?), so instead after automated test, a Canary is released for any who want to try it. In this way, Canary is somewhat similar to a Windows Insider build.
On the misleading version numbers, an improvement is expected. Duplicati version numbering has the general idea. With this one can at least guess by version number which version has the newer function.
Settings in Duplicati will let you change channels if you get tired of possible surprises Canary may give. Updating Duplicati is somewhat automated. You’ll hear about newer versions for the channel you’re on.