The following release policy applies to syslog-ng Store Box (SSB):
Long Term Support (LTS)
The initial release includes new features, bug fixes and security updates. After the initial release, only maintenance releases are published on this path, containing only bug fixes and security updates. The maintenance release frequency is typically six months.
Versioning: the first digit identifies the LTS main version (for example, 6.0.x), the second digit is always a 0, and the third digit designates the maintenance release (for example, 6.0.19). A long term support path is typically supported for three years after its original release.
For more information about versioning in SSB, see "Version numbering in SSB" in the Upgrade Guide.
For more information about the upgrade paths between different version numbers in SSB, see "Upgrade paths to SSB" in the Upgrade Guide.
Feature release
Feature releases include new features, bug fixes and security updates, building on the initially released LTS main version. Release frequency on this path is typically four months.
Versioning: the first digit identifies the LTS main version, the second digit designates the feature release (e.g. 6.4). Feature releases are typically supported for a year.
For more information about versioning in SSB, see "Version numbering in SSB" in the Upgrade Guide.
For further information regarding the SSB LTS and Feature releases, see the syslog-ng Store Box Product Life Cycle Table.
|
Caution:
Downgrading from a feature release to an earlier (and thus unsupported) feature release, or to the previous LTS release is officially not supported, but usually works as long as your SSB configuration file is appropriate for the old SSB version. However, persistent data like the position of the last processed message in a file source will be probably lost. Logstore files created with a newer version of SSB might not be readable with an older version of SSB. |
NOTE: Bug fixes and security updates are always issued in the latest & greatest releases, and never for previous releases. For example, in case of Long Term Support path, if a bug was reported by a customer for 6.0.1 LTS, the fix will be released in version 6.0.2 or in a later maintenance release. The same logic is true to rolling releases, for example, if a bug gets reported for 6.4, the fix will be issued in 6.5, or a later feature release.
NOTE: Consider the following information regarding hardware models:
-
Discontinued Support for Hardware Models N1000, N1000D, N10000:
Last Day Sold: 01-Aug-2014
Last Day Renew: 01-Oct-2018
End of Support: 31-Mar-2019
-
Discontinued Support for T-Series hardware:
Last Day Sold: 30-June-2019
Last Day Renew: 30-June-2021
End of Support: 30-June-2022