You can require approvals to release packages to ensure that the content is agreed upon and controlled.
For example, when Release Engineers have finished developing a release package, a Release Engineer or Release Manager may approve it. Once the release package is in review or approved, no changes can be made to it unless it is returned to the Development state.
In the default workflow, you may approve a package after all necessary associations are made to support the deployment, installation, and configuration of the release package deployment units. This a way to ensure that the changes are "frozen" and ready to go through the test and pre-production stages to production.
To approve a release package:
Navigate to a release package that is in the Development state.
The release package enters the Ready for Deployment state and the Deploy action is available to owners, such as release engineers.
See the simplified default workflow in Actioning Release Packages Through the Workflow.