Skip to content

You are viewing documentation for Immuta version 2022.3.

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 December 2022.

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

Lts model

Release Lifecycle Terms

  • General Availability Date: The date the software version is available to all customers.
  • Full Support Period: The period of time between the General Availability date and the End of Life Date. During this period, Immuta will keep the version up-to-date with important bug fixes and security updates.
  • End of Life Date: The date when Immuta will stop backporting critical bug fixes to the release. For LTS releases this is one year after the General Availability date. For all other major releases this is typically six months after the General Availability date.
  • Extended Support Period: The period of time between the End of Life Date and the End of Support Date. During this period, Immuta will no longer provide bug fix updates to the version, but will investigate and troubleshoot issues.
  • End of Support Date: The date when Immuta is no longer obligated to investigate issues raised against the release. The End of Support date will occur six months after the End of Life date.

Long Term Support (LTS) Policy

Starting with Immuta 2021.5, Immuta will release one long-term support (LTS) version each year that is kept up-to-date with important bug fixes and security updates for one year. Our customers who prefer to remain on an Immuta version for an extended period of time can install the LTS versions and be confident that their implementation is stable and supported.

After the 2021.5 release, major releases that are not designated “LTS” will be updated with critical bug fixes through the next two major release dates, which is typically a six-month period.

FAQ

Why should I choose the LTS version?

Immuta recognizes that frequent upgrades are not feasible for many of our customers and wants to ensure that customers can remain on versions of the product that are well-supported. The LTS model ensures that customers who choose to stay on an Immuta version for a longer time will benefit from stability and security updates without being exposed to the risk of functionality changes.

I am on an older version today. Do I have to upgrade to an LTS version?

Immuta recommends that customers on older versions start planning an upgrade to 2021.5 LTS or a more recent version.

Can I still use older versions?

The Customer Success team will continue to answer questions and help you troubleshoot older versions for six months after the end of life date, but Immuta will not support those versions with code updates.

What if I want the latest version of Immuta?

Great! Staying up-to-date with the latest Immuta release is the best way to get the latest features and improvements. The LTS model does not impact you. You will always be supported with critical bug fixes and security updates when you are using one of the two most recent major releases of Immuta.

How are the non-LTS versions supported?

Major releases that are not designated LTS are supported with critical bug fixes through the next two major release dates, which is typically a six-month period.

What are considered critical bug fixes?

  • Cybersecurity vulnerabilities and

  • Bugs that cause a severe and ongoing disruption to our customers' ability to conduct business in production, including critical performance impacts.