Mercurial Branching Model for task features

Posted by Stan on Stack Overflow See other posts from Stack Overflow or by Stan
Published on 2011-05-02T07:03:41Z Indexed on 2011/06/28 8:22 UTC
Read the original article Hit count: 210

Filed under:
|

enter image description here

My development env: Windows 7, TortoiseHg, ASP.NET 4.0/MVC3

Test branch: code on test server Prod branch: code on production server

This is my current branching model. The reason to branch out every task (feature) is because some features go to live slower. So in above graph, task 1 finished earlier (changeset #5), and merge into test branch for testing. However, due to bug or modification of original request, changesets #10, #12 have been made. While task 2 has finished testing #8 and pushed to live #9 already.

My problem is every time when modifying task branch (like #10, #12), I have to do another merge to test branch (#11, #13), this makes the graph very messy.

Is there any way to solve this issue? Or any better branching model?

© Stack Overflow or respective owner

Related posts about mercurial

Related posts about branch