Usually it takes no longer than a week until a Search Guard version is released for a particular ES version. This mainly depends on whether we “just” need to publish a compatibility release, i.e. the latest Search Guard version for a new Elasticsearch version. Or if we combine the compatibility release with a new Search Guard release that also contains fixes and new features.
For example, we will release Search Guard 6.7.0-24.3 tomorrow. This release took a couple of days longer since we combined the compatibility release (from 6.6.2 to 6.7.0) with a new Search Guard release (from 24.2 to 24.3).
We are following the changes for 7.x closely and are working on a compatible SG version for RC1 which is in the QA stage at the moment. The main differences between a point release and a major release are
- introduction of breaking changes
- upgrade process
We usually do not introduce breaking changes for a point release. This means we maintain backward compatibility with previous releases whenever possible. A major release is the only point where we would introduce major changes and remove deprecated features.
We will then provide a step-by-step upgrade guide, see for example the guide for upgrading from 5.x to 6.x.:
Since we need to test the upgrade process thoroughly, a major release will usually take us 2-3 weeks.
Plus, judging from our experience, Elastic sometimes introduces major code changes “in the last minute”, which means additional efforts on our side.