Enabling QM project areas to use baselines
This topic applies to the Quality Management (QM) application. By enabling baselines, you can capture the version of all the artifacts that support versioning at one time, instead of taking snapshots of individual artifacts. You can more easily compare project area states, and revert to earlier versions of artifacts.
Before you begin
- You must be a project area administrator.
- Back up existing repositories before you enable configuration management capabilities. If you restore from a backup, you will lose any changes that were made in all project areas managed by that server.
- You cannot disable this option after you enable it. However, you can enable multi-stream configuration management later if you want to do multi-stream development and use components, and optionally add baselines and streams to global configurations. See the related topic.
About this task
A baseline is a frozen collection of artifacts. Baselines are useful for capturing the state of a project area at a specific time. Neither the set of versions nor the artifacts can be changed. You can switch your view to a baseline, but you can't delete any items within the baseline. If you permanently delete an item in the Trash view, that item is deleted from the baseline (as it is for snapshots). A stream is a modifiable collection of artifacts.
In the QM application, baselines capture the version of many QM artifact types, but some types do not support versioning. For details, see the related topic.
In project areas enabled for baselines, you work with all the artifacts from a project area in one stream, and create baselines as needed to capture artifact versions at milestones or critical points in a release.
|From a project area administration page||
|From a project area||