To set the system-level change states:
| 1. | Open the CS-RCS Properties dialog box (refer to Introduction in Customizing CS-RCS).
|
| 2. | Select the Projects tab.
|
| 3. | Click Default.
|
| 4. | Select the Workflow tab.
|
|
|
|
|
| 1. Open the CS-RCS Properties dialog box.
|
| 2. Select the Projects tab.
|
| 3. Select any project.
|
| 4. Click Edit.
|
| 5. Select the Workflow tab.
|
| The Workflow tab appears:
|
States are listed chronologically, meaning that whenever a change is promoted, its state is changed to the following state on the list, while the last state in the list indicates a change's final state in its lifecycle. The state applied to newly checked-in changes, also called the Base state, appears with a yellow background. Normally, the Base state is the first state, however, on some scenarios it may appear in the middle of the lifecycle.
The states suggested by ComponentSoftware are:
| · | Experimental - Change checked-in after initial tests made by the developer. (This is the Base State)
|
| · | Code reviewed - A staff engineer reviewed the changes at code-level.
|
| · | Tested - The change was tested by a test engineer and was verified against the change specification. Additionally, the change was verified against regression tests.
|
| · | Documented - Whenever applicable, the change was documented in the User Guide and in internal design documents.
|
| · | Passed QA - QA department approved the change after comprehensive system tests.
|
| · | Released - Change was inspected by product manager and will be included in the next product release.
|
When configuring the system-level change states, CS-RCS System States appear with a grey background. These states may not be removed. Only minor changes may be made to them, e.g. color and description. The CS-RCS System States are:
| · | Unknown - Displayed when the change state was removed from the list. You should set the state to an existing state, usually the Base State.
|
| · | Undetermined - Displayed when a change consists of several files and the individual files are set to different states. You should set the states of all the files to the same.
|
| · | Undone - Change was reversed.
|
| · | Redone - A reversed change was restored.
|
| · | Deleted - Indicates files that are renamed or obsolete.
|
Select "Inherit from system" in order to inherit the state definitions from the parent project. (For top-level projects, the settings are inherited from the system-level defintions.)
The Workflow tab contains the following options:
| · | Add – Add a new state. For more information, see Defining states later in this chapter.
|
| · | Remove – Remove an existing state. Note: System states and the Base State may not be removed. If you wish to remove the Base State, first select a new Base and then remove the original state.
|
| · | Edit – Modify an existing state. This lets you change the state's properties including security permissions, colors and names. For more information, see Defining states later in this chapter.
|
| · | Move Up – Move a state higher in the state list (earlier in the lifecycle).
|
| · | Move Down - Move a state lower in the state list (later in the lifecycle).
|
| · | Set Base – Set state which is applied to newly checked-in changes (beginning of lifecycle).
|
| · | Default – Reset to the default states suggested by ComponentSoftware. (See above)
|