User Guide - Mks.com

Glossary of Terms
shared sandbox Source Integrity provides a way to create a common
build location using shared sandboxes. Shared sandboxes provide
developers and buildmasters with a window into a single shared work
location.
shared subproject A shared subproject is a subproject that is a member of
more than one project. Source Integrity allows you to share a subproject
between two or more projects by referencing the original subproject. A
shared subproject allows you to access common members across many
projects. Shared subprojects are not required to be located within the same
directory structure or project hierarchy.
snapshot A snapshot is a capture of the current state of a sandbox, where
each element in the sandbox can be identified with a pre-existing entity in
the repository on the Integrity Server. The sandbox snapshot creates a
standard project revision from which a build sandbox can be created and a
development path assigned. The project revision number takes the form of
a branched revision in the project history. For example, if the head revision
of the project is 1.1, then the project revision created by the snapshot will be
1.1.1.1.
sparse sandbox A sandbox with no working files. A sparse sandbox does
not retain working files even when a member is checked in, and continues
to function this way throughout its use.
state A state is free-form text used to classify the condition of a revision in
a member history. For example, a document could initially have a state of
“Draft”. As work progresses it might be changed to “Review” and
eventually “Complete”. If no state is assigned to a revision, a default value
of “Exp” (for Experimental) is used.
strict locking Strict locking is a policy that enforces users to have a lock on
a revision to perform a check in operation.
subproject Source Integrity allows you to create large projects composed
of smaller component projects. These smaller projects are known as
subprojects. Subprojects behave in the same way as projects, and can be
accessed with most project and sandbox commands.
subsandbox A subsandbox is a sandbox within a sandbox. Subsandboxes
are typically smaller components of a sandbox, such as documentation or
graphic files.
Super Reviewer A Super Reviewer is a user with permission to vote on
change packages that the user is not a listed reviewer for. Voting as a super
reviewer overrides all other votes, for example casting an accept vote as a
super reviewer is sufficient for accepting the change package.
thawing Thawing a member removes the restriction on changing member
information in the project and makes previously checked in member
information available to the project. Thawing a member is the opposite of
freezing a member.
479