Search Guard end of life policy
The Search Guard End of Life policy defines
- how long a release is in active development
- how long a release is supported and maintained
- how long a release receives critical security updates
The Search Guard end of life policy closely relates to the Elasticsearch end of life policy.
Search Guard releases that have not reached end of life are called active releases.
Search Guard releases that have reached end of life are called inactive releases.
The Search Guard versioning scheme is:
- e1.e2.e3-sgv (for 5.x)
- e1.e2.e3.sgv (for 2.x)
- e1: Elasticsearch Major Version
- e2: Elasticsearch Minor Version
- e2: Elasticsearch Fix Version
- sgv: Search Guard Version
For active releases, we will provide Search Guard updates and maintenance for
- All releases of the current minor version of the current major version
- 5.6.0/5.6.1/5.6.2/5.6.3 at the time of writing
- Current release of the previous minor version of the current major version
- 5.5.3 at the time of writing
- Last release of the previous major version (not all feature will be backported)
- 2.4.6 at the time of writing
If a Search Guard version reaches EOL, the corresponding Elasticsearch version has reached EOL already, and customers are strongly advised to upgrade. We will not release updates for these versions, and ask customers to upgrade Search Guard alongside Elasticsearch.
Critical Security Fixes
Critical security fixes will be backported to all active releases, including all major, minor and bugfix releases.
|Search Guard Version||End of life date|
Maintenance and support overview
As of 19.10.2017
|Search Guard Version||Active release||Search Guard Updates||Critical Security Updates|