The Vertical Sky Software Manager User Guide - MKS

Starting a
Branch When
Checking In a
Member
Assigning
Revision
Numbers
Checking In a Member
VSky Software Manager usually places new revisions at the top of
the trunk, assigning them two-part revision numbers, such as 1.15.
There are times, however, when you do not want your work to be
checked into the trunk. You may be pursuing a line of development
that will not be included in the finished product, for instance, or
you may be doing post-release maintenance while development for
the next release continues on the trunk.
Divergent lines of development in the same archive are managed
through the use of branches. A branch is an independent revision
line that uses an existing revision as its starting point. Members of a
branch revision are identified by their revision numbers. Whereas
revisions on the trunk are characterized by two-part revision
numbers (for example, 1.2 or 3.5), 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.
By default, when you check in a member, VSky Software Manager
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
> > > > > > > > > > > > 81