Well, two separate decisions: release 0.6.24 or not and whether we want to go to 0.7.
But I don't have a reason to wait on releasing 0.6.24. And as for 0.7, I'm fine with that too. Just a number. :) But this branch itself feels like not a very momentous change. By which I mean, end users shouldn't care about this at all. Doesn't fix any big bugs (except maybe the --cf-backend argument) and doesn't add any new features. The bump to require python 2.6 feels like a more natural jumping off point, but as edso noted, 0.6.23 already has 2.6isms in it. So not really a change there either. So... :shrug: -- https://code.launchpad.net/~mterry/duplicity/backend-unification/+merge/216764 Your team duplicity-team is requested to review the proposed merge of lp:~mterry/duplicity/backend-unification into lp:duplicity. _______________________________________________ Mailing list: https://launchpad.net/~duplicity-team Post to : [email protected] Unsubscribe : https://launchpad.net/~duplicity-team More help : https://help.launchpad.net/ListHelp
