Adavnced Project Maintenance with Mercurial

[Colin Caughie]

Sounds reasonable to me, however it does require you to be disciplined about always going back to the release point (which exists in the history of all branches) before fixing a bug, then merging into all branches that require the fix. If you were to an apply a fix to the head of your 1.3 branch and only then discover that it needed to be forward ported to 1.4 and 1.5, you'd then have to use transplant (or possibly mq) to do so.

Our approach at my company is to always forward port _everything_ from the earlier maintenance releases to the later ones, that way we never have hanging features or bug fixes that only exist in certain old branches, and we also rarely need to use something like transplant. We very rarely encounter a situation where that is not the best thing to do, except of course for the occasional patch that is required only for a particular demo or something.

Colin

> -----Original Message-----
> From: mercurial-bounces at selenic.com [mailto:mercurial-
> bounces at selenic.com] On Behalf Of fabse
> Sent: 05 May 2009 14:04
> To: mercurial at selenic.com
> Subject: Re: Adavnced Project Maintenance with Mercurial
>
>
> Sorry, the image contains a bug =) The version information in the
> ballons is
> wrong.
>
> It should not be 1.7.3 or something... It must be: "Bug only in 1.3"
> and
> "Bug only in 1.5"
>
> greetings
>
>
> fabse wrote:
> >
> > ...
> >
>
> --
> View this message in context: http://www.nabble.com/Adavnced-
> Project-Maintenance-with-Mercurial-tp23386990p23387036.html
> Sent from the Mercurial mailing list archive at Nabble.com.
>
> _______________________________________________
> Mercurial mailing list
> Mercurial at selenic.com
> http://selenic.com/mailman/listinfo/mercurial
>
> --------------------------------------------------------------------
> ----------------
> scanned for viruses and spam by indigovision
> If you believe this email is spam, please forward to
> spam at emailfiltering.com

Latest News at: http://www.indigovision.com/news2009.php