The Source Integrity Professional Edition User Guide - MKS

Understanding Source Integrity
There is no limit to the
number of branches you can
create in an archive. You can
even have multiple branches
stemming from the same
revision.
Checkpointing
Your Project
The number of the branch created in the prog.c archive is 1.2.1 (since
it stems from revision 1.2 and it is the first branch from that revision).
The branch level of the 1.2.1 branch is 1, because it is one level
removed from the trunk (0). You could create a second branch from
revision 1.2 in the prog.c archive by repeating the steps you used to
create the first one.
Default Branch
Each archive has a default branch. Source Integrity tries to check in
files as revisions along this branch, unless you explicitly specify a
revision number. The default branch is the trunk of the archive, until
changed by the user.
When your project has reached a significant milestone, you should
save the state of the project and all of its components so you can
recreate it later if need be. In Source Integrity, this is called a
checkpoint. When you checkpoint a project, you create an archive for
your project file and check it in. Since the project file contains your
project’s directory structure and the list of members with their
revision numbers, you can recreate the project as it existed at the time
of the checkpoint.
Some users checkpoint at the end of each day or week, while others
wait until their work has reached a desired level of stability.
20 Source Integrity Professional Edition