There is no special reason besides being motivated by a complaint regarding the 0.7-series that I've considered as a bug report.
- http://lists.nongnu.org/archive/html/duplicity-talk/2017-01/msg00026.html It obviously is a new thing and the change can be made to 0.8-series. I'll submit a pull request to that branch when I have the chance. 2017-01-16 9:53 GMT+00:00 Aaron Whitehouse <[email protected]>: > The aim is to add new features to lp:duplicity (the 0.8-series) and only > backport important fixes to 0.7-series. Any reason this feature is proposed > to go into 0.7-series? > > > Duplicity 0.7-series series > --- > This was the focus of development until June 2016. This branch should now > be considered stable and new features should be merged into 0.8, with > ongoing development of this branch limited to bug fixes. > > It is likely to become obsolete quickly, but regressions should be limited. > > ======================== > Duplicity 0.8-series series > ---- > The main development branch. > -- > https://code.launchpad.net/~m4ktub/duplicity/0.7-fixes/+merge/314778 > You are the owner of lp:~m4ktub/duplicity/0.7-fixes. > -- https://code.launchpad.net/~m4ktub/duplicity/0.7-fixes/+merge/314778 Your team duplicity-team is requested to review the proposed merge of lp:~m4ktub/duplicity/0.7-fixes into lp:duplicity/0.7-series. _______________________________________________ Mailing list: https://launchpad.net/~duplicity-team Post to : [email protected] Unsubscribe : https://launchpad.net/~duplicity-team More help : https://help.launchpad.net/ListHelp
