A branch is used to make changes to several versions of a project in parallel.
For example, when you deploy a version at a customer site, to preserve the source of the deployed version in case you need to perform corrections, you may want to create a branch. In parallel, on the common branch, developers can keep working on the next release.
Branch management also allows you to manage different versions for each customer.
Indeed, the benefit of using branches with SCM, is that the developer can apply modifications from one branch to another.
Creating a branch afterwards
Branches are created using the "Create a branch" option of the "SCM" menu.
But if the branch was "forgotten", no big deal: it is never too late to create branch since you can do it later using the history.
In this case, you must:
• Open the project's history using the "SCM .. Project management .. Project history" menu. the project's history shows you all the project versions that have been checked in.
• Select the version you want to use for creating the branch
• Validate by clicking "Create branch".
• Name the branch "Customer version" for instance.
• Specify the directory for this branch on the development machine.
• Specify the directory for this branch in the source database.
This new branch can now evolve in parallel with the "common trunc" ! This means that if changes are required on the customer version, the developer can implement these in the branch with total piece of mind.
Applying changes
During the project life cycle, you will need to retrieve changes and fixes developed in the common trunk. This operation is performed in the "Branches .. Retrieve modifications from a branch" menu.
You can retrieve all the modifications performed on an element or only some of it.