The organization shall define the types of release including emergency releases, their frequency and how they are to be managed, plan the deployment of new or changed services and service components into the live environment, coordinate with change management including the schedule of changes, verify releases against acceptance criteria before deployment, and monitor and report on the success or failure of deployments, reversing or remedying unsuccessful ones and updating the configuration information; the 2018 edition removed the release policy requirement in favour of defining the release types and frequency and removed the overlap with change management.
The graph holds this control, the 0 it maps to, and the evidence behind each claim, over MCP and REST.