[core-workflow] PEP 512: migrating hg.python.org to GitHub

2016-01-17 Thread Brett Cannon
Here is the first complete draft of the PEP laying out what needs to happen to migrate to GitHub (along with some extras that would be nice). The PEP can also be viewed at https://github.com/brettcannon/github-transition-pep/blob/master/pep-0512.rst or at https://www.python.org/dev/peps/ once the P

Re: [core-workflow] PEP 512: migrating hg.python.org to GitHub

2016-01-17 Thread Oleg Broytman
Hi! On Sun, Jan 17, 2016 at 08:48:42PM +, Brett Cannon wrote: > Change sys._mercurial > ' > Once Python is no longer kept in Mercurial, the ``sys._mercurial`` > attribute will need to be removed. An equivalent ``sys._git`` > attribute will be needed to take its place.

Re: [core-workflow] PEP 512: migrating hg.python.org to GitHub

2016-01-17 Thread Ezio Melotti
On Sun, Jan 17, 2016 at 10:48 PM, Brett Cannon wrote: > Here is the first complete draft of the PEP laying out what needs to happen > to migrate to GitHub (along with some extras that would be nice). The PEP > can also be viewed at > https://github.com/brettcannon/github-transition-pep/blob/master

Re: [core-workflow] PEP 512: migrating hg.python.org to GitHub

2016-01-17 Thread Martin Panter
On 17 January 2016 at 23:20, Oleg Broytman wrote: > On Sun, Jan 17, 2016 at 08:48:42PM +, Brett Cannon > wrote: >> Rejected Ideas >> == >> Commit multi-release changes in bugfix branch first >> --- >> As the current development proc

Re: [core-workflow] PEP 512: migrating hg.python.org to GitHub

2016-01-17 Thread Martin Panter
On 17 January 2016 at 20:48, Brett Cannon wrote: > Rationale > = > . . . > The overarching goal of this migration is to improve the development > process to the extent that a core developer can go from external > contribution submission through all the steps leading to committing > said co

Re: [core-workflow] PEP 512: migrating hg.python.org to GitHub

2016-01-17 Thread Brett Cannon
On Sun, 17 Jan 2016 at 15:20 Oleg Broytman wrote: > Hi! > > On Sun, Jan 17, 2016 at 08:48:42PM +, Brett Cannon > wrote: > > Change sys._mercurial > > ' > > Once Python is no longer kept in Mercurial, the ``sys._mercurial`` > > attribute will need to be removed. An equival

Re: [core-workflow] PEP 512: migrating hg.python.org to GitHub

2016-01-17 Thread Brett Cannon
On Sun, 17 Jan 2016 at 16:42 Martin Panter wrote: > On 17 January 2016 at 23:20, Oleg Broytman wrote: > > On Sun, Jan 17, 2016 at 08:48:42PM +, Brett Cannon > wrote: > >> Rejected Ideas > >> == > >> Commit multi-release changes in bugfix branch first > >> ---

Re: [core-workflow] PEP 512: migrating hg.python.org to GitHub

2016-01-17 Thread Brett Cannon
On Sun, 17 Jan 2016 at 17:37 Martin Panter wrote: > On 17 January 2016 at 20:48, Brett Cannon wrote: > > Rationale > > = > > . . . > > The overarching goal of this migration is to improve the development > > process to the extent that a core developer can go from external > > contributio

Re: [core-workflow] PEP 512: migrating hg.python.org to GitHub

2016-01-17 Thread Chris Angelico
On Mon, Jan 18, 2016 at 7:48 AM, Brett Cannon wrote: > Luckily, Git [#git]_ does not require GitHub's workflow and so one can > be chosen which gives us a linear history by using Git's CLI. The > expectation is that all pull requests will be fast-forwarded and > rebased before being pushed to the

Re: [core-workflow] PEP 512: migrating hg.python.org to GitHub

2016-01-17 Thread Ezio Melotti
On Mon, Jan 18, 2016 at 4:33 AM, Brett Cannon wrote: > > > On Sun, 17 Jan 2016 at 16:30 Ezio Melotti wrote: >> >> > >> > Repositories to Migrate >> > === >> > While hg.python.org [#h.p.o]_ hosts many repositories, there are only >> > six key repositories that must move: >> > >