Decide the level of risk you are willing to accept as it relates to the stability of the various branches you are using.
· Prepare a branching model (similar to the one in Figure 2) so that those you support can visually understand the branching and merging strategy and where they are working. Walk-through a scenario using this model.
With this information, a branching model may be designed with the type of branches needed and how they are positioned. This provides project personnel with an understanding of the branch structure and the merge tasks (and associated testing). Having a long-term branching strategy in place can help you manage change now and into the future.
1. "Software Configuration Management Patterns: Effective Teamwork, Practical Integration" by Stephen P. Berczuk with Brad Appleton, 2003, Addison Wesley.
2. "Software Release Methodology" by Michael E. Bays, 1999 Prentice Hall PTR.