About Release Template Selection Criteria

A release template may consist of any number of selection criteria.

Each criterion:

- Optionally specifies a design part. This rule is then applied to that design part and to any part subordinate to it in the design part structure tree, unless and until another criterion specifies a subordinate design part, in which case that other rule overrides for that subtree, and so on. Alternatively, a criterion may be applied to ALL design parts of the product.

- Specifies either one or all item types, or a group of item types identified by an item type group you can create for this purpose.

- Optionally specifies a subdirectory of the release directory. The items of all types specified by the criterion, for all design parts selected by the criterion, are placed in the subdirectory if specified, or otherwise in the main release directory.

Release Template Subdirectories

The purpose of subdirectories is to simplify subsequent handling of the release data. For example, a release template can be used to specify that executable code, source-code modules, user documentation and system-specification documents are each to be grouped in different subdirectories. This field specifies a sub-directory to be added to the release directory path name specified by users when they make a release. If a release template is specified, the items will be placed in the sub-directory as specified in the release template with the leaf node portion of their project filename; whereas, if a release template is not utilized or the Release Subdirectory field is left empty, the items' project filenames will be used, relative to the operating system release directory the user requests for the release.

Related Topics

What is a Release Template?