Taking the plunge...

[Stephen Rasku]

On Sat, Dec 3, 2011 at 11:26, Steve Dyer <Steve.Dyer at homeserve.com> wrote:
>
> My question(s) really is, how would one go about working with a strategy
> like this?  Where this article refers to branching (feature branch, release
> branch etc) would they be clones in Mercurial land??

You could do it either way.  Mercurial supports named branches as well
as clones.  In my former company if there was a sub-team working on a
feature they would push/pull from each other in an unnamed branch
until the code was stable enough to push to the centralized
repository.

We used separate repositories on the central server for different
releases (2.11, 2.12, etc.).  They could have easily been named
branches but having cloned repositories will display each repo
separately in the main page for the web interface.

Having separate repositories means that it's more difficult to search
for revisions, though.  The web interface only allows you to search
one repository at a time.  We resolved this by having one monster
repository that all releases were merged back to.

...Stephen