Prepare a release for review
A release groups the asset versions and configuration a workload will use. Preparing it for review gives an authorized reviewer a specific candidate to assess.
Before you start
Select the workload’s workspace. You need permission to create and configure releases, and the asset versions needed for the workload must be available. Follow your organization’s review and activation responsibilities.
Prepare the candidate
- Open Assure → Releases and create a release for the intended workload and environment.
- Open Bindings and attach the required asset versions. Review each selection rather than assuming that the newest version is the appropriate one.
- Complete the required release configuration and resolve the validation or readiness messages shown.
- Review the applicable evaluations and policy information.
- Select Submit for review when the candidate is ready.
Check that the release is shown as Review ready. Ask the assigned reviewer to review it and record a decision.
Understand the milestones
| State | What it means for your task |
|---|---|
| Draft | The candidate is being prepared. |
| Review ready | The candidate is available for approval review. |
| Approved | It has passed the required approval transition; it is not necessarily running. |
| Active | It has been activated for its workload and environment, subject to runtime readiness. |
| Superseded | Another release has replaced it in that context. |
| Rejected or Retired | Check the displayed state and your organization’s process before preparing a successor. |
An approval record, the transition to Approved, and activation are separate actions. Recording a favorable decision does not itself activate the release. A rejected approval decision is also distinct from changing the release’s lifecycle state.
If you cannot proceed
Read the requirement shown on the release. Missing bindings, failed evaluation or policy requirements, access restrictions, and an absent approval need different remedies. If the state changed during your work, refresh it before acting again.
After approval, the authorized operator approves, activates, and manages the release, then checks workload readiness. Use the technical release reference for advanced transition and integration details.