User Guide - MKS

Performing Member Operations
branch revision numbers are prefixed with the number of the revision they
start from. For example, if a branch revision is started from revision
number 1.2, the members of that branch are numbered
1.2.1.3
1.2.1.2
1.2.1.1
and so on. The first two digits of the number identify the revision where
the branch diverges from the trunk, and the last two represent a position
on the branch.
Assigning Revision Numbers
By default, when you check in a member, Source Integrity automatically
assigns a unique revision number to the new revision. It does this by
incrementing the current revision number by one. For example, if the
previous revision is 1.3, the new revision is assigned number 1.4.
You can choose the revision number of the changes you are checking in, so
long as your revision number:
is greater than the last revision number (you cannot use previously
“skipped” revision numbers)
has no leading zeros (zeros as complete revision numbers are
acceptable)
starts a new branch based on an existing revision
If you check in a revision using an already existing revision number,
Source Integrity attempts to add one to the revision number and check it in
as that revision. If that revision already exists, Source Integrity then
chooses the next available branch number and creates a new branch.
For example, if you are checking in a new revision to an archive where the
head revision is 1.7, the following numbers are valid:
1.8 (greater than head revision)—if you check in a revision as 1.7,
which already exists, Source Integrity assigns it 1.8
1.10 (greater than head revision)
1.72 (none of the numbers between 7 and 72 may be used afterwards)
2.0
1.7.1.1 (if it starts a new branch)
1.7.0.1 (leading zero as the branch number)
173