[Twisted-Python] Suggested plan for GitHub migration

Jonathan Lange jml at mumak.net
Tue Dec 1 11:36:06 MST 2015


On Tue, 17 Nov 2015 at 23:48 Craig Rodrigues <rodrigc at crodrigues.org> wrote:

> On Tue, Nov 17, 2015 at 8:57 AM, Adi Roiban <adi at roiban.ro> wrote:
>
>>
>> For now, the funds were raised to migrate to GitHub, so we can not use
>> them to do other things.
>>
>> We will stay on Trac for issues... at least for now.
>>
>> I have no idea how we can migrate to any issue tracker without losing
>> data if we don't have full access to the database.
>>
>
>
> [snip]


> B.7  Update all wiki documentation to change all references to getting
> code from Subversion,
>          to getting code from GitHub.
>
>
Probably would be a good idea to have a list of such changes *before* the
migration.


> B.8  Update all systems which used Subversion to use GitHub.  For example,
> buildbots.
>
>
Couldn't we do this before the migration anyway?  At least partly?

jml
-------------- next part --------------
An HTML attachment was scrubbed...
URL: </pipermail/twisted-python/attachments/20151201/d4544e1d/attachment-0002.html>


More information about the Twisted-Python mailing list