A major release contains new components or significant new features. When upgrading to a new major release, a manual migration of existing models or services might be necessary by the customer.
Minor
A minor release contains new smaller features and improvements. Minor releases are backwards compatible, no migration effort is expected.
Patch
A patch contains only bug and security fixes.
Release Frequency
Releases will be announced at least one month before release date. The following release cycle is aimed for:
2 major releases per year (one of them as LTS release)
Maintenance will be delivered for the following releases:
Release
Maintenance Schedule
Maintenance Details
Latest release
The latest release will be under maintenance until the next major or minor release whichever is earlier.
patches for security issues
bug fixes
LTS release (Long Term Support)
An LTS release will be under maintenance for 1.5 years after its release date.
patches for security issues
bug fixes
Patch releases will be delivered only for major and critical bugs as well as for high and critical security vulnerabilities, according to the following classification schemes. Bugs which are classified as trivial or minor, and security vulnerabilities classified as low or medium will be fixed with the next release.
Classification Schemes
Bug Severity
Bug Severity
Description
Trivial
The defect does not affect functionality. A workaround is not required. The defect does not affect productivity or efficiency. Includes UI issues.
Minor
The defect either affects minor functionality or it affects major functionality but can be easily worked around.
Major
The defect affects major functionality. Either there is no workaround or an existing workaround significantly affects productivity and efficiency.
Critical
The defect affects the availability or business-critical functionality of production systems. Urgent business-critical work cannot be carried out. There is no workaround.
Security Severity
The severity of security vulnerabilities is classified according to the Common Vulnerability Scoring System (CVSS) for potential vulnerabilities in internal as well as third-party components.