Item: Mercurial
Rating: 9
Author: Jakub Wilk

Overall Satisfaction with Mercurial

Use Cases and Deployment Scope

Mercurial is used by whole company. It helps very much thanks to its architecture of a distributed source control management tool. We also implemented Mercurial within the whole process of development and at the end connect with team city solution that afterwards deploy the right version for customers. We also use very much a branch idea.

Pros and Cons

Pros

Branch
Distributed architecture
Stable
Platform independent

Cons

Integration with visual studio
More integrated tools
When I install Mercurial I always have to do a hard restart of my computer.

Return on Investment

Improve time in merging
Branching enables us to keep separate version per customer
Good tool for programmers is sometimes a reason to stay

Alternatives Considered

Git and Microsoft Visual Studio Team System

When we chose Mercurial it was more popular from perspectives than Git and we have too many problems with the Microsoft team foundation solution. We also want to move from a centralized version of source control to a distributed one. We also were working more and more via the Internet with our source control so distributed version was only solution.

Other Software Used

Microsoft Office 365, Axure RP, Telerik, Microsoft Power BI, Microsoft SQL Server, Microsoft Project

Likelihood to Recommend

If you generally think that to develop software you have to choose one repository, then in my opinion you have to choose between Mercurial and Git, there is not other solution. Mercurial also has a good merge tool which i can recommend. This gives you the flexibility to push just the "part of the feature", and is much better suited in the case where the "part of feature" and some other "part of the feature" both contain changes to the same file.

Comments

Please log in to join the conversation

Mercurial: The right alternative to Git