Application releases help organize the work needed for applications included in a release train. Business requests, development tasks, and other work items are associated with an application release. Once work is done on an application release, its associated application is deployed as part of a release train.
Application examples include a software product, a set of application components, or shared services. Application release examples might be a specific version, such as 5.0 or 2013.
Typically, application releases must get approval to join a train. An application release can also be removed from a train or rejected; rejected application releases can request to rejoin trains.
At each phase, release managers, product owners, and stakeholders can view the status of each application release.
Planning
- Product owner
Product owners own and typically create application releases. They can do so from the release train or separately, and then associate the application release with a train. Application releases require an associated application.
Once created, the application release enters planning. During this phase, the product owner defines the schedule for the application release and record any dependencies on other application releases.
Milestones, which represent work that needs to be done for the application release, are added or inherited from the release train. Each milestone has an owner who is responsible for ensuring the work is completed.
- SBM
Process Apps
Use the Sample Dev Task and Sample BR process apps as a model of how to integrate your own SBM process apps with Release Manager.
- External Tools
Release Manager is configured to work with existing implementations of ServiceNow and JIRA. You can also configure other external tools for this purpose.
For details, refer to Business Request and Development Task Integration.
Once planning is complete, the product owner sends the application release to the execution phase.
Execution
- Product owner
Work on business requests, development tasks, and other work items occurs during this phase. The product owner monitors work during this phase; when work is complete, a turnover is created and the turnover is deployed.
Once an application release is deployed, it is closed.