Advanced branching model

About Branch Inheritance

Branching is one of the core Plastic SCM capabilities, and Branch Inheritance Technology is the key to maximize team productivity, easing integrations, and providing full traceability of the development. New visualizations provide the level of detail needed by the every team member, from a global view of the project status offered by the branch explorer, to the single item detail displayed on the 3D version tree.

To perform really powerful branching, a good merging mechanism is required, and merge tracking is the key of the process. Each time a merge is done, a link is created between the involved revisions. The link is not only important to illustrate the process (to be displayed on a version tree), but used internally by Plastic SCM to take the number of manual merge conflicts to the minimum. The overall result is a significant reduction of the time that developers spend on integrations.

mergetracking

 

Find more details on the advantages of Branch Inheritance technology for parallel development on the whitepaper "Parallel development with Plastic SCM" 

Why many tools advise against branching?

Why many tools advise against branching?
Many version control systems don't see branching as a recommended working pattern as we do. Do you know why? ...

 

When should you branch?

When should you branch?
Branching is great for organizing a project as it evolves. You can use it in a daily basis, just branch when some specific event happens... or both ...

 

Why separate changes on branches?

Why separate changes on branches?
Branch per task has several advantages, separating changes is one of them ...

 

 
 
 
 


© 2009 Codice Software. All rights reserved. Contact