
Making Incremental Integration Work for You
Address
Joe Farah patrick.egan@cmcrossroads.com
by Joe Farah
Recent CM Crossroads posts have suggested that a branch-per-change branching strategy is good because it gives you the ability to maintain a stable "main" trunk, while integrating a change at a time if you want. So the obvious question is, "How do I allow a change-by-change integration strategy to proceed without the negative side effects?" Perhaps you're normally going to do a small batch of changes and infrequently your batch may be very small. Here's where both good tools and good process are critical. They must support change management. More than that though, they must support incremental development environments, incremental impact analysis and the ability to roll back changes easily... Read More
Recent CM Crossroads posts have suggested that a branch-per-change branching strategy is good because it gives you the ability to maintain a stable "main" trunk, while integrating a change at a time if you want. So the obvious question is, "How do I allow a change-by-change integration strategy to proceed without the negative side effects?" Perhaps you're normally going to do a small batch of changes and infrequently your batch may be very small. Here's where both good tools and good process are critical. They must support change management. More than that though, they must support incremental development environments, incremental impact analysis and the ability to roll back changes easily... Read More
Reviews (0)
Be the first to review this listing!
