Hello,
Duplicity has no existing tracks, so per Process for aliases, auto-connections and tracks , we need a 1-week voting/discussion period, so I’ll check back on the discussion and votes in a few days.
I have a few questions before casting my vote.
- What’s Duplicity’s release cadence, how often is a new version (potentially requiring a new track) released? is this documented somewhere by upstream?
- I see here you’re requesting tracks for what looks like patch releases, which is an unusual usage for tracks. Is this intended? are patch versions incompatible among themselves, would a user have a good reason not to upgrade to 0.8.25 if they’re currently using 0.8.24 for example? (As a hunch/suggestion, I think you’d be better served by tracks for e.g. 0.7, 0.8, and subsequent minor versions but I’ll defer to your requirements and knowledge of the project).
- Is there some commitment from upstream on maintenance of old versions? e.g. is 0.7 still supported with security updates? will it continue to be supported now that 0.8 is out, and for how long? What will happen once 0.9 is out?
- Are new versions backwards-incompatible? meaning, if I was running 0.8.24 and try to install 0.8.25, will that just work, or do I need to migrate my data/configuration, or will things break horribly? How about trying to read 0.7-produced data with 0.8? or, looking ahead, will 0.9 be able to read and/or write 0.8 files?
Thanks!
- Daniel