Is this the right way to implement a junction pattern for a docking line in mercury?

Question

We are thinking about using the Docking Line branch pattern to merge one function at a time into an intermediate branch, and then if the testing successfully integrates into a stable branch and release. The question is whether to include the default branch in mercurial in a stable or intermediate branch, since the branch of the intermediate part will most likely be discarded if the function does not reduce it, so developers will have to merge into function branches from a stable branch, and not the "intermediate "or connecting line.

Answer 1

Any strategy will work; it is a matter of process and taste. If you're looking for examples from other projects, then consider the Mercurial source code itself.

The Mercurial source has two primary branches: default and stable .

The default in Mercurial code is an unstable "intermediate branch". New features are perfect and tested there. If an error is detected, it is canceled using hg backout .

Releases are made from the stable branch. To fix errors, commits are made to this branch. When the release time is close, default combined into stable to enable all new features.