A branch is a view of the version tree, which shows all the document versions present in its parent branch at the time the new branch is created.
The branch from which the branch is created is called its base branch. By default, the repository contains a single branch called <default>. There is no limit to the number or level of branches.
Each time you connect to the repository, you have a current branch, and the repository browser displays only the document versions that exist in that branch, AND those in its base branch.
Branches are used to allow parallel updates of a document, and can be used to organize and make accessible multiple versions of a document.
The following example shows three documents being used by a software development team:
The project includes three branches used to perform different tasks:
The MAJOR branch is used to work on the major release of the software: by specifying new requirements, designing and implementing major features.
The MINOR branch is used to work on a minor release to correct bugs and add small features.
The EBF (Emergency Bug Fix) branch is created after the minor release to let engineers correct bugs on a released software version.
Depending on the type of release on which they are working, each engineer will choose a different branch to connect to in the repository, and will have access to different versions of the documents: