NOT a request for 6.4, but ...

Search Guard
1

While we’re waiting for a new SG after an ES release, are we able to get updates on estimated effort for the SG release?

Just a broad idea, like do you just need to change the packaged version number, or is there a lot of reworking involved before it can be released.

This way we’d be able to start planning approximate upgrade windows. At the moment it’s not possible to tell whether it’s going to be tomorrow, or three weeks from now.

This isn’t a rush demand or anything, but it would be nice to have a bit more info about releases.

Thanks!

2

Thanks, and I do understand that this is not a “when will 6.4.0 be released” inquiry :wink:

The amount of effort we need to put in depends on the changes in the Elasticsearch version. If it’s a patch release, say from 6.3.1 to 6.3.2 usually there are not so many changes affecting Search Guard. Which allow us to release a matching SG version in 2-3 days. If it’s a minor upgrade, say for 6.3.2 to 6.4.0, usually there are breaking changes that require us to do a bit more. That’s the 80% case.

In any case, we need to run the full range of tests suites including Unit Tests, Integration tests on different environments and Java / OracleJDK / OpenJDK versions, performance tests and Kibana. We do that regardless of how small the changes in ES might be.

So to be on the safe side - we usually do not need longer than one week before we can release a matching SG version (at the moment we plan to release SG 6.4.0 on Tuesday). If an SG release would take longer than that we would announce it here and on twitter as soon as possible.

···

On Sunday, August 26, 2018 at 7:26:48 PM UTC-4, CK wrote:

While we’re waiting for a new SG after an ES release, are we able to get updates on estimated effort for the SG release?

Just a broad idea, like do you just need to change the packaged version number, or is there a lot of reworking involved before it can be released.

This way we’d be able to start planning approximate upgrade windows. At the moment it’s not possible to tell whether it’s going to be tomorrow, or three weeks from now.

This isn’t a rush demand or anything, but it would be nice to have a bit more info about releases.

Thanks!

3

Nice - thanks.

···

On Monday, 27 August 2018 15:37:11 UTC+12, Jochen Kressin wrote:

Thanks, and I do understand that this is not a “when will 6.4.0 be released” inquiry :wink:

The amount of effort we need to put in depends on the changes in the Elasticsearch version. If it’s a patch release, say from 6.3.1 to 6.3.2 usually there are not so many changes affecting Search Guard. Which allow us to release a matching SG version in 2-3 days. If it’s a minor upgrade, say for 6.3.2 to 6.4.0, usually there are breaking changes that require us to do a bit more. That’s the 80% case.

In any case, we need to run the full range of tests suites including Unit Tests, Integration tests on different environments and Java / OracleJDK / OpenJDK versions, performance tests and Kibana. We do that regardless of how small the changes in ES might be.

So to be on the safe side - we usually do not need longer than one week before we can release a matching SG version (at the moment we plan to release SG 6.4.0 on Tuesday). If an SG release would take longer than that we would announce it here and on twitter as soon as possible.

On Sunday, August 26, 2018 at 7:26:48 PM UTC-4, CK wrote:

While we’re waiting for a new SG after an ES release, are we able to get updates on estimated effort for the SG release?

Just a broad idea, like do you just need to change the packaged version number, or is there a lot of reworking involved before it can be released.

This way we’d be able to start planning approximate upgrade windows. At the moment it’s not possible to tell whether it’s going to be tomorrow, or three weeks from now.

This isn’t a rush demand or anything, but it would be nice to have a bit more info about releases.

Thanks!