[META] Ensure 2.11 branch readiness for 2.11.1 release

[gaiksaya]

Coming from #4161 this issue tracks all child issues for ensuring branch readiness for 2.11.1 release.

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 on 2.11 as a reference branch

Why?

1. 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)

2. 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.

3. There are two reason we don’t back port features to the current release branch (right now 2.11):

   1. Because we want patch release to be as thin as possible, and the more changes you make, the more verification we need to do
   2. Adding features in a patch breaks semver.

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.

• [Action Required] Ensure 2.11 branch readiness for 2.11.1 release alerting#1297
• [Action Required] Ensure 2.11 branch readiness for 2.11.1 release anomaly-detection#1097
• [Action Required] Ensure 2.11 branch readiness for 2.11.1 release asynchronous-search#509
• [Action Required] Ensure 2.11 branch readiness for 2.11.1 release common-utils#559
• [Action Required] Ensure 2.11 branch readiness for 2.11.1 release reporting#926
• [Action Required] Ensure 2.11 branch readiness for 2.11.1 release index-management#1032
• [Action Required] Ensure 2.11 branch readiness for 2.11.1 release job-scheduler#538
• [Action Required] Ensure 2.11 branch readiness for 2.11.1 release k-NN#1294
• [Action Required] Ensure 2.11 branch readiness for 2.11.1 release performance-analyzer#592
• [Action Required] Ensure 2.11 branch readiness for 2.11.1 release performance-analyzer-rca#516
• [Action Required] Ensure 2.11 branch readiness for 2.11.1 release security#3650
• [Action Required] Ensure 2.11 branch readiness for 2.11.1 release sql#2417
• [Action Required] Ensure 2.11 branch readiness for 2.11.1 release observability#1765
• [Action Required] Ensure 2.11 branch readiness for 2.11.1 release cross-cluster-replication#1283
• [Action Required] Ensure 2.11 branch readiness for 2.11.1 release ml-commons#1592
• [Action Required] Ensure 2.11 branch readiness for 2.11.1 release geospatial#582
• [Action Required] Ensure 2.11 branch readiness for 2.11.1 release notifications#812
• [Action Required] Ensure 2.11 branch readiness for 2.11.1 release neural-search#486
• [Action Required] Ensure 2.11 branch readiness for 2.11.1 release security-analytics#714
• [Action Required] Ensure 2.11 branch readiness for 2.11.1 release custom-codecs#80
• [Action Required] Ensure 2.11 branch readiness for 2.11.1 release dashboards-query-workbench#210
• [Action Required] Ensure 2.11 branch readiness for 2.11.1 release alerting-dashboards-plugin#792
• [Action Required] Ensure 2.11 branch readiness for 2.11.1 release notifications#813
• [Action Required] Ensure 2.11 branch readiness for 2.11.1 release security-dashboards-plugin#1643
• [Action Required] Ensure 2.11 branch readiness for 2.11.1 release index-management-dashboards-plugin#914
• [Action Required] Ensure 2.11 branch readiness for 2.11.1 release anomaly-detection-dashboards-plugin#646
• [Action Required] Ensure 2.11 branch readiness for 2.11.1 release reporting#927
• [Action Required] Ensure 2.11 branch readiness for 2.11.1 release dashboards-reporting#253
• [Action Required] Ensure 2.11 branch readiness for 2.11.1 release dashboards-observability#1230
• [Action Required] Ensure 2.11 branch readiness for 2.11.1 release dashboards-visualizations#289
• [Action Required] Ensure 2.11 branch readiness for 2.11.1 release dashboards-search-relevance#348
• [Action Required] Ensure 2.11 branch readiness for 2.11.1 release dashboards-maps#559
• [Action Required] Ensure 2.11 branch readiness for 2.11.1 release security-analytics-dashboards-plugin#779
• [Action Required] Ensure 2.11 branch readiness for 2.11.1 release ml-commons-dashboards#283
• [Action Required] Ensure 2.11 branch readiness for 2.11.1 release OpenSearch#11094
• [Action Required] Ensure 2.11 branch readiness for 2.11.1 release OpenSearch-Dashboards#5431

[Swiddis]

Looks like observability got two issues (1765 and 1766), I assume one of those is meant for dashboards-observability

[gaiksaya]

Looks like observability got two issues (1765 and 1766), I assume one of those is meant for dashboards-observability

Looks like it. I used the meta tool here to create issues. Maybe check if there is some issue with re-direct of GitHub repo naming there? I'll move one of the issue to dashboards-observability.
Thanks!

[mengweieric]

Sql also has duplicated issues 2147 and 2148, plus we are missing query workbench and dashboard reports.

[gaiksaya]

Sql also has duplicated issues 2147 and 2148, plus we are missing query workbench and dashboard reports.

You can move the issues from sql to those repos. Taking care of it of it for now.

[gaiksaya]

Closing this issue as all related action item sub-issues are now addressed.
Thanks!