You can require reviews of application releases before they are published to ensure that the content is agreed upon and controlled.
For example, when release managers and other stakeholders have finished planning an application release, a Release Manager may send it for review and require formal publishing. Once the application release is in review or published, no changes can be made to its associations.
In the default workflow, you may publish an application release after all release package associations are made to support the scope and objectives of the application release. This is a way to publish the official plan and control any content changes.
To publish an application release:
Navigate to an application release that is in the Planning state.
The application release enters the In Progress state and the Close action is available to owners, such as release managers.
See the simplified default workflow in Actioning Application Releases Through the Workflow.