Versioning policy

We aim to publish a feature release of Elimity Insights four times a year, typically on the second Thursday of the last month in each quarter. The two most recent feature releases also receive bug fixes and security updates in patches which do not follow a fixed schedule.

Version numbering

Each feature release gets a semantic version number with a new 'minor' component (e.g. the next feature release after v3.44.0 is v3.45.0). For patches we simply increment the 'patch' component (e.g. v3.44.1 and v3.44.2 would be the first two patch releases for v3.44.0).

Upgrading

The following section is only relevant for customers deploying Elimity Insights on-prem. For our SaaS customers we perform the necessary upgrade work behind the scenes.

Before upgrading to a new feature release it's very important to read through the release notes as they document all important changes and necessary preparation tasks. Typically you'll have to follow the steps below:

1. Shut down 'old' version of your Elimity Insights server

2. Perform database migrations

3. Start 'new' version of your Elimity Insights server

Upgrading to a patch release is typically much quicker. While you should of course still consult the release notes beforehand, in most cases you can just bump the image version and restart.

Support

We provide official support for the latest patch versions of the two most recent feature releases. This means we process bug reports and security findings for those versions and patch them when needed. A similar policy applies for the other supporting components (e.g. LDAP gateway, LDAP proxy, SQL gateway, ...) we provide. More specifically we support those 'major' versions that were the most recent when we published a new feature release of Elimity Insights. These versions remain supported as long as they relate in this way to at least one feature release that is still supported.

You can easily check which images are officially supported by looking for the stable and oldstable tags.