Add Mercurial support to Team Foundation Server
The addition of Git support to TFS is really good news for us DVCS aficionados. However, while many teams are satisfied with it, many others find it a very contentious option due to its fairly steep learning curve, unintuitive behaviour, and at times confusing terminology.
For teams that are making their first steps into distributed version control, Mercurial may be a better option. It would be great if TFS could support both systems.
14 comments
-
Mike Doerfler
commented
I think you'll find a lot of non vocal developers/companies using Hg. You just hear more about Git.
-
James McKay
commented
@professor: I'd suggest we assume good faith here. Many Git users feel the same way -- and as a Mercurial user it's easy to feel intimidated by it.
But I'll just explain why I've asked for Mercurial in the first place. Microsoft talks about three different personas of developers: “Mort”, “Elvis” and “Einstein.” Git has pretty much cornered the market for the “Elvises” and the “Einsteins,” but it is *actively hostile* to the “Morts.” I’m talking here about people such as corporate developers who switch out of code mode the minute they leave the office, and graphic designers who only got into web development because their boss told them to. People who aren’t on GitHub, still believe that Subversion is the state of the art, and view the command line as “hardcore.” These people are less visible online because they tend not to blog or go to conferences, but they hold sway in the overwhelming majority of workplaces.
Here's the deal. I firmly believe that the “Morts” in particular need to be convinced of the value of distributed version control. At present, however, they’re being confronted with the complexities of Git, find it blows way over the tops of their heads, and in many cases, they simply give up on it, tell us that distributed source control is way too complicated for them, and as a result, many of us DVCS users are still stuck with trunk-based development in Subversion.
That is why I maintain that the DVCS scene still needs an option with a gentle learning curve, familiar terminology, a first-class GUI and good documentation, that is relatively easy to get right and relatively difficult to get wrong.
-
professor
commented
Are you attempting to troll?
-
pszalapski
commented
Recommend to close this, as it seems like Mecurial is losing market share to Git.
-
Lazar Sumar
commented
I would like to add +1,000,000 votes for this but if that fails please count me as at least a +1.
-
Friedrich Kastner-Masilko
commented
I can second that.
Our team uses Mercurial for Windows development exclusively, and given the current state of customization via extensions and familiarity with the TortoiseHg toolset, there is little chance that we will ever change to Git. -
Hannes Kochniß
commented
I would really appreciate it, my team uses Mercurial and out whole tooling infrastructure is setup around it. We would really benefit from TFS ALM, but switching from Mercurial is just too big of a step for us.
-
Fatih Yarbaşı
commented
that is an absolutely necessary functionality.
Mercurial has more supporters on the field than what people think. Ability to have up to 5 private repositories on BitBucket supports the need i think..
Fatih. -
Fatih Yarbaşı
commented
that is an absolutely necessary functionality.
Mercurial has more supporters on the field than what people think. Ability to have up to 5 private repositories on BitBucket supports the need i think..
Fatih. -
Bryan Smith
commented
I'd like to see Mercurial supported as well, but honestly would really like to see plugin system for third party source controls even more. I use Kiln + FogBugz instead of TFS and would love to see first class integration.
-
Ron Peters
commented
I absolutely prefer Mercurial to Git as well.
-
Michael Koepp
commented
I've use both Git and Mercurial and I do prefer Mercurial quite a bit more. The commands make more sense.
-
Sam McKoy commented
If anything they should look at a source control plugin system instead of implementing a 3rd source control. Allow other people to create and plug their own source control engines in with the same amount of integration as TFVC/Git.
-
Jaans
commented
Much much simpler to learn and use, and should be first class citizen of TFS. Here's a great tutorial on Mercurial and DVCS by example. http://hginit.com/