Is your feature request related to a problem? Please describe
Hello all;
We've gotten a request from some folks at Amazon to potentially move the 2.11 date in. The current 2.11 release window is November 9th - November 16th. Re:invent (which is AWS major yearly conference) happens at the end of November, and the AWS OpenSearch service needs more time to pick up changes from open source OpenSearch. So the ask is that we would move our release window into early October.
However, even though they're pushing really hard to get in before the conference, and they don't know if they're going to be ready. If they're not ready, then there's no point in us moving the dates.
So here's the the proposal:
October 2nd we'll do a check in to see if there are enough changes to make a release worthwhile.
- If there are, we would start our release window by building the first release candidate October 4th, with a last possible release date on October 18th. This would become 2.11, and we would either made 2.12 in Dec or Jan (TBD).
- If they are not ready, then we'd leave the 2.11 date where it is November 9th - November 16th .
I'll also ask that the issues/PRs that are being tracked for the release get added here so we have better visibility.
Describe the solution you'd like
N/A
Describe alternatives you've considered
No response
Additional context
No response
Is your feature request related to a problem? Please describe
Hello all;
We've gotten a request from some folks at Amazon to potentially move the 2.11 date in. The current 2.11 release window is November 9th - November 16th. Re:invent (which is AWS major yearly conference) happens at the end of November, and the AWS OpenSearch service needs more time to pick up changes from open source OpenSearch. So the ask is that we would move our release window into early October.
However, even though they're pushing really hard to get in before the conference, and they don't know if they're going to be ready. If they're not ready, then there's no point in us moving the dates.
So here's the the proposal:
October 2nd we'll do a check in to see if there are enough changes to make a release worthwhile.
I'll also ask that the issues/PRs that are being tracked for the release get added here so we have better visibility.
Describe the solution you'd like
N/A
Describe alternatives you've considered
No response
Additional context
No response