Add 2.11 release note

[heemin32]

Description

Add 2.11 release note

Issues Resolved

#317

Check List

• New functionality includes testing.
  • All tests pass
• New functionality has been documented.
  • New functionality has javadoc added
• Commits are signed as per the DCO using --signoff

By submitting this pull request, I confirm that my contribution is made under the terms of the Apache 2.0 license.
For more information on following Developer Certificate of Origin and signing off your commits, please check here.

[codecov]

Codecov Report

Merging #392 (cfbb6a6) into main (8e98167) will not change coverage.
The diff coverage is n/a.

@@            Coverage Diff            @@
##               main     #392   +/-   ##
=========================================
  Coverage     84.56%   84.56%           
  Complexity      449      449           
=========================================
  Files            38       38           
  Lines          1348     1348           
  Branches        201      201           
=========================================
  Hits           1140     1140           
  Misses          120      120           
  Partials         88       88           

[navneet1v]

why multi model feature is not added in release notes?

[navneet1v]

@martin-gaievski

[heemin32]

it went directly to 2.x branch. I might need to update release note during backport.

[martin-gaievski]

We may need to add #396 for 2.11 release, hope it can be finalized today

[martin-gaievski]

We may need to add #396 for 2.11 release, hope it can be finalized today

We have merged that to 2.11 #400, please update notes by including change from that PR @heemin32

[opensearch-trigger-bot]

The backport to 2.x failed:

The process '/usr/bin/git' failed with exit code 1

To backport manually, run these commands in your terminal:

# Fetch latest updates from GitHub
git fetch
# Create a new working tree
git worktree add .worktrees/backport-2.x 2.x
# Navigate to the new working tree
cd .worktrees/backport-2.x
# Create a new branch
git switch --create backport/backport-392-to-2.x
# Cherry-pick the merged commit of this pull request and resolve the conflicts
git cherry-pick -x --mainline 1 0f73cc69d033b84f193405045eb2e0d57dcea69b
# Push it to GitHub
git push --set-upstream origin backport/backport-392-to-2.x
# Go back to the original working tree
cd ../..
# Delete the working tree
git worktree remove .worktrees/backport-2.x

Then, create a pull request where the base branch is 2.x and the compare/head branch is backport/backport-392-to-2.x.

[opensearch-trigger-bot]

The backport to 2.11 failed:

The process '/usr/bin/git' failed with exit code 1

To backport manually, run these commands in your terminal:

# Fetch latest updates from GitHub
git fetch
# Create a new working tree
git worktree add .worktrees/backport-2.11 2.11
# Navigate to the new working tree
cd .worktrees/backport-2.11
# Create a new branch
git switch --create backport/backport-392-to-2.11
# Cherry-pick the merged commit of this pull request and resolve the conflicts
git cherry-pick -x --mainline 1 0f73cc69d033b84f193405045eb2e0d57dcea69b
# Push it to GitHub
git push --set-upstream origin backport/backport-392-to-2.11
# Go back to the original working tree
cd ../..
# Delete the working tree
git worktree remove .worktrees/backport-2.11

Then, create a pull request where the base branch is 2.11 and the compare/head branch is backport/backport-392-to-2.11.