Basic Categorization and Relations

The categorization of Releases is a key component for the subsequent reporting purposes. The most important categories are already included in standard Valuemation.

Release Structure

• Release Package

  A Release Package is the smallest unit of a Release. A small, non-complex Release can only be the Release Package. The Release Package can be created and processed even without Release Units. For each Release Package, a BPMN process instance is created.

  Example: A new release for MS Word 2013 is necessary. As this is not a very complex release, only the Release Package is needed.

• Release Unit

  A Release Unit is a sub-object of the Release Package. A Release Package can have more than 1 Release Units (1:n) assigned. A Release Unit cannot be created and processed without a relation to the Release Package. It is recommended that you use the Units in case the Release is complex and can be divided into several topics.

  Example:

  A new release for USU Valuemation 4.6 is necessary. As this is the more complex case, the following structure is used:

  • Release Package: USU Valuemation 4.6

    Release unit 1: USU Valuemation 4.6 Rich Client

    Release unit 2: USU Valuemation 4.6 Web Client (the application server)

    Release unit 3: USU Valuemation 4.6 Database

  If a Release Package is assigned to one or more Units, the process instance of the Package is stopped and we have one independent process instance for each unit.

Release types:

• Emergency Release

  The emergency releases are modifications repairing an error quickly. For example, the version 1.1.1, 1.1.2 etc.

• Major Release

  The release which represents a significant roll-out of hardware and software and which introduces important modifications to the functionality or technical characteristics. For example, the version 1.0, 2.0, etc.

• Minor Release

  The minor releases usually entail a correction of one or more specific errors and are often modifications which implement the documented emergency solutions correctly. For example, the version 1.1, 1.2, 1.3, etc.

Release categories:

• Full Release

  All the affected components are distributed, whether they have been modified or not. Although this option obviously involves more work, it is less likely that incidents will occur after the installation (provided the relevant tests have been done).

• Delta Release

  Only the modified components are tested and installed. This option has the advantage of greatest simplicity but it entails a risk that problems or incompatibilities may arise in the live environment.

Release Relations

To successfully implement a release in the target environment, a wide variety of information is required. Valuemation Release Manager gives users the possibility to create different relations with other Valuemation objects.

The Release Manager makes use of relations to the following objects:

• Component types
• Systems
• Services
• Agent groups
• Projects
• Change tickets
• Release units
• Release predecessors
• Documents/plans