[Python-Dev] Mercurial migration readiness (original) (raw)

Tres Seaver tseaver at palladion.com
Mon Jul 5 22:12:34 CEST 2010

-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1

Martin v. Löwis wrote:

I'd love to see a more detailed description of this, including why someone new to Mercurial would choose one over the other. I think someone new to Mercurial shouldn't choose either one. Just sit back and wait for the real migration to happen. I would say that using the SVN mirror is a fine way to experiment with using hg against the Python sources to develop and test patches. I think your description already falls into the "advanced user" category. The new-to-mercurial committer should (IMO) use a "what if it still was svn" workflow, which uses hg pull/up/commit/push. That can only work if pushing really has the desired effect, which isn't the case for any of the installations that we operate.

I am not a committer myself, and not really familiar with Mercurial (I know CVS/SVN best, and bzr better). I found the current hg mirror of svn quite useful as a way to work on bugs, review patches, etc. without needing any commit access.

When the test-for-two-weeks installation becomes available, the new-to-hg users will have a chance to learn how to use it without fear of breaking anything. Until then, they should just remain patient.

Experimenting with the mirror today without trying to push changes back would give those users a chance to do "familiarization" drills with the majority of mercurial's features, with the exception of the final push.

Tres. - --

Tres Seaver +1 540-429-0999 tseaver at palladion.com Palladion Software "Excellence by Design" http://palladion.com -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.9 (GNU/Linux) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org

iEYEARECAAYFAkwyPKwACgkQ+gerLs4ltQ6zxQCcCRFduUc97jH3g28m/xh3+fTC RtIAniyqilkaNFHS54bW+oF4YXv/cq4l =pdkc -----END PGP SIGNATURE-----

More information about the Python-Dev mailing list