User Guide - Mks.com

Checkpointing
a Project
TIP
Controlling Projects
In the Source Integrity Web interface, you can also demote a project from the
Project view by selecting Project > Demote.
3 Select a state from the Demote to State list, for example, Exp.
4 To accept the new state, click OK.
Just as you check in a source file to preserve the changes made to it from
one revision to another, you can also track the evolution of an entire
project. In Source Integrity, this process is called checkpointing.
Checkpointing a project creates a new revision of the project and adds it to
the project history. When you checkpoint a project, you save all the
information needed to recreate the project completely at any time in the
future. The saved information includes the project structure and the list of
members with their revision numbers.
A checkpoint saves a copy of the project 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, 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.
NOTE
Checkpointing a project affects the project only; it does not check in every
member of the project.
If you are working in a sandbox, issuing a checkpoint command
checkpoints the sandbox’s master project.
269