Mailman 3 February 2017 - core-workflow

Choosing a label format for cherry-picking reminders
by Brett Cannon Feb. 8, 2017

Feb. 8, 2017

Since we are going to need reminders of what versions of Python to cherry-pick a PR into, I figured this was a perfect use of labels. If you want to provide feedback on possible formats for the label, add appropriate reactios to https://github.com/python/core-workflow/issues/17 .

1 0

Block direct pushes to the cpython repo?
by Brett Cannon Feb. 7, 2017

Feb. 7, 2017

I opened https://github.com/python/core-workflow/issues/16 to track the idea of turning off direct pushes to the git repo after the migration at some point. But immediately both Senthil and Barry voted to say they thought we should just start off on the proper footing and just block direct pushes to begin with. If you have a +1/-1 reaction to this then please add the appropriate reaction to https://github.com/python/core-workflow/issues/16#issue-205987825 (i.e. add a thumbs up or down reaction depending on how you care to vote). If things obviously lean in one way or the other will help me decide how we want to start the repo set as (we can obviously turn it off if it turns out to be a problem).

1 0

GitHub migration scheduled for Friday, Feb 10
by Brett Cannon Feb. 5, 2017

Feb. 5, 2017

I plan to start writing a doc covering workflow changes today or tomorrow in preparation for Friday.

1 0

Planning the GitHub migration
by Brett Cannon Feb. 1, 2017

Feb. 1, 2017

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