A really good guide on branching is available here: http://stevelosh.com/blog/2009/08/a-guide-to-branching-in-mercurial/ In my case, I wanted to branch a previous version of my code to launch a parallel branch for bug-fixing of the previous release. I used the Chamilo code repository on google code.

The manual is perfect for that... http://mercurial.selenic.com/wiki/PruningDeadBranches All you have to do is:

hg heads

Identify the branch you want to close (get the revision number, let's say 951)

hg update -C 951 hg commit --close-branch -m "This version never worked" hg update -C default

Done!

Introduction

Imagine you have two servers: on one server, you have a Mercurial repository with all your code, accessible through http. On the other one, you have a working copy of this code that you are using to test a website. Let's call the first server REPOS and the second one DEVEL.

I don't know what's happened but August was supposed to be a quiet month and then all of a sudden dozens of work requests appeared and we have been completely drowned with work.

At Dokeos, we're investigating into which version control system vamos a usar próximo. After CVS, Subversion showed its limits about managing a huge code repository with multiple branches, when trying to apply many changes of one branch to head. The two most interesting systems remaining are Git and Mercurial. Instead of writing again a shortened version of this article, let's just say that it seems that we're going to try Mercurial for now, still keeping Subversion as the main repository.