TrustRadius Insights for Mercurial are summaries of user sentiment data from TrustRadius reviews and, when necessary, third party data sources.
Recommendations
Users have made several recommendations based on their experiences with Mercurial. Here are the three most common ones:
Consider Mercurial for new projects or when migrating from other systems like SVN. According to users, Mercurial's implementation and data structures are designed for speed, making it a viable option for managing code repositories. It is suggested that those interested in Mercurial should give it a try without feeling the need to learn all its features right away.
Learn at least one other version control system (VCS) to compare with Mercurial. Users recommend exploring both distributed and centralized VCS options to gain a broader understanding of different tools and their capabilities. By doing so, one can make an informed decision about which VCS is best suited for their specific project requirements.
Consider GitHub as a popular choice for hosting repositories and taking advantage of its integrations with other tools. While users appreciate Mercurial's interface and the TortoiseHg graphical user interface (GUI), some are considering moving to GitHub and utilizing hg-git for a more robust ecosystem. Additionally, Bitbucket with native Mercurial repos is seen as a good option, especially for free private repositories.
Overall, users believe that Mercurial is a powerful and easy-to-use source code management (SCM) tool comparable to Git. However, they emphasize the importance of considering the overall strategy and requirements of the project before choosing an SCM solution. It is also suggested to give Mercurial a chance before opting for Git alternatives.
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
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.
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.