From brett at python.org Sun Jan 22 13:19:22 2017 From: brett at python.org (Brett Cannon) Date: Sun, 22 Jan 2017 18:19:22 +0000 Subject: [core-workflow] Update on the GitHub migration Message-ID: 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). -------------- next part -------------- An HTML attachment was scrubbed... URL: From brett at python.org Mon Jan 30 17:51:22 2017 From: brett at python.org (Brett Cannon) Date: Mon, 30 Jan 2017 22:51:22 +0000 Subject: [core-workflow] last blocker for the GitHub migration is in! Message-ID: 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. -------------- next part -------------- An HTML attachment was scrubbed... URL: From brett at python.org Mon Jan 30 18:21:37 2017 From: brett at python.org (Brett Cannon) Date: Mon, 30 Jan 2017 23:21:37 +0000 Subject: [core-workflow] Planning the GitHub migration Message-ID: 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). -------------- next part -------------- An HTML attachment was scrubbed... URL: From senthil at uthcode.com Tue Jan 31 01:52:49 2017 From: senthil at uthcode.com (Senthil Kumaran) Date: Mon, 30 Jan 2017 22:52:49 -0800 Subject: [core-workflow] Planning the GitHub migration In-Reply-To: References: Message-ID: On Mon, Jan 30, 2017 at 3:21 PM, Brett Cannon 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). Sounds good to me. I am fine and with the knowledge of likely dates, I will be able to plan and stick to it. Thanks, Senthil From benjamin at python.org Tue Jan 31 02:57:32 2017 From: benjamin at python.org (Benjamin Peterson) Date: Mon, 30 Jan 2017 23:57:32 -0800 Subject: [core-workflow] Planning the GitHub migration In-Reply-To: References: Message-ID: <1485849452.2836719.865129480.30CBC0BD@webmail.messagingengine.com> I can handle those things. On Mon, Jan 30, 2017, at 15:21, Brett Cannon 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). > > 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). From brett at python.org Tue Jan 31 13:26:07 2017 From: brett at python.org (Brett Cannon) Date: Tue, 31 Jan 2017 18:26:07 +0000 Subject: [core-workflow] Planning the GitHub migration In-Reply-To: References: Message-ID: [for my own notes, I forgot something in the list] On Mon, 30 Jan 2017 at 15:21 Brett Cannon 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). > > 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. bugs.python.org webhook > 1. Migrate the hg repo and push it to GitHub (*Senthil*?) > 2. Update docs.python.org to build from GitHub (push > https://github.com/python/psf-salt/pull/91; *Berker*?) > 3. Get buildbots to build from GitHub (*Zach*?) > 4. Updates posted to #python-dev (*R. David*?) > 5. Commits sent to python-checkins > 6. Gather commit IDs from hg repo > 7. Push update to hg.python.org/lookup (*Benjamin*, *Georg*, or > *Antoine*?) > 8. 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). > -------------- next part -------------- An HTML attachment was scrubbed... URL: From zachary.ware+pydev at gmail.com Tue Jan 31 13:31:31 2017 From: zachary.ware+pydev at gmail.com (Zachary Ware) Date: Tue, 31 Jan 2017 12:31:31 -0600 Subject: [core-workflow] Fwd: Planning the GitHub migration In-Reply-To: References: Message-ID: On Mon, Jan 30, 2017 at 5:21 PM, Brett Cannon 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 From brett at python.org Tue Jan 31 13:35:49 2017 From: brett at python.org (Brett Cannon) Date: Tue, 31 Jan 2017 18:35:49 +0000 Subject: [core-workflow] Planning the GitHub migration In-Reply-To: References: Message-ID: [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 wrote: > [for my own notes, I forgot something in the list] > > On Mon, 30 Jan 2017 at 15:21 Brett Cannon 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). > > 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. bugs.python.org webhook > > > 1. Migrate the hg repo and push it to GitHub (*Senthil*?) > 2. Update docs.python.org to build from GitHub (push > https://github.com/python/psf-salt/pull/91; *Berker*?) > 3. Get buildbots to build from GitHub (*Zach*?) > 4. Updates posted to #python-dev (*R. David*?) > 5. Commits sent to python-checkins > 6. Gather commit IDs from hg repo > 7. 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 > > 1. 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). > > -------------- next part -------------- An HTML attachment was scrubbed... URL: From ezio.melotti at gmail.com Tue Jan 31 15:52:03 2017 From: ezio.melotti at gmail.com (Ezio Melotti) Date: Tue, 31 Jan 2017 22:52:03 +0200 Subject: [core-workflow] Planning the GitHub migration In-Reply-To: References: Message-ID: On Tue, Jan 31, 2017 at 8:35 PM, Brett Cannon 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 wrote: >> >> [for my own notes, I forgot something in the list] >> >> On Mon, 30 Jan 2017 at 15:21 Brett Cannon 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 From alexander.belopolsky at gmail.com Tue Jan 31 16:21:23 2017 From: alexander.belopolsky at gmail.com (Alexander Belopolsky) Date: Tue, 31 Jan 2017 16:21:23 -0500 Subject: [core-workflow] Planning the GitHub migration In-Reply-To: References: Message-ID: On Tue, Jan 31, 2017 at 3:52 PM, Ezio Melotti wrote: > you can submit a project idea for GSoC by the 7th of > February. > Where can I find instructions on how to do it? I may have an idea to submit. -------------- next part -------------- An HTML attachment was scrubbed... URL: From ezio.melotti at gmail.com Tue Jan 31 16:24:06 2017 From: ezio.melotti at gmail.com (Ezio Melotti) Date: Tue, 31 Jan 2017 23:24:06 +0200 Subject: [core-workflow] Planning the GitHub migration In-Reply-To: References: Message-ID: On Tue, Jan 31, 2017 at 11:21 PM, Alexander Belopolsky wrote: > > On Tue, Jan 31, 2017 at 3:52 PM, Ezio Melotti > wrote: >> >> you can submit a project idea for GSoC by the 7th of >> February. > > > Where can I find instructions on how to do it? I may have an idea to > submit. See http://python-gsoc.org/#mentors and/or ask on #python-gsoc on Freenode. From berker.peksag at gmail.com Tue Jan 31 16:52:30 2017 From: berker.peksag at gmail.com (=?UTF-8?Q?Berker_Peksa=C4=9F?=) Date: Wed, 1 Feb 2017 00:52:30 +0300 Subject: [core-workflow] Planning the GitHub migration In-Reply-To: References: Message-ID: On Tue, Jan 31, 2017 at 2:21 AM, Brett Cannon wrote: > Update docs.python.org to build from GitHub (push > https://github.com/python/psf-salt/pull/91; Berker?) I can review and test this on my development environment, but we probably need someone from the infra team to do the merging :) --Berker From brett at python.org Tue Jan 31 17:43:19 2017 From: brett at python.org (Brett Cannon) Date: Tue, 31 Jan 2017 22:43:19 +0000 Subject: [core-workflow] Planning the GitHub migration In-Reply-To: References: Message-ID: On Tue, 31 Jan 2017 at 14:01 Berker Peksa? wrote: > On Tue, Jan 31, 2017 at 2:21 AM, Brett Cannon wrote: > > Update docs.python.org to build from GitHub (push > > https://github.com/python/psf-salt/pull/91; Berker?) > > I can review and test this on my development environment, but we > probably need someone from the infra team to do the merging :) > I've emailed them to see if there's anything I can do to make it easier for them. -------------- next part -------------- An HTML attachment was scrubbed... URL: From berker.peksag at gmail.com Tue Jan 31 20:23:36 2017 From: berker.peksag at gmail.com (=?UTF-8?Q?Berker_Peksa=C4=9F?=) Date: Wed, 1 Feb 2017 04:23:36 +0300 Subject: [core-workflow] Planning the GitHub migration In-Reply-To: References: Message-ID: On Wed, Feb 1, 2017 at 1:43 AM, Brett Cannon wrote: > > > On Tue, 31 Jan 2017 at 14:01 Berker Peksa? wrote: >> >> On Tue, Jan 31, 2017 at 2:21 AM, Brett Cannon wrote: >> > Update docs.python.org to build from GitHub (push >> > https://github.com/python/psf-salt/pull/91; Berker?) >> >> I can review and test this on my development environment, but we >> probably need someone from the infra team to do the merging :) > > > I've emailed them to see if there's anything I can do to make it easier for > them. Thanks! I don't think I have commit rights to that repo so hopefully they will only need to press the merge button :) --Berker