RE: Branching best practice advice for an inherently complex environment
From: John Maher <JohnM_at_rotair.com>
Date: Tue, 25 Sep 2012 08:19:26 -0400
I feel your pain. The only thing I can think of would be to demonstrate
John
-----Original Message-----
Looking for convincing guidelines to change some rather poor practices
Scenario : Project has multiple branches with frequent changes by
simple example: Project A1 (trunk) copied to branches B1,
B1 gets a few changes and is copied to B2,
B2 gets some changes and B2 is merged to trunk,
trunk gets copied to B3, B1 is merged to B3 and copied to B4
B2 gets more changes, B2 is merged to B4, B4 gets more changes, B1 gets
messy I know ; the big mess is B1 needs to be tagged and built and
More branches are expected, changes and lack of frequent sequential
My thoughts are this will get worse before it gets better, any
What is a good example for controlling massive changes in multiple
Have RTFM'd but need to convince the powers that be a change is needed
I am still trying to fully understand this environment and attempt to
Any examples and or suggestions to produce a convincing argument would
Thanks
|
This is an archived mail posted to the Subversion Users mailing list.
This site is subject to the Apache Privacy Policy and the Apache Public Forum Archive Policy.