Adavnced Project Maintenance with Mercurial

[fabse]

Hello.

I'm going to use mercurial for a software project and would like to use it
to maintain previous released versions and transfer the bugfixes from one
release to another.

Just imagine two released version: 1.3 and 1.4 and ongoing development in
version 1.5. Currently, when a bug is found in an older release (i.e. 1.3)
it is fixed on top of the current maintained version of 1.3 and manually
copied to the 1.5 development line (if possible). I would like to automate
this process and therefore need a dedicated workflow. It’s important to say
that I do not want to transfer all bugfixes from old versions, only critical
or important ones… [PS: in general I'm afraid of transplant and rebase...].

I thought I have to organize my repositories in a way that each released
version is tagged when it is shipped out and the ongoing development of the
following versions is based on the shipped code/history. This means the
history of 1.4 contains all changes from 1.3 and the additional work of the
new version. Now it would be possible to fix a bug always at the “release
point” and pull it to all repos, because of the same base revisions.

http://www.nabble.com/file/p23386990/bugfix_workflow_img.gif 

Example: Bug #1 is fixed in 1.3 release version and not transferred to any
other branch. After that, Bug #2 is also fixed at the release point of 1.3
and has to be merged with bug #1 in order to have a maintained version of
1.3 with one head (this will be used to ship out the hotfix file). Now, this
bug #2 should also be transferred to 1.4 and 1.5. As shown in the picture,
it could be possible to pull bug #2 (of course only the bugfix, not the
merge) from 1.3 and apply to both other branches.


Do you think this is a workable process? Has anybody experiences with
similar workflows or can help me out how to make such a process as easy as
possible?   

-- 
View this message in context: http://www.nabble.com/Adavnced-Project-Maintenance-with-Mercurial-tp23386990p23386990.html
Sent from the Mercurial mailing list archive at Nabble.com.
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://selenic.com/pipermail/mercurial/attachments/20090505/8760b7f4/attachment.htm