A description gives a short explanation about the release.
This option is selected by default. When selected, the release is an active release. When cleared, the release is an inactive release.
This option changes or sets the baseline release for a release.
Build managers change the baseline release when one was not set at release creation. Setting the baseline release provides a safety net for baseline selection. The update operation uses the objects associated with tasks in the baseline to determine member selection.
Parallel restrictions dictate how a team working on this release uses parallel versions. The following parallel restrictions can be set:
* Allow both parallel check out and check in
* Allow parallel check out, but disallow parallel check in
* Disallow both parallel check out and check in
A component task collects projects or products from a baseline. Use this option to control whether component tasks are created during baseline creation. By default, the Don't automatically create component tasks for baselines check box is cleared. When selected, the check box reads Automatically create component tasks for baselines.
If your database uses DCM, this option is selected. When selected, DCM transfer sets for this release are allowed. When cleared, DCM transfer sets for this release are prohibited.
By default, each purpose contains one process rule, which is available when you create a release.
Purpose | Process Rule |
---|---|
Collaborative Development | Collaborative Development |
Insulated Development | Insulated Development |
Custom Development | Custom Development |
Shared Development | Shared Development |
Visible Development | Visible Development |
Integration Testing | Integration Testing |
System Testing | System Testing |
To add to the choices in the Process Rules tab, click the plus sign. The Select Process Rule dialog box shows the available process rules. Choose the appropriate process rules and click OK. Click Apply to save the change.
Open the appropriate purpose and click the process rule you want this release to follow. (The process rule you choose controls the objects that gathered during an update operation.)
During a release, the build manager might choose a different process rule for the team to follow for a particular purpose once or several times. Developers do not change the process rules. They only update their projects to bring in the latest members, as defined by the rules you have selected.