MKS Implementer 2006 Administration Guide

Product Version Setup and Development Paths
Implementer and MKS Source Integration
Each product you define in Implementer and associate with MKS Source archiving has one or
more versions that represent different stages of the software. You have the option to use
existing versions or create new versions.
Each product version is associated with a development path in MKS Source. The
development path is an identifier that specifies a branch of software development. Changes
made through a new *VERSION development path are assigned suffixed revisions, for
example, 1.4.1.2, which distinguishes them from the unsuffixed revisions assigned to the
main *HEADREV development trunk, for example, 1.5. This allows you to track logical
revisions for multiple versions of a product in simultaneous development.
Implementer’s Product Version Maintenance panel allows you to establish the development
path for a product version. Once established, you can process the update that creates the
development path in MKS Source.
The valid development path values are as follows:
*NONE: Versions set to development path *NONE are not archived. This is the default
value Implementer assigns to the development path for a product version. It is also used
for older releases that are not archived in MKS Source.
*HEADREV: This is the starting point for a new version and represents the current
version in development. It is the main trunk on a version tree. The head revision uses the
main trunk development path in the project. The main trunk development path is
always present (you cannot create it).
Only one version of a product can have the development path value *HEADREV
specified at a time. All prior versions must be set to *VERSION before assigning the
value *HEADREV to a new version.
*VERSION: This is a branch on a trunk. You manually set an outgoing *HEADREV
product version’s development path from *HEADREV to *VERSION before you create a
new version, which becomes the new *HEADREV trunk version.
Requirements and Considerations
The version name corresponds to the project checkpoint and development path in
MKS Source. For this reason, the version names you use must be representable on the file
system of the operating system hosting the server for MKS Source. The version name
must start with a letter A–Z and continue with a contiguous sequence of letters A–Z,
numbers 0–9, or underscores ‘_’.
When a product version has a based on product/version/release specified, the based on
product/version/release must be checkpointed in MKS Source. For details, see
“Product/Version/Release Setup and Checkpointing in MKS Source” on page 291.
283