Why we didn't migrate to Mercurial (long)

dukeofgaming dukeofgaming at gmail.com
Wed Oct 10 09:48:22 UTC 2012


This thread is pure gold.

I'm currently doing the exact same thing as you. I have a group of DVCS
(some mercurial, some git) fans and I hold 1-4 meetings per month with IT,
it is not an easy task, and I can relate to most of what you say.

A couple of points that have helped me move things along:

- Sell the centralized workflow first: You don't need to squeeze each ounce
of "workflow-ability" on day 1
- Sell it with repository management software: Corporate environments
require visibility and ease of administration, this is where software like
Rhodecode and Stash (which will get mercurial support
https://jira.atlassian.com/browse/STASH-2469 ) come into play.
- Do a proof of concept integration with your current VCS: Ok, not that
easy, BUT, I'm using perfarce to integrate to our Perforce depot, which
helps people visualize how they can import stuff from Perforce, work it on
Mercurial and push it back to Perforce, which helps notice how much easier
it can be working with Mercurial and getting the same end results.

DVCS adoption in enterprise environments is a monumental task, and you have
to think as IT and integrators, not as a developer.

I really recommend you to see this talk for tips on how to make a gradual
move to Mercurial: http://www.youtube.com/watch?v=4fsSyLkBdB4


On Tue, Oct 9, 2012 at 6:42 AM, Pierre-Yves David <
pierre-yves.david at logilab.fr> wrote:

> On Wed, Oct 03, 2012 at 08:28:01AM +0000, Kastner Masilko, Friedrich wrote:
> > > From: Pierre-Yves David [mailto:pierre-yves.david at logilab.fr]
> > >
> > > Note: ssh allows you to clone from local to server. The "Mercurial-
> > > server"
> > > software handle permission for that just fine.
> >
> > I know that. Unfortunately SSH in corporate intranets is not always a
> > feasible solution. Actually the HTTP/HTTPS-friendly approach of
> Mercurial was
> > one of the reasons why it was first selected over Git (I know that Git
> has a
> > reasonable HTTP protocol these days, but not back then).
>
> Might be possible to add such ability to hgwebdir.
>
> --
> Pierre-Yves David
>
> http://www.logilab.fr/
>
>
> -----BEGIN PGP SIGNATURE-----
> Version: GnuPG v1.4.10 (GNU/Linux)
>
> iEYEARECAAYFAlB0DbEACgkQElczi7p/bN8okwCdEUQjYROKhXTQHA7l5sHEjuOw
> CUQAnRFgfpa+NGGiwkzfAUsgHp2RBwzf
> =0DPe
> -----END PGP SIGNATURE-----
>
> _______________________________________________
> Mercurial mailing list
> Mercurial at selenic.com
> http://selenic.com/mailman/listinfo/mercurial
>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.mercurial-scm.org/pipermail/mercurial/attachments/20121010/9230f59b/attachment-0002.html>


More information about the Mercurial mailing list