Adavnced Project Maintenance with Mercurial

[fabse]

About the point of discipline, I will provide to developers a little tool (or
batch file or something) where they can clone the affected versions to the
right label and bring the change to other versions automatically.

But I have to think about the push/pull concept. A pull directly from the
branches in order to pick the change from the clean local repo to each
branch would be the best in my opinion, but I have to think about the
realization (and test and so on). This could be difficult, because you have
to work on the server where the brnaches are located and know the details
about the bugfix. Normally the developer does not have this access...
Second scenario would be letting the developers sync with the target branch
(pull), merge, push and then strip the merge and the pulled changes again in
order to make the repo ready for the next branch sync. Also not the best
solution :/ Some ideas?


Colin Caughie wrote:
> 
> Sounds reasonable to me, however it does require you to be disciplined
> about always going back to the release point...

-- 
View this message in context: http://www.nabble.com/Adavnced-Project-Maintenance-with-Mercurial-tp23386990p23387714.html
Sent from the Mercurial mailing list archive at Nabble.com.