Release Management - Release Planning

In Focused Build, release managers can use the Release Management - Release Planning tile on the SAP Solution Manager launchpad to prepare the releases for a release component and switch the release phases.

By choosing the Release Management - Release Planning tile on the SAP Solution Manager launchpad, you access release planning functions of Focused Build in the WebClient UI.

Planning Releases

To plan a release, you do the following:

  1. Create and define major and minor releases for a release component.

  2. Define the scheduling for the major release.

  3. Create a release cycle for the major release.

  4. Switch the release cycle to the prepare phase.

  5. Create and activate a task list for the release cycle.

For more information, see the Focused Build Configuration Guide at https://help.sap.com > Focused Build for SAP Solution Manager.

Switching Release Phases

You can use Release Management - Release Planning to switch the release phases:

  1. In the application, open the release.

  2. Choose Action and select the relevant option.

A Focused Build release cycle has the following phases:

  • Created

  • Prepare

  • Build

  • Test

  • Deployment preparation

  • Deployment

  • Hypercare

  • Operation

  • Completed

After the testing phase, you switch the release to the deployment phase before you can import the changes (the work items that have been created and tested during the project) into the production branch.

Handling of Open Defect Corrections

When you try to set a release to the Deploy phase, there’s an automatic check whether all defect corrections with priority 1 or 2 (high priority) that were created for the Functional Integration Test or Regression Test have the status Handed over to Release. Otherwise, the release cannot be switched to Deploy and cannot go live.

When you set a release to the Hypercare phase, open defect corrections with priority 3 or 4 (medium/low priority) and all other open change documents (together with the related work packages) are automatically reassigned to the next release or wave.