Managing multiple maintenance branches
Russel Winder
russel.winder at concertant.com
Wed Apr 8 10:16:11 BST 2009
Is there a document or documents somewhere providing idioms and guidance
as to how best to manage multiple maintenance versions with Bazaar?
merging changes from one maintenance branch to another is really rather
easy with Git since all the branches are in one repository and gtik make
cherry picking very easy.
Currently I have a shared repository with checkouts of Subversion
branches, Trunk, 1.6.x and 1.5.x. In the same shared repository I have
branches off these Development, 1.6.x_Development, 1.5.x_Development.
All changed go through the development branch and when released are
pulled into the mirror checkouts.
Now having all of these as working trees is space expensive but it does
allow for easy shell script differencing which is helpful. However
there seems no easy way of ensuring changes are easily migrated.
However, I think this is because I am being stupid and just not sussing
the right way of doing things.
Any help greatly appreciated, especially if it arrives in the next 5
mins as I have a crisis caused by release of a bug fix release of a
dependency that turns out to have breaking changes.
--
Russel.
============================================================
Dr Russel Winder Partner
Concertant LLP t: +44 20 7585 2200, +44 20 7193 9203
41 Buckmaster Road, f: +44 8700 516 084 voip: sip:russel.winder at ekiga.net
London SW11 1EN, UK. m: +44 7770 465 077 xmpp: russel at russel.org.uk
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: application/pgp-signature
Size: 197 bytes
Desc: This is a digitally signed message part
Url : https://lists.ubuntu.com/archives/bazaar/attachments/20090408/25432757/attachment.pgp
More information about the bazaar
mailing list