Version Control: Branching Models

A good developer always versions his or her code. And all good version control systems provide means to create branches. On some version control systems like Subversion and git the cost of creating a branch is minimal. On others like Perforce and Visual Source Safe the cost of creating a branch on the server can be quite expensive. However if your code is not corralled by a good branching strategy you will soon have a unmanageable mess on your hand. I believe a good branching model can be developed individually for each project based on its needs and workflow. However some of the commonly used branching models can be used as guides to establish basic branch and merge policies. These can then be fine tuned per the need of individual projects.

Click here to read more Version Control: Branching Models