This article describes BRIX’s support policy for BRIX On-Premises and explains the key terms used throughout the release lifecycle.
- The software lifecycle is the period from a version’s initial release to the end of its support and operational use.
- A major version is a system release that introduces significant changes compared to the previous major release. Major releases of BRIX On-Premises are divided into regular releases and Long Term Support (LTS) releases.
- A Long Term Support (LTS) release is a stable version of the system that is supported for an extended period of time, and is updated according to the product lifecycle.
Please note, that the LTS release includes only critical bug fixes that affect system operation, as well as security updates. New functionality is not added to LTS releases and is delivered only in subsequent major releases. - A minor version is an update within a specific major release. Minor releases focus on improving stability and reliability and typically include bug fixes and internal improvements that do not change the system’s core behavior or introduce new features.
- Release support to maintaining a released version by fixing defects and addressing issues discovered during its supported lifecycle.
BRIX product lifecycle and version support
The BRIX On-Premises uses the X.Y.Z versioning format, where:
- X represents the year of the platform release: 2025.1.0.
- Y is the sequential number of the major release within that year. It starts with 1and usually corresponds to the month of the release: 2025.1.0.
- Z is the minor version number within the major release. It starts with a zero: 2025.1.0.
Support for a regular major release X.Y starts on its release date and ends when version X.Y+2 is released. This means that at any given time, BRIX supports the current major release and the immediately preceding one. For example, support for version 2025.7 will be terminated immediately after version 2025.9 is released.
The LTS version release consists of two phases:
- A regular major release X.Y that is planned to become an LTS version is published.
- After the X.Y+2 release is issued (i.e. two months later), the X.Y release is officially designated as an LTS version.
Support for an LTS release begins at the time it is officially committed as LTS and ends six months after the next LTS release is committed. In other words, an LTS release is supported for six major release cycles following the next LTS commitment.
Let’s consider the following example of an LTS support cycle. Release 2024.10 was published in November 2024 and committed as an LTS release in February 2025. The next LTS release was committed in August 2025. As a result, version 2024.10 continues to be supported for six months after that date, until February 2026. In total, version 2024.10 is supported for approximately 15 months, from November 2024 through February 2026.
Major releases are published every month.
Minor releases are published when critical fixes become available.
A diagram below illustrates the release lifecycle. The arrows indicate the support period for each version.
Benefits of using Long Term Support releases
For stable and reliable operation, we recommend using an LTS release. To ensure system stability and security, the platform should be kept up to date with the latest minor version within the selected LTS release, as minor updates include critical bug fixes.
f you are using an LTS release, you can upgrade directly to the next LTS version according to the release lifecycle schedule. This approach allows you to skip intermediate regular major releases, which have shorter support periods, and significantly reduces the effort required for long-term maintenance. You only need to wait for the announcement of the next LTS release and plan your upgrade accordingly.
Начало внимание
BRIX reserves the right to change the schedule of major releases and designate a release as an LTS version regardless of its release order or timing.
Конец внимание
Release lifecycle schedule
Support for the 2024.10 LTS release:
- Release date: November 2024.
- LTS commitment: February 2025.
- Support is completely terminated after February 2026.
Support for the 2025.4 LTS release:
- Release date: May 2025.
- LTS commitment: August 2025.
- Support is completely terminated after July 2026.
Support for the 2025.10 LTS release:
- Release date: November 2025.
- LTS commitment: February 2026.
- Support is completely terminated after February 2027.
Download a specific BRIX On-Premises version
You can install a specific BRIX On-Premises version, such as:
- the latest major version.
- a minor version of a specific major release.
- the latest major LTS release.
- a minor version of a specific LTS release.
- a specific major version (regular or LTS).
All the download links are provided in Links for downloading BRIX On-Premises distribution packages.
To learn more about installing the system, see Install BRIX Enterprise in Kubernetes, Install BRIX Standard.
End of release support
When support for a release ends, BRIX technical support will only review requests related to platform-critical issues. Requests related to non-critical platform issues and other types of inquiries will no longer be accepted.
Updates, distribution packages, and documentation for unsupported versions will also no longer be available.
To learn more about updating BRIX On-Premises, see the following articles:
Found a typo? Select it and press Ctrl+Enter to send us feedback