[core-workflow] GitHub migration status as of 2016-11-18

Brett Cannon brett at python.org
Fri Nov 18 20:15:59 EST 2016


Since Python 3.6.0 is due in just under a month it means we're hopefully in
the home stretch of getting things in line to do the GitHub migration by
the end of the year! This is a quick update on where things stand.

The devguide is still finished. :) That's the end of the "completed" list
for now.

In progress are reviews for the patches against bugs.python.org thanks to
Maciej and his GSoC student. Ezio is reviewing those patches and once they
go in we will then be able to test some things to make sure nothing is
going to break. I have also configured Travis and CircleCI at
https://github.com/brettcannon/cpython-ci-test to test them out (separate
email on that coming later).

I'm trying to track down the location of the code for hg.python.org/lookup
so that it can be updated appropriately. Emails for checkins and IRC
messages can be done the day of the migration (or shortly thereafter).
Updating PEP 101 or getting sys._git in can come after the migration. That
leaves updating how the buildbots get triggered and pull down code (email
out to python-buildbots on that topic).

And due to the lack of tags in the mirror we will have to recreate the repo
using Senthil's script. I don't know if it's best to simply delete the
project and recreate it or to do a force-push over the mirror.

And that's where everything stands. It all seems doable by the end of the
year!
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://mail.python.org/pipermail/core-workflow/attachments/20161119/f1ef3324/attachment.html>


More information about the core-workflow mailing list