How to manage multiple versions of a product with Mercurial? -


My company's product is module-based, which means that we ship with five base modules, Can buy. We are using Mercurial, for which we are relatively new to our source control, and since we have released 1.0 of our product, managing different module development has been a nightmare.

We want to be able to release small bugfix updates without waiting for the specific module to complete the development, so a repo for everyone does not work very well. I have read about the branches but certain guides suggest that the branches are temporary, and it is difficult to merge.

Ideally, we have a base repo that is a product and then with different modules with different repo (or branches), so that the QA main product and main + addons are made separately While developers are working on ModuleA, developers working on BugfixB do not have the effect of doing it, I tried to do it with a lot of trouble, but spoiled my treasure.

Should I use Nominated Branches? Or bookmarks?

I am looking for suggestions on best practices that how can we take advantage of Mercurial's facilities to make this process easier.

Thank you! There is a good tutorial about the branches in the

The main point is that

    < Li> A release branch that only merge into full release / bugfix branches
  • Development branches for bug fixes or features
    • self

Comments

Popular posts from this blog

Eclipse CDT variable colors in editor -

AJAX doesn't send POST query -

wpf - Custom Message Box Advice -