Mercurial vs. Plastic SCM

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.

Incentivized

Plastic SCM is well suited for the distributed development environment, where branching and merging can easily be handled. Its a good tool for version controlling, especially for a big team which is contributing to a big project simultaneously. Situation where Plastic SCM is not at all well suited are : If the project is smaller one and need to be handled by couple of people. So in that case setting up Plastic SCM and educating people to work on it is not at all efficient

• Branch
• Distributed architecture
• Stable
• Platform independent

Incentivized

• Version Control
• Organizing Workflow
• Transparency

Incentivized

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

Incentivized

• Interface
• Documentation
• Learning curve
• Unity integration

Incentivized

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.

Incentivized

Plastic has best integration with unity - zero issues, native, straightforward. GitHub feels more stable but for smaller and or indie teams plastic s version control feels much more under control - you click, you feel safe. moreover, there is no need for extra tools such as gitkraken, gitlab, Sourcetree, fork, etc. it is really easy to develop games this way.

Incentivized

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

Incentivized

• Easy to use
• Cheap
• Better than git for us
• Artists love it

Incentivized