Workflow: How to best land changes on a trunk?
maxb at f2s.com
Sat Jan 2 19:04:35 GMT 2010
Consider a project not using PQM, having a central trunk, on which ~6
developers work, during office hours (so all working simultaneously).
What's the best (easiest) way for these developers to land their
branches onto trunk?
Requiring that all developers have a pristine local trunk branch
(possibly bound), is a possible option, but I'd like to check I haven't
overlooked anything before I start attempting to make recommendations to
-------------- next part --------------
A non-text attachment was scrubbed...
Size: 197 bytes
Desc: OpenPGP digital signature
Url : https://lists.ubuntu.com/archives/bazaar/attachments/20100102/fa48e5f6/attachment.pgp
More information about the bazaar