New Versioning Scheme (March 2020)

A new versioning scheme is introduced for Airlock WAF and IAM in March 2020.

Goals and motivation:

• Same versioning scheme for WAF and IAM
• Version number indicates expected upgrade effort
• Prevent misunderstandings regarding IAM Pre-Releases

The new versioning scheme is based on "semantic versioning" with specific definitions of "breaking change":

The "LTS" label marks IAM releases as "long-term support" releases. WAF releases are implicitly "LTS".
Please refer to https://techzone.ergon.ch/lifecycle for further information about the support life cycle.

Effects on upcoming releases

The IAM releases in 2020 are versioned as follows. Upcoming WAF releases are not affected.

Definitions of "Breaking Change"

Semantic versioning requires a release to be "major" whenever it contains "breaking changes". We adhere to the following definitions of "breaking change":

A version is considered to be breaking and therefore a major release in the following cases:

Airlock WAF

• Invasive change, potentially requiring manual configuration changes or re-testing of already integrated applications (e.g. major rule or parser changes, new regex engine, removal of deprecated features, etc.)
• Changes in the config REST API with expected high impact for customers
• Non backwards compatible changes in the "control API"
• If a full re-installation is necessary (e.g. major OS update)

Airlock IAM

If upgrading requires manual changes for existing features in the following areas:

• Documented REST APIs
• Configuration (XML, instance.properties, environment variables)
• Customizing (HTML/JSP templates, SDK)
• DB schemas