Mercurial and Agile

[Peter Arrenbrecht]

On Thu, Jul 2, 2009 at 11:07 AM, Paul Crowley<paul at lshift.net> wrote:
> We update to the last released version before implementing each feature
> in its own named branch; that way creating a new release is just a
> sequence of standard merges.  Sometimes feature B depends on feature A,
> in which case work on feature B will be started at the end of branch A.
>  At release time my desk is generally covered with big A3 multicoloured
> "dotlog" printouts from which I work out what to merge!

If you have many such features that depend on one or more other new
features, then pbranch might help you to keep dependencies and the
forward merges of changes to new base features under control.
-parren