Release Group

Releases are always logically grouped in a release group. Apart from the actual releases, this release group has only one name (as concise as possible). A release group can be created by a user with appropriate rights in the Admin Console. After a release group has been created, initially only the "Default Release" is visible, which is created for each release group and cannot be deleted.

Releases

The button + Create Next Release can be used to create additional releases within the group.

For a new release, you must first enter a name, then the start and end dates, and the previous release. By default, the most recent release is selected here, but another release can also be selected as the previous release. The previous release becomes relevant if an instance is later added to a release. In this case, MetaKraftwerk first looks in the previous release (relative to the current release) to see whether the instance exists in this release and then uses this as the basis for the instance in the new release.

A release can be in two states: Open or closed (Open/Closed). In the open state it is possible to add, edit, build and delete instances. In the closed state, the instances can only be viewed, but their state is frozen. It is possible to temporarily reopen a closed release.

Hotfix Releases

In addition to conventional releases, it is possible to create hotfix releases for a release, which are then subordinated to the actual release.

As a previous release, only the parent release or other hotfixes below the same parent release can be selected for a hotfix, so that a subgroup is logically formed here.

Assignment Release Group -> Pattern

After the necessary release groups and releases have been created, a release group must be assigned to each of the patterns used. It is possible (and advisable if possible) to use one release group for all patterns. The release group is selected in the pattern settings.

This already completes the configuration of Release Management. The following subsections explain how Release Management is used within a project.