On Fri, 2 Jul 2010 15:22:44 +0300 anatoly techtonik <techtonik@gmail.com> wrote:
On Fri, Jul 2, 2010 at 3:02 PM, Éric Araujo <merwok@netwok.org> wrote:
hg.python.org/cpython is a test setup for people working on the transition. It is not guaranteed to be usable, it usually lags, and it will be rewritten before the real switch IIRC.
code.python.org/hg is a mirror kept in sync for use by contributors who don’t want to use Subversion now.
After the switch, hg.python.org/cpython will be the official repo, and code.python.org/hg will probably be closed.
Why this transition is not described in PEP?
Because it's not a transition. It's a mirror. It was put in place before the hg migration plan was accepted, IIRC.
How code.python.org/hg is synchronized with Subversion?
What does your question mean exactly? It's a mirror (well, a set of mirrors) and is synchronized roughly every 5 minutes.
Why it is not possible to leave code.python.org/hg as is in slave mode and then realtime replication is ready just switch master/slave over?
The two sets of repositories use different conversion tools and rules. They have nothing in common (different changeset IDs, different metadata, different branch/clone layout). Regards Antoine.