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

[Georg Brandl]

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 Mercurial and
>>> those who prefer Subversion use that. If Mercurial allows to submit to
>>> Subversion - why people can't use that while we writing tutorials and
>>> answering question about workflow?
> 
>> I don't think that we have enough manpower to maintain such a bridge
>> indefinitely.
> 
> The code.python.org/hg mirror has been running for many months now: As a
> non-committer, I have been able to use its 2.6 branch and the trunk with
> hg to test / develop / submit patches.
> 
> Can somebody comment on how much ongoing effort is required to keep that
> mirror running?  I know that the hg / git / bzr mirrors I set up for the
> repoze SVN repository haven't require any ongoing effort, after the
> initial day or two of setup effort.

As Barry says, that's not a problem.  What's problematic is the continued
use of the current Subversion setup as a read-write bridge to the Mercurial
repo, once the switch to Mercurial as the main platform has happened.

Georg

-- 
Thus spake the Lord: Thou shalt indent with four spaces. No more, no less.
Four shall be the number of spaces thou shalt indent, and the number of thy
indenting shall be four. Eight shalt thou not indent, nor either indent thou
two, excepting that thou then proceed to four. Tabs are right out.