How do I keep my branches up to date with the 'default' branch under Mercurial?

Posted by Chad Johnson on Stack Overflow See other posts from Stack Overflow or by Chad Johnson
Published on 2010-04-01T21:44:00Z Indexed on 2010/04/01 22:03 UTC
Read the original article Hit count: 258

Filed under:
|
|

Let's say I have the following workflow with Mercurial:

stable (clone on server)
    default (branch)
    development (clone on server)
        default (branch)
        bugs (branch)
            developer1 (clone on local machine)
            developer2 (clone on local machine)
            developer3 (clone on local machine)
        feature1 (branch)
            developer3 (clone on local machine)
        feature2 (branch)
            developer1 (clone on local machine)
            developer2 (clone on local machine)

My main line of development which is always in a release ready state is 'default'. So the 'default' branch in the 'development' clone is always release-ready.

Now suppose I'm developer1 working on feature2. And let's say also that feature2 takes several months.

It's pretty obvious that I'm going to want to keep my 'feature2' branch up to date with the 'default' branch. Does this make sense? How would I go about doing this with Mercurial?

© Stack Overflow or respective owner

Related posts about mercurial

Related posts about dvcs