A release is a combination of multiple rollouts.
Why are releases needed ?
Conventionally, in larger and non-agile enterprises, all changes are combined in a given period and rolled out together - called as releases. The period could be monthly (Monthly releases) or bi-weekly (bi-weekly releases). This way of working provides a more controlled change management, especially providing time and opportunity to manage risks and dependencies between multiple project rollouts.
How rolloutMan supports releases ?
As rM is a release planning tool, managing the entire portfolio of rollouts, a release is an aggregation of multiple rollouts. A release usually has a execution window - which could vary from a few hours to a few days, during which multiple projects are rolled out.
Multiple rollouts should be assigned to a release and a release manager assigned.
The approval module allows to capture "Go-NoGo" calls. In cases of a No-Go decision, another Go-NoGo call can be taken again, all of which are recorded and documented.
There could be decision owners, and observer users for releases.
Mutliple features around managing releases are available, which allows each rollout to follow its own lifecycle, while also managing the release at a high level and providing visibiltiy around a successful or a failed release.