← Back to team overview

duplicity-team team mailing list archive

Re: Converting duplicity from bzr to git

 

Thanks Ken,

On Jun 1 2019, at 4:32 pm, Kenneth Loafman <kenneth@xxxxxxxxxxx> wrote:
> I was thinking of using GitHub instead of Launchpad for git. It would be a much more agreeable site rather than something patched together to provide a non-native addition.

Yes, I think that makes sense, though when we last discussed this I thought the consensus was Gitlab instead of Github on the basis it is at least open core (and you had some concerns around Github ownership).
We have been discussing a potential move for quite a while. As the preliminary step for either of those would be the bzr -> git translation, my thinking was that completing that transition would be a step in the right direction.
You are right that we have a fair bit on with the 0.8.00 release and the move to Python 3 and I agree it probably makes sense to just focus on that for now. To ensure we do not break anything in those changes I have been wanting to build some more robust backwards compatibility tests and backend tests into the test suite. It would be great to have those as part of a CI suite testing each proposed merge, but if I do them as part of the existing test suite and use environment variables for any secrets, we should be able to move them over to anything new.
Kind regards,
Aaron


Follow ups

References