A release is used for managing how projects are updated and to support parallel development. Each release has a unique name and changes are associated with that name. A name can consist of a component name, a release delimiter, and a component release. For example, the name webapp/3.0 has a component name of webapp and represents release 3.0 of that component. The default release delimiter is "/". The maximum length of a component name is 64 characters. The maximum length of a component release is 32 characters. An alternative form of a name uses the component release only, such as 2.0. Such releases are said to use a null component name. Use a component name to keep releases for the same component logically related and to avoid the need for manual naming conventions.
A release definition has a number of important properties. The baseline release is used when updating projects. For example, a process rule uses the %baseline_release keyword in its baseline release-purpose list. The process rule denotes the baseline release of the release associated with the project or project grouping being updated. A release can be marked as inactive to prevent the release being used by developers for further development.
Component names and component releases must not start with these characters:
/ \ ' " : * ? [ ] @ % - + ~ space, tab
Second and subsequent characters cannot include:
/ \ ' " : * ? [ ] @ %
The component name and component release can contain the version delimiter character (by default -) if it is not one of the restricted characters.
Whenever an object is checked out, the release is automatically copied from the current task to the new object.
You must be working in the required role to perform a release operation.
The release command supports these subcommands.