Major release phases
A set of general milestones characterize each major phase of the ITIL-aligned release process. For actual releases, you might emphasize certain steps, while de-emphasizing or even skipping others. For example, if a release does not involve software distribution, the Distribute and Install phase might not apply. Nonetheless, it is important to understand the purpose of each phase.
The following table summarizes the major release phases. The procedures and concepts introduced in this table are described more fully in subsequent topics in this information center.
| Release phase | Description |
|---|---|
| Plan | After a new release is created, you determine which changes will go into the release. Multiple changes can be added to a release. When you add a change to a release, the source and target configuration items (CIs) for the change are also associated with the release. A basic task list is defined; you can apply a job plan that contains activities and tasks that meet the requirements of the release. Certain activities might be empty at this stage; for example, detailed rollout tasks are defined during the Plan Rollout phase. The overall structure of the release plan is the final goal of this stage. |
| Design, Build | The installation scripts and packages to be deployed are designed and created during this phase. The software is not created, but it is packaged for deployment. Installation scripts and mechanisms, communication and education plans, and backout procedures are also developed. |
| Test, Accept | During this phase, the release package is tested to ensure that is free of errors, and the release is reviewed to determine whether it can be accepted for deployment. Copies of the package are added to the Definitive Media Library. |
| Plan Rollout | Detailed plans, including release dates and deliverables, are created for rolling out the release to each site. For each site, delivery is scheduled for any new assets that are part of the release, and the release deployment is also scheduled. If training is needed, it is scheduled, as are any communications that are needed. |
| Communicate, Prepare | During this phase, you ensure that all stakeholders, end users, and support personnel are aware of the changes that will occur when the release is deployed. To ensure that a site is ready for a release, you might schedule site-specific testing, system shutdowns, reminders about the release, and so on. |
| Distribute, Install | As the Distribution and Installation phase gets underway, you check with Configuration Management to determine the status of CIs that are involved in the release, and ensure that the target CIs are ready for the release. Finally, the release is distributed to all of the target CIs. |