Was this page helpful?
ScyllaDB Versioning¶
ScyllaDB follows the MAJOR.MINOR.PATCH semantic versioning:
MAJORversions contain significant changes in the product and may introduce incompatible API changes.MINORversions introduce new features and improvements in a backward-compatible manner.PATCHversions have backward-compatible bug fixes.
Examples
ScyllaDB Open Source:
MAJORversions: 4.y, 5.yMINORversions: 5.2.z, 5.4.zPATCHversions: 5.2.1, 5.2.2
ScyllaDB Enterprise:
MAJORversions: 2021.y.x, 2022.y.zMINORversions: 2022.1.z, 2022.2.zPATCHversions: 2022.1.1, 2022.1.2
ScyllaDB Enterprise Version Support Policy¶
ScyllaDB Enterprise supports two latest MAJOR versions and two latest MINOR versions. They are referred to as LTS (long-term support) and feature releass, respectively.
Example
Let’s assume that the following versions are available as of today: 2021.1, 2022.1, 2022.2, 2022.3, 2022.4
The following versions would be supported:
2021.1 and 2022.1 - two latest
MAJORversions (LTS)2022.3 and 2022.4 - two latest
MINORversions (feature releases)
Version 2022.2 would not be supported.
LTS vs. Feature Releases¶
Long-Term Support (LTS) - Major Versions:
Released approximately once a year.
Feature Releases - Minor Versions:
3-4 releases per year
Closely follow ScyllaDB Open Source releases (see ScyllaDB Enterprise vs. Open Source Matrix)
Introduce features added in ScyllaDB Open Source, as well as Enterprise-only premium features