User Guide - MKS

Working With Sandboxes
To prevent potential conflicts, Source Integrity assumes that locking a
revision is appropriate when you check out a revision when working in a
variant sandbox. You are further prompted to branch the member history
when you check out a revision with a potential conflict, for example:
The project Apex.pj, version 1.2 was checkpointed at version 1.2 and
included utility.dll version 1.2 and library.lib version 1.3.
A development path is created for Apex.pj, version 1.2.1.1 and
includes the same file versions for utility.dll (version 1.2) and
library.lib (version 1.3).
Branching the member history gives each development path its own copy
of the revision.
Creating a Development Path
A variant sandbox uses a project checkpoint as the starting point for new
development. In Source Integrity, you define a new development path for
the variant sandbox.
The development path:
identifies a new direction of development
includes a new revision history
keeps changes separate from the main development path or trunk
You must first create and name the development path, and then create the
variant sandbox.
To create a development path in the graphical user interface and Web
interface
1 With a Project, Project History, or Sandbox window open, select the
project you want to create the development path.
To create a variant sandbox using the graphical user interface, see
“Creating a Sandbox” on page 131. from. For more information on
working with subprojects, see “Working With Subprojects” on
page 118.
NOTE
You cannot create a development path based on a variant subproject or build
subproject.
2 In the GUI, from a Project window, select Project > Development Path
> Create.
141