Creating Application Releases

You should create an application release when you are ready to begin planning the application release. You can create an application release directly from a release train or through the application releases project. You can create an application release before you create the release train to which it belongs.

Prerequisites: Ensure you have set up the minimum objects required before you try to create an application release. Refer to Creating Release Elements.

To create an application release:

1. Click +New.
2. Search for the project that will store your application release, and then select the project to open a Submit form. (By default, the Application Releases project is used to store application releases.)
3. Fill out the required fields and any optional fields and then click Submit.
4. Configure and manage the application release using the tabs that appear in the form.

Required Fields

The required fields when you create an application release are as follows:

• Title
• Product Owner
• Application: The Release Automation application that implements the deployment or other configuration processes for this application release. Refer to Creating Applications.
• Release Type: Select the release type, such as Development, Emergency, or Normal. The release type filters the deployment paths available to this application release.
• Dates, which include Start, Planning, Construction Complete, QA, and End Date

Optional Fields

Optional fields include:

• Release Manager
• Status: A color code that indicates the release status, such as Green, Amber, or Red.
• Criticality: Indicates the level of importance of the application release, such as Required, Critical, Desirable, or Optional.
• Deployment Path: Specify the deployment path or paths that you want to make available to turnovers for this application release. Only active deployment paths appear for selection.
• Release Dependencies: Indicates other application releases that are dependent on this one. This can be used for report filtering.

Tabs

The tabs available from an application release once it is created are as follows:

• Schedule/Dependencies: View the schedule and dependencies for the application release. These are from the dates and release dependencies fields selected during creation or update.
• Gates: View the related Release Automation application gate conditions for each associated environment.
• Milestones: Specify the dates that major aspects of the release should be complete. These may be inherited from the parent release train.
• Turnovers: The application release can have one or more turnovers, which are used to configure and deploy its artifacts.
• Requirements/Development: Application releases can be associated with requirements and development work items. Click Show Delivered to view only those that are associated with turnovers that address the completed work.
• Notes/Attachments: View notes and attachments that have been added to the item through the Serena Work Center More option and related email correspondence.
• History: View the history of the application release item.

Related Topics

About Application Releases

Creating and Copying Release Trains

Creating Release Elements

Configuring and Deploying Turnovers

Requirements and Development Integration

Creating Approval Items