On Tue, Jan 31, 2017 at 8:35 PM, Brett Cannon <br...@python.org> wrote: > [another missing step; I can't wait to put all of these proverbial "spinning > plates] > > On Tue, 31 Jan 2017 at 10:26 Brett Cannon <br...@python.org> wrote: >> >> [for my own notes, I forgot something in the list] >> >> On Mon, 30 Jan 2017 at 15:21 Brett Cannon <br...@python.org> wrote: >>> >>> 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). >>> >>> Make the hg repo read-only (Benjamin, Georg, or Antoine?) >>> Rename python/cpython to python/cpython-mirror >>> Create a new python/cpython project and add relevant >>> webhooks/integrations >>> >>> CLA bot >>> Travis >>> Codecov >> >> 4. bugs.python.org webhook >> >>> Migrate the hg repo and push it to GitHub (Senthil?) >>> Update docs.python.org to build from GitHub (push >>> https://github.com/python/psf-salt/pull/91; Berker?) >>> Get buildbots to build from GitHub (Zach?) >>> Updates posted to #python-dev (R. David?) >>> Commits sent to python-checkins >>> Gather commit IDs from hg repo >>> Push update to hg.python.org/lookup (Benjamin, Georg, or Antoine?) > > 8. Merge the github branch of the devguide into master > 1. Don't forget to update cpython-devguide.rtfd.io to point to master > and only have a single branch >>> >>> Add configuration files for services from >>> https://github.com/brettcannon/cpython-ci-test >>> >>> Travis >>> 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).
Just a quick remainder: if you need more help (especially post-migration), you can submit a project idea for GSoC by the 7th of February. CPython currently has 0 project ideas, and if we don't get any within the next week we might not get accepted. Best Regards, Ezio Melotti _______________________________________________ core-workflow mailing list core-workflow@python.org https://mail.python.org/mailman/listinfo/core-workflow This list is governed by the PSF Code of Conduct: https://www.python.org/psf/codeofconduct
