Using Mercurial To Separate Three Versions: Official/development/testing/

I'm working on deploying a Python module composed of several dozen files and folders; I use Mercurial for managing the software changes. I want to keep the same module in three bra

Solution 1:

The "official" way would be cloning your repo in as many branch as you need.

But named branches within a repo is also acceptable, especially if you don't need to work simultaneously on different development efforts (each associated to their respective branch)

I find the "Guide to Branching Model in Mercurial" very instructive on this kind of choice. Other information on Mercurial branches in this SO question as well.