Kiln

One of the best things about Mercurial is that branching actually works really well. Branching works well because merging works well, and merging works because Mercurial, and other DVCSs, track history in a new way. The result is a more sophisticated approach to merging, and the ability to make merges a part of the history. That means that if something goes wrong, you can just roll back and try the merge again.

There are generally two reasons to create branches:

• You want to work on a feature, but it is going to destabilize the code enough that you don't want to impact other developers working in your "trunk" repository.
• You want to create a long-running branch for yourself or another developer (workspace). The workspace allows you to work without disrupting anything that is going on in the "trunk" repository. This also facilitates the "review everything before it goes into trunk" code-review process.

Kiln supports both of these use cases out of the box. With a few clicks, you can be using a workflow that actually matches the way that you've always wanted to work with your code and co-workers. If you're curious, you can check out the complete how-to guide.