-
Notifications
You must be signed in to change notification settings - Fork 30
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
[Action Required] Ensure 2.11 branch readiness for 2.11.1 release #210
Closed
1 of 2 tasks
Tracked by
#4199
Comments
Closed
36 tasks
6 tasks
70 tasks
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Coming from opensearch-project/opensearch-build#4161
What is happening?
We are planning
2.11.1
release in upcoming few weeks. Following the semver guildelines and branching strategy, this release will be based on2.11
as a reference branchWhy?
We need this release because of a critical breaking bug in the security plug-in. This bug impacts everyone using logstash and the only work around is to turn off compression (which is expensive)
As a refresher, our normal process is to commit changes to main, then backport to 2.x. Since the 1.0 release, we only backport bug fixes and security changes to the current 2.x branch (in this case 2.11) so that if we need to we can quickly do a patch release.
There are two reason we don’t back port features to the current release branch (right now 2.11):
However, looking at the list of changes for 2.11, we currently have a mix of features that have been merged in. After providing several options and discussing with all the component teams as well as community we came to the conclusion of reverting all feature related changes from 2.11 branch.
What do I need to do?
Please help revert all the commits that are related to new features or enhancements from 2.11 branch that were added after 2.11.0 release.
Here is a rough list of commits that went in after 2.11.0 release for each repo.
Status
Please check-mark one of the below and close this issue once the action item is completed.
OR
Thank you!
cc: @bbarani @CEHENKLE @Divyaasm
The text was updated successfully, but these errors were encountered: