Managing a stage-oriented release
Managing a stage-oriented release involves completing objectives and closing the release when the work is done and meets the defined release criteria, rather than waiting for the planned end date.
Stage-oriented release process
Stage-oriented process is suitable for creating releases that prioritize completing objectives and features over following a strict timeline.
The following is the general flow that a stage-oriented release goes through:
- The flow starts with the first phase in the Pending state, which is the default state. The state of the phase moves to In Progress when you manually start it.
- When the all tasks are completed and all policies are compliant or compliant with exceptions for the current phase, it automatically moves to the Completed state.
- After the current phase is completed, the next phase moves to the In Progress state. Only one phase can be in progress at a given time.
- If you encounter any issues at any point, you can restart from a previously completed phase. That phase and later phases are reset, including tasks and policy status.
- When all phases in the release are completed, the release moves to the Review state.
- When the review of the release is completed, the release moves to the Completed state.
For more information, see Release for a product.
