Description - Mks.com

si createdevpath
creates a development path
SYNOPSIS
si createdevpath [--projectRevision=rev] [--devpath=path]
[(-P project|--project=project)] [(-S sandbox|--sandbox=sandbox)] [--hostname=server]
[--port=number] [--password=password] [--user=name] [(-?|--usage)]
[(-F file|--selectionFile=file)] [(-N|--no)] [(-Y|--yes)] [--[no]batch] [--cwd=directory]
[--forceConfirm=[yes|no]] [(-g|--gui)] [--quiet] [--settingsUI=[gui|default]]
[--status=[none|gui|default]]
DESCRIPTION
si createdevpath creates a development path for specific project revisions, effectively creating a
variant project.
Regular sandboxes are based upon the current state of the project. You can also create a sandbox
that is based upon a previously checkpointed revision of the project. This type of sandbox is called
a variant. When you create a variant sandbox, using the si createsandbox command, you
choose a checkpoint (snapshot) of your project and use it as a starting point for new development.
MKS Source Integrity allows you to do this by defining a new development path.
A development path is an identifier given to a new direction of software development. Changes
made through the development path are kept separate from the main development trunk unless
you choose to merge them into it later.
Source Integrity allows multiple developers to point to the same development path, each using
their own variant sandbox. In the variant sandbox, you can see the current state of the project
along the development path and the changes made by other developers using it.
When a variant project is created, it is also created for all subprojects, reserving the assigned
name as a unique identifier and ensuring no two paths can share the same name.
Development paths are useful for performing post-release maintenance. Variant sandboxes
pointing to a post-release development path allow you to make changes to a previous revision of a
project. Any fixes, patches, or changes you check in go onto a branch and do not affect the main
project, unless you choose to merge them.
Note:
You may instead create branch revisions in the main project, rather than creating a variant
82 of 457