Mailman 3 January 2017 - core-workflow

Planning the GitHub migration
by Brett Cannon 01 Feb '17

01 Feb '17

Assuming I'm right and there are no more blockers for the migration (see my other email to this list on that topic), here is my current thinking on the steps necessary to migrate (I am CC'ing people I'm hoping can help me out with this plan and *bolded* their names; anything without someone's name is on me to do). 1. Make the hg repo read-only (*Benjamin*, *Georg*, or *Antoine*?) 2. Rename python/cpython to python/cpython-mirror 3. Create a new python/cpython project and add relevant webhooks/integrations 1. CLA bot 2. Travis 3. Codecov 4. Migrate the hg repo and push it to GitHub (*Senthil*?) 5. Update docs.python.org to build from GitHub (push https://github.com/python/psf-salt/pull/91; *Berker*?) 6. Get buildbots to build from GitHub (*Zach*?) 7. Updates posted to #python-dev (*R. David*?) 8. Commits sent to python-checkins 9. Gather commit IDs from hg repo 10. Push update to hg.python.org/lookup (*Benjamin*, *Georg*, or *Antoine*?) 11. Add configuration files for services from https://github.com/brettcannon/cpython-ci-test 1. Travis 2. Codecov If I'm missing anything please let me know (everything else I know isn't really time-critical for accepting commits). Once we agree that these are the steps required and people whose help I need/want are on board then I will schedule with python-committers and the requisite release managers to get a date and verify with the people helping me. Then we can do the migration! I know there seem like there are a lot of steps, but a lot of this is parallelizable (e.g. once step 1 is done, steps 2-4 can occur, and after step 4 then the rest of the steps can happen in any order).

7 11

Fwd: Planning the GitHub migration
by Zachary Ware 31 Jan '17

31 Jan '17

On Mon, Jan 30, 2017 at 5:21 PM, Brett Cannon <brett(a)python.org> wrote: > Get buildbots to build from GitHub (Zach?) I've made a couple of small steps in this direction. Once we have a clear date set, I'll budget some concentrated time to get it done if free time hasn't gotten me far enough. -- Zach

1 0

last blocker for the GitHub migration is in!
by Brett Cannon 30 Jan '17

30 Jan '17

Thanks to the very hard work of Maciej and Ezio, the final change required of bpo is in! That should be the last blocker for the migration. ( https://github.com/python/peps/blob/master/pep-0512.txt#L698 as always is the "official" todo list.) If there is any critical blocker that people feel *must* be in before the migration, *speak up now!* There will be a separate email about my current thinking on how to handle the migration.

1 0

Update on the GitHub migration
by Brett Cannon 22 Jan '17

22 Jan '17

The last blocker is updating issues on bugs.python.org when a commit is made that references an issue (Maciej is working on it, although as usual I'm sure help is welcome). Once that's in then it will be time to choose a date to stop commits and do the conversion. Once that's done it will be a bunch of little things to update due to the repo moving (e.g building the docs from git).

1 0

core-workflow January 2017