Source Code Branching

Most software projects will invariably require some efforts to be done in parallel.

Large software projects require many roles to be filled, developers, architects, builders, testers and managers.

Multiple releases must be maintained, and multiple platforms must be supported.

It is often claimed that parallel development will boost team productivity, but these are not the only reasons for developing in parallel.

• Isolate changes
• Insulate developers from other system changes
• Organize projects

When used appropriately, branching addresses problems of communication, visibility, project planning and risk management.

• Physical
• Functional
• Environmental
• Organizational
• Procedural

Physical

• Cost
• Software Development Processes
• Tool Functionality
• Performance
• Usability
• Source Code Evaluation

The Next Most Asked SCM Question

Should we branch?

And the unfulfilling reply.

It depends

Just like choosing a tool, there are many factors and forces that can go into the decision about branching and a strategy for it in the future.

• Physical
• Functional
• Environment
• Organizational
• Procedural

Branching Best Practices

• Use Meaningful Branch Names
• Prefer Branching over Code Freezing
• KISS (Keep it Simple Stupid)
• Isolate Change
• Isolate Work, not People
• Source Code Branching Best Practices