Re: [Python-Dev] Mercurial migration readiness (was: Taking over the Mercurial Migration)

Georg Brandl wrote: > Am 02.07.2010 16:17, schrieb anatoly techtonik: >> On Fri, Jul 2, 2010 at 4:53 PM, Georg Brandl wrote: What is the problem with realtime synchronization and working with already up to date Mercurial mirror of central SVN repository? >>> The specifics of the conversi

Re: [Python-Dev] Mercurial migration readiness (was: Taking over the Mercurial Migration)

Am 02.07.2010 17:09, schrieb Tres Seaver: > Development will continue in SVN > repository until everybody is ready for final migration in X weeks > later. Is that right? No; as soon as we switch, SVN will be read-only. >>> Why don't allow people who already know Mercurial use Mercu

Re: [Python-Dev] Mercurial migration readiness (was: Taking over the Mercurial Migration)

On Jul 02, 2010, at 11:09 AM, Tres Seaver wrote: >Can somebody comment on how much ongoing effort is required to keep >that mirror running? I'm guess "zero". Other than uploading new ssh keys, I think our svn master has been humming along pretty well without intervention. I know that the bzr mi

Re: [Python-Dev] Mercurial migration readiness (was: Taking over the Mercurial Migration)

Am 02.07.2010 16:17, schrieb anatoly techtonik: > On Fri, Jul 2, 2010 at 4:53 PM, Georg Brandl wrote: >>> >>> What is the problem with realtime synchronization and working with >>> already up to date Mercurial mirror of central SVN repository? >> >> The specifics of the conversion process are not

Re: [Python-Dev] Mercurial migration readiness (was: Taking over the Mercurial Migration)

-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Georg Brandl wrote: > Am 02.07.2010 15:48, schrieb anatoly techtonik: >> On Fri, Jul 2, 2010 at 11:33 AM, Georg Brandl wrote: So, if I understand correctly - there are no Mercurial mirrors for testing at the moment, >>> There are repositorie

Re: [Python-Dev] Mercurial migration readiness (was: Taking over the Mercurial Migration)

On Fri, Jul 2, 2010 at 10:17 AM, anatoly techtonik wrote: > On Fri, Jul 2, 2010 at 4:53 PM, Georg Brandl wrote: >>> >>> What is the problem with realtime synchronization and working with >>> already up to date Mercurial mirror of central SVN repository? >> >> The specifics of the conversion proce

Re: [Python-Dev] Mercurial migration readiness (was: Taking over the Mercurial Migration)

On Fri, Jul 2, 2010 at 16:17, anatoly techtonik wrote: > As PEP 384 says - the transition is mostly to make lives of outside > contributors easier. Core developers can wait for a while. I think a lot of the core developers also want this because it makes their lives better. Also, several people

Re: [Python-Dev] Mercurial migration readiness (was: Taking over the Mercurial Migration)

On Fri, Jul 2, 2010 at 4:53 PM, Georg Brandl wrote: >> >> What is the problem with realtime synchronization and working with >> already up to date Mercurial mirror of central SVN repository? > > The specifics of the conversion process are not nailed down yet. > Therefore, the exact translation of

Re: [Python-Dev] Mercurial migration readiness (was: Taking over the Mercurial Migration)

Am 02.07.2010 15:48, schrieb anatoly techtonik: > On Fri, Jul 2, 2010 at 11:33 AM, Georg Brandl wrote: >>> >>> So, if I understand correctly - there are no Mercurial mirrors for >>> testing at the moment, >> >> There are repositories at http://hg.python.org/; the "cpython" one >> represents the re

Re: [Python-Dev] Mercurial migration readiness (was: Taking over the Mercurial Migration)

On Fri, Jul 2, 2010 at 11:33 AM, Georg Brandl wrote: >> >> So, if I understand correctly - there are no Mercurial mirrors for >> testing at the moment, > > There are repositories at http://hg.python.org/; the "cpython" one > represents the result of conversion at some point in time. What is the p

Re: [Python-Dev] Mercurial migration readiness (was: Taking over the Mercurial Migration)

On 07/02/2010 10:33 AM, Georg Brandl wrote: > Am 02.07.2010 09:27, schrieb anatoly techtonik: >> On Thu, Jul 1, 2010 at 6:16 PM, Jesse Noller wrote: >>> >>> This migration is far from "rushed". Workflow will need to be >>> documented and we need a working hg setup a little while before the >>> off

Re: [Python-Dev] Mercurial migration readiness (was: Taking over the Mercurial Migration)

Am 02.07.2010 01:05, schrieb Antoine Pitrou: > On Thu, 1 Jul 2010 15:26:12 -0700 > Brett Cannon wrote: >> >> As I said, quick-and-dirty. It will take discussion to decide what we >> want to ask non-committers to do, > > I don't think we have to ask them to do anything special, as long as > they

Re: [Python-Dev] Mercurial migration readiness (was: Taking over the Mercurial Migration)

Am 02.07.2010 09:27, schrieb anatoly techtonik: > On Thu, Jul 1, 2010 at 6:16 PM, Jesse Noller wrote: >> >> This migration is far from "rushed". Workflow will need to be >> documented and we need a working hg setup a little while before the >> official migration. Both of those said, I personally t

Re: [Python-Dev] Mercurial migration readiness (was: Taking over the Mercurial Migration)

Am 01.07.2010 23:25, schrieb Doug Hellmann: > > On Jul 1, 2010, at 10:31 AM, Daniel Stutzbach wrote: > >> On Thu, Jul 1, 2010 at 7:52 AM, anatoly techtonik > > wrote: >> >> 4. Even if I make patch in my Mercurial clone - you still can't pull >> it and I have to

Re: [Python-Dev] Mercurial migration readiness (was: Taking over the Mercurial Migration)

On Fri, Jul 2, 2010 at 02:08, Stephen J. Turnbull wrote: > No, you don't.  You make links to 200MB+ (unless you're on Windows, > where I don't know how this works).  This is much cheaper than > copying, though not as cheap as in git.  I don't hesitate to make > branches in Mercurial. It can still

Re: [Python-Dev] Mercurial migration readiness (was: Taking over the Mercurial Migration)

On Thu, Jul 1, 2010 at 6:16 PM, Jesse Noller wrote: > > This migration is far from "rushed". Workflow will need to be > documented and we need a working hg setup a little while before the > official migration. Both of those said, I personally think this has > dragged on long enough. So, if I unde

[Python-Dev] Mercurial migration readiness (was: Taking over the Mercurial Migration)

anatoly techtonik writes: > After reading PEP 384 and PEP 385 (finally) I got a strong impression > that they are not ready for the change (read below the line for > details), because they do not propose any workflow. This was deliberate. There are a lot of different workflows, and we are not

Re: [Python-Dev] Mercurial migration readiness (was: Taking over the Mercurial Migration)

On Jul 01, 2010, at 03:26 PM, Brett Cannon wrote: >On Thu, Jul 1, 2010 at 15:07, Barry Warsaw wrote: >> Other than that, while I sometimes review patches in email, I do not >> think patches in a tracker are the best way to manage these.  A >> dvcs's biggest strength is in branches, so we should

Re: [Python-Dev] Mercurial migration readiness (was: Taking over the Mercurial Migration)

On 2 July 2010 09:08, Tim Delaney wrote: > On 2 July 2010 08:07, Barry Warsaw wrote: > >> >> Other than that, while I sometimes review patches in email, I do not think >> patches in a tracker are the best way to manage these. A dvcs's biggest >> strength is in branches, so we should use those a

Re: [Python-Dev] Mercurial migration readiness (was: Taking over the Mercurial Migration)

On 2 July 2010 08:07, Barry Warsaw wrote: > > Other than that, while I sometimes review patches in email, I do not think > patches in a tracker are the best way to manage these. A dvcs's biggest > strength is in branches, so we should use those as much as possible. > > I changed my team over fro

Re: [Python-Dev] Mercurial migration readiness (was: Taking over the Mercurial Migration)

On Thu, 1 Jul 2010 15:26:12 -0700 Brett Cannon wrote: > > As I said, quick-and-dirty. It will take discussion to decide what we > want to ask non-committers to do, I don't think we have to ask them to do anything special, as long as they can submit their contributions under the form of a patch.

Re: [Python-Dev] Mercurial migration readiness (was: Taking over the Mercurial Migration)

On Thu, Jul 1, 2010 at 15:07, Barry Warsaw wrote: > On Jul 01, 2010, at 10:57 PM, Paul Moore wrote: > >>On 1 July 2010 20:58, Brett Cannon wrote: >>> Here is a *really* quick-and-dirty approach for non-committers to >>> create a patch they can submit. This is not extensively tested so >>> some ot

Re: [Python-Dev] Mercurial migration readiness (was: Taking over the Mercurial Migration)

On Jul 01, 2010, at 10:57 PM, Paul Moore wrote: >On 1 July 2010 20:58, Brett Cannon wrote: >> Here is a *really* quick-and-dirty approach for non-committers to >> create a patch they can submit. This is not extensively tested so >> some other Hg expert should back me up on this before telling any

Re: [Python-Dev] Mercurial migration readiness (was: Taking over the Mercurial Migration)

On 1 July 2010 20:58, Brett Cannon wrote: > Here is a *really* quick-and-dirty approach for non-committers to > create a patch they can submit. This is not extensively tested so some > other Hg expert should back me up on this before telling anyone that > this is the simplest way. I am also not sa

Re: [Python-Dev] Mercurial migration readiness (was: Taking over the Mercurial Migration)

On Jul 1, 2010, at 10:31 AM, Daniel Stutzbach wrote: On Thu, Jul 1, 2010 at 7:52 AM, anatoly techtonik wrote: 4. Even if I make patch in my Mercurial clone - you still can't pull it and I have to attach it to tracker. No gain. Was there ever any discussion about hosting the central reposito

Re: [Python-Dev] Mercurial migration readiness (was: Taking over the Mercurial Migration)

The workflow described by Brett looks like a patch-and-email one. It’s used by the Mercurial team itself, and has the advantage of not cluttering the history with lots of changes, since you only apply one patch in the end. However, in the not-so-long run I feel that a simpler and more mercurialic w

Re: [Python-Dev] Mercurial migration readiness (was: Taking over the Mercurial Migration)

On Thu, Jul 1, 2010 at 07:31, R. David Murray wrote: > On Thu, 01 Jul 2010 15:51:06 +0200, Dirkjan Ochtman > wrote: >> On Thu, Jul 1, 2010 at 14:52, anatoly techtonik wrote: >> > Primary concern is that will happen with central Subversion >> > repository. There are a plenty of private tools and

Re: [Python-Dev] Mercurial migration readiness (was: Taking over the Mercurial Migration)

On Thu, Jul 1, 2010 at 8:52 AM, anatoly techtonik wrote: > After reading PEP 384 and PEP 385 (finally) I got a strong impression > that they are not ready for the change (read below the line for > details), because they do not propose any workflow. So, instead of > rushing with migration I'd like

Re: [Python-Dev] Mercurial migration readiness (was: Taking over the Mercurial Migration)

On Thu, Jul 01, 2010 at 09:31:13AM -0500, Daniel Stutzbach wrote: > On Thu, Jul 1, 2010 at 7:52 AM, anatoly techtonik wrote: > > > 4. Even if I make patch in my Mercurial clone - you still can't pull > > it and I have to attach it to tracker. No gain. > > > > Was there ever any discussion about h

Re: [Python-Dev] Mercurial migration readiness (was: Taking over the Mercurial Migration)

On Thu, Jul 1, 2010 at 16:31, Daniel Stutzbach wrote: > Was there ever any discussion about hosting the central repository on a site > such as bitbucket or github?  I tried searching the python-dev archives but > was unable to find much. > Anyway... assuming there's a at least a clone of the centr

Re: [Python-Dev] Mercurial migration readiness (was: Taking over the Mercurial Migration)

On Thu, Jul 1, 2010 at 16:31, Daniel Stutzbach wrote: > The hg-git tool allows Mercurial and git to interoperate, so that's not as > much of an issue as it once was.  It's geared toward using a Mercurial > client to talk to a git server, but I'm told it can work the other way > around with a bit o

Re: [Python-Dev] Mercurial migration readiness (was: Taking over the Mercurial Migration)

On Thu, 01 Jul 2010 15:51:06 +0200, Dirkjan Ochtman wrote: > On Thu, Jul 1, 2010 at 14:52, anatoly techtonik wrote: > > Primary concern is that will happen with central Subversion > > repository. There are a plenty of private tools and automated scripts > > that were written to work with central

Re: [Python-Dev] Mercurial migration readiness (was: Taking over the Mercurial Migration)

On Thu, Jul 1, 2010 at 7:52 AM, anatoly techtonik wrote: > 4. Even if I make patch in my Mercurial clone - you still can't pull > it and I have to attach it to tracker. No gain. > Was there ever any discussion about hosting the central repository on a site such as bitbucket or github? I tried se

Re: [Python-Dev] Mercurial migration readiness (was: Taking over the Mercurial Migration)

On Thu, Jul 1, 2010 at 14:52, anatoly techtonik wrote: > Primary concern is that will happen with central Subversion > repository. There are a plenty of private tools and automated scripts > that were written to work with central Subversion repository, so it is > important that central Subversion

[Python-Dev] Mercurial migration readiness (was: Taking over the Mercurial Migration)

After reading PEP 384 and PEP 385 (finally) I got a strong impression that they are not ready for the change (read below the line for details), because they do not propose any workflow. So, instead of rushing with migration I'd like to propose incremental change rather than revolutionary that will