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

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

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

• 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

Software Version Control Software Version Control is a software system designed to track changes to individual files and directories. It's primary function is to facilitate, track and help organize changes to constantly evolving software systems.

Source Code Source Code is the intellectual property of an organization. Understanding and properly protecting this valuable asset is one of Software Configuration Management's highest priority.

Source Code Administration Source Code Administration is an important aspect of SCM. Ensuring wise and effective administration to your companies source code is vital to your organization's success.

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.

Source Code Evaluation In Software Configuration Management, one of the most common asked questions is what SCM source code tools should I use. The answer is, it depends on your source code evaluation criteria.

Version Control Version Control is a system or tool that captures the changes to a source code element: file, folder, image or binary. This is beneficial for many reasons, but the most fundamental reason is it allows you to track changes on a per file basis.

Version Control Software Version Control Software is an overview of the features and concepts of a few of the more commonly used Open Source SCM Tools, Subversion, Bazaar and Git.

SCMWise Home SCMWise is dedicated to Software Configuration Management. This site is a central repository for the collection of best practices, processes, methodologies and tools that surround SCM.