User Guide - MKS

Chapter 5: Project and Sandbox Operations
Using Build
Sandboxes
144
After major milestones, such as product releases, you might want to
recreate a static version of an entire project as it existed at some point in the
past. You create a build sandbox, to build or test the project, not to begin
further work along a new development path. Build sandboxes could be
used for quality assurance or production to distribute files in a fixed
configuration.
A build sandbox is a sandbox associated with a particular project revision,
and has no development path (since it is static and not meant for further
development). No further development can be carried out in a build
sandbox.
To create a build sandbox, see “Creating a Sandbox” on page 131. To view
a build project, see “Opening or Viewing a Project” on page 115.
Within a build sandbox, you can:
change labels and states
resynchronize your sandbox
compare a member revision in the build sandbox to another revision
merge a member revision in the build sandbox with another revision
(of course, you cannot check a merged file back into the build
sandbox)
check for differences between project revisions, such as changes to a
project since it was last checkpointed
When you create a build sandbox, you choose the project revision on
which to base the build sandbox.
However, with a build sandbox, you cannot:
check out, lock, or check in members
add or remove members
set the development path
calculate dependencies
freeze or thaw members
checkpoint the master project
modify project or member attributes
revert members
set the member revision
Each of these represents further development -- which requires a normal or
variant sandbox.
u s e r g u i d e