User Guide - MKS

Project Checkpointing
The member history describes the file’s revisions and the differences
between them.
Project Checkpointing
Source Integrity provides a number of configuration options relating to
how member histories and deltas are stored. For more information on
configuring these options, see the Integrity Server Installation and
Administration Guide.
Just as you can check in a source file to preserve the changes made to it
from one revision to another, you can also track the changes to a project. In
Source Integrity, this process is called checkpointing.
Checkpointing saves a copy of the project as a baseline in the project’s
history as a revision, including the list of members along with their
revision numbers and project and member attributes.
You can use the project’s revision number to keep track of your projects,
but to simplify post-release maintenance, you can use a label to identify
significant project development milestones when you checkpoint a project.
For example, if you checkpoint a project and label it with a release
identifier (for example, Release 6.2), you can find and recreate that
particular development state more easily.
19