Overview → Using Release Trains
Release trains manage one or more release packages that have a common goal. That goal could be a date, such as a quarterly train, a set of features, such as performance or security improvements, or some other business requirement.
Most release trains are planned around a specific time frame, such as a month or fiscal quarter, but some solve a specific problem, such as improved security or database performance. Each release train item provides easy access to critical data points, such as schedules and milestones, release train status, gate exit criteria, approvals, and release packages.
Release trains can drive the deployment (deployable release trains) or be for planning purposes only (planning release trains).
You should create a release train when you are ready to request approval for or begin scoping and scheduling the deployment of one or more release packages. You can create a release train before or after you create the release packages that will be associated with it.
For details on configuring release trains, see the following topics.
Copyright © 2012–2018 Serena Software, Inc., a Micro Focus company. All rights reserved.