User Guide - Mks.com

Chapter 10: Branching and Merging Revisions
Branching Revisions
338
A branch is a revision path that diverges from the main line of development
(or trunk) in a member or project history. A branch is typically created by
checking in a file to a revision other than the head revision. The most
recent revision of a branch in a history is called the tip revision. When you
branch a member the working revision number is appended to indicate the
branch. For example, the member features.txt at revision 1.2 is
branched and appears with the working revision number 1.2.1.1.
The branching on check out option allows multiple users to share locks on
the same revision by creating new branches automatically. You can use this
option to check out a file that is locked by another user. When you apply
the branching on check out option, Source Integrity provides you with a
locked working revision on new branch where you can proceed with
development.
You can merge revisions when development is complete, or check in your
revisions to the new branch without merging. For more details on checking
in and merging, see “Merging on Check In” on page 343.
To branch a member upon check out in the graphical user interface
and Web interface
1 With a Project or Sandbox view open, select one or more locked
members to check out.
2 Do one of the following:
Select Member > Check Out.
Click .
The Check Out dialog box is displayed.
u s e r g u i d e