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