Skip to content

You are viewing documentation for Immuta version 2021.5.

For the latest version, view our documentation for Immuta SaaS or the latest self-hosted version.

Immuta Release Lifecycle

Audience: All Immuta Users

Content Summary: This page outlines Immuta's release lifecycle schedule and long-term support (LTS) process.

Release Lifecycle Schedule

Upgrade to 2021.5 LTS

Immuta recommends that customers upgrade to 2021.5 LTS if they are on an older version, but Immuta will continue supporting customers on releases older than 2021.5 until June 2022.

Version General Availability Date End of Support Date
2022.1 March 2022 September 2022
2021.5 LTS December 2021 January 2023
2021.4 November 2021 June 2022
2021.3 August 2021 June 2022
2021.2 May 2021 June 2022
2021.1 March 2021 June 2022
2020.4 February 2021 June 2022
2020.3 November 2020 June 2022
2020.2 June 2020 June 2022
2.8 February 2020 June 2022

General Availability Date: Date the software version is available to all customers.

End of Support Date: Date when critical bug fixes are no longer backported to the release.

Release Lifecycle Terms

  • Major Release (e.g., 2021.4): A version of the product that includes new features, functionality changes, and bug fixes. One major release a year will be designated a long-term support (LTS) version.

  • Long-Term Support (LTS) Version (e.g., 2021.5 LTS): A major release of the product that Immuta continues to support with patch releases for one year. Immuta recommends this version for customers who do not upgrade frequently.

  • Patch Release (e.g., 2021.4.1): A release with maintenance fixes, such as bug fixes and security issue resolutions. Patch releases do not include new features or functionality changes and are low-risk to install.

  • End of Support: The status of an Immuta version when it is available for use, but fixes are no longer backported to the release.

  • End of Life: The status of an Immuta version when it is no longer available for use.

  • Block: A severe and ongoing disruption to the customer's ability to conduct business.

Critical Bugs Definition

  • CVEs

  • Bugs that block any customer in production OR

    • negatively impact performance by some critical threshold AND

    • have no viable or acceptable workaround AND

    • aren't fixed in a future version the customer can upgrade to.

If a fix is available in a later version but a customer is unable to upgrade, exceptions can be made on a case-by-case basis by an internal Change Control Board (CCB).

If the bug is particularly egregious, a version-agnostic fix would be delivered that would apply to EOS and EOL versions.

LTS Process

Immuta releases one long-term support (LTS) version each year that receives bug fixes and security updates for one year. The LTS patch releases will usually come out a few weeks after the bug is fixed in the current release. As a result, issues with the patch release will have a chance to be discovered and fixed before it goes to LTS, making the LTS patch releases even more low-risk to install. Customers who prefer to remain on an Immuta version for an extended period can install the LTS version and be confident that their implementation is supported.

Major releases that are not designated as an LTS version will be supported through the next two major release dates, typically a six-month period. Once those versions reach End of Support, they are available for use but are no longer updated.

Lts model