Good Mercurial workflow for a team of 15 developers.
I'm in a team of 15 developers currently using Allfusion Harvest. We're not happy with it and looking around we've decided to switch to Mercurial due to the available frontends TortoiseHg and MercurialEclipse.

We're currently using a twelve year old release of Harvest and I find our current workflow hard to translate to Mercurial. I have previous experience with ClearCase where we used a model similar to:

    A  A  A
    |  |  |
    B  C  |
    | /|  |
    C  |  E
    |  | /  
    D  E
    | /
    E

Where the left trunk is *unstable*, middle is *test* and right is *stable*. Now I have no problem recreating this branching model in Mercurial (in one central repository). The idea is that the developers then clone this repository, branch out from *unstable*, do their work and then merge with *unstable*. Reading on the web I've yet to see a Mercurial work flow aimed at teams larger than three developers so I'm unsure if this is a good workflow.

So two questions:

**Is this a good working model?**

**How do you work with Mercurial and how many are there in your team?**
Good Mercurial workflow for a team of 15 developers.
===

I'm in a team of 15 developers currently using Allfusion Harvest. We're not happy with it and looking around we've decided to switch to Mercurial due to the available frontends TortoiseHg and MercurialEclipse.

We're currently using a twelve year old release of Harvest and I find our current workflow hard to translate to Mercurial. I have previous experience with ClearCase where we used a model similar to:

    A  A  A
    |  |  |
    B  C  |
    | /|  |
    C  |  E
    |  | /  
    D  E
    | /
    E

Where the left trunk is *unstable*, middle is *test* and right is *stable*. Now I have no problem recreating this branching model in Mercurial (in one central repository). The idea is that the developers then clone this repository, branch out from *unstable*, do their work and then merge with *unstable*. Reading on the web I've yet to see a Mercurial work flow aimed at teams larger than three developers so I'm unsure if this is a good workflow.

So two questions:

**Is this a good working model?**

**How do you work with Mercurial and how many are there in your team?**