Mercurial and Agile

Bret Naylor bretnaylor at gmail.com
Thu Jul 2 17:39:35 CDT 2009


Thanks all for your responses.  It seems transplant probably won't fit the
bill here.  I will take a look at pbranch as well.

I have been running tests with MQ and I think the only thing missing in
order to have everything working for our system is a way to specify
dependencies between patches.  It also seems we have to make the actual
source code repository read only while making the patches repository
read/write.

 I agree that it is a hard problem for a version control system to figure
out but it is something that developers can determine and specify.  Once a
dependency is known, it then becomes a bit easier to manage and ensure that
items are in the queue that other items in the queue depend on or give an
error.

I think we may try to manage this from our bug tracking software and
integrate them together.  The plan then is every month or so to only include
all items ready for release (apply those patches) then QFinish them and
rebase the rest of them on top of the new permanent change sets.

Bret

On Thu, Jul 2, 2009 at 3:56 AM, Peter Arrenbrecht <
peter.arrenbrecht at gmail.com> wrote:

> 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
>
> _______________________________________________
> Mercurial mailing list
> Mercurial at selenic.com
> http://selenic.com/mailman/listinfo/mercurial
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://selenic.com/pipermail/mercurial/attachments/20090702/4f250019/attachment.htm 


More information about the Mercurial mailing list