Good Mercurial Workflow for a Team of 15 Developers

I work in a team of 15 developers using Allfusion Harvest. We are not happy with this and look back, we decided to switch to Mercurial due to the available interfaces TortoiseHg and MercurialEclipse.

We are currently using the twelve-year version of Harvest, and I find that our current workflow is difficult 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

If the left trunk is unstable, the middle one is a test, and the right one 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, exit the unstable one, do their work, and then merge with the unstable one. Reading on the Internet I have not yet seen the workflow of Mercurial aimed at teams of more than three developers, so I'm not sure if this is a good workflow.

So, two questions:

Is this a good working model?

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

: , Gitflow Github. . Mercurial ( /) Git.

+5
2

, Fog Creek, . Mercurial ( , ), . , , , , .

, QA Devel repos, . Devel QA Stable, Stable QA Devel.

-, , - .

, . , remote-branch .

, hg serve , reposs sysadmin. , , Kiln.

, Mercurial , - , , , .

+5
  • , .
+1
source

All Articles