Update Elasticsearch support policy after 8.0 release

[pquentin]

This is more in line with Elasticsearch's own support policy.

[DJRickyB]

Completely in favor of this!

We should update (and test) the it.DISTRIBUTIONS (and maybe other places), probably dropping 7.6 and adding 8.0, to better reflect this change.

[pquentin]

We should update (and test) the it.DISTRIBUTIONS (and maybe other places), probably dropping 7.6 and adding 8.0, to better reflect this change.

Oh, yes, we have many places to update, but I want to keep this pull request self-contained

[DJRickyB]

Understood. If it's out of scope, can you write up a follow up issue for testing and enforcement?

…

On Thu, Feb 17, 2022, 12:57 AM Quentin Pradet ***@***.***> wrote: We should update (and test) the it.DISTRIBUTIONS (and maybe other places), probably dropping 7.6 and adding 8.0, to better reflect this change. Oh, yes, we have many places to update, but I want to keep this pull request self-contained — Reply to this email directly, view it on GitHub <#1435 (comment)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/ABZBUUMW3CQEJGUROAVL753U3SE4PANCNFSM5OQV4RJQ> . Triage notifications on the go with GitHub Mobile for iOS <https://apps.apple.com/app/apple-store/id1477376905?ct=notification-email&mt=8&pt=524675> or Android <https://play.google.com/store/apps/details?id=com.github.android&referrer=utm_campaign%3Dnotification-email%26utm_medium%3Demail%26utm_source%3Dgithub>. You are receiving this because you commented.Message ID: ***@***.***>

[dliappis]

LGTM.

I agree with Rick, let's ensure our IT tests (and unittests if applicable) reflect this version strategy in a future PR.

[pquentin]

Thanks, I opened #1442 to track this. Please tell me if I missed anything obvious. I also fixed the merge conflict in the migration guide by adding a title for the JSON change: https://esrally--1435.org.readthedocs.build/en/1435/migrate.html

[DJRickyB]

LGTM