Add Release Notes for 2.19.0.0

[yizheliu-amazon]

Description

Add Release Notes for 2.19.0.0

Related Issues

Resolves #968

Check List

• New functionality includes testing.
• New functionality has been documented.
• API changes companion pull request created.
• Commits are signed per the DCO using --signoff.
• Public documentation issue/PR created.

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

All modified and coverable lines are covered by tests ✅

Project coverage is 81.62%. Comparing base (cb97cab) to head (954ff1b).
Report is 2 commits behind head on main.

Additional details and impacted files

@@             Coverage Diff              @@
##               main    #1163      +/-   ##
============================================
- Coverage     81.72%   81.62%   -0.10%     
+ Complexity     1247     1246       -1     
============================================
  Files            93       93              
  Lines          4213     4213              
  Branches        714      714              
============================================
- Hits           3443     3439       -4     
- Misses          500      505       +5     
+ Partials        270      269       -1     

☔ View full report in Codecov by Sentry.
📢 Have feedback on the report? Share it here.

[heemin32]

LGTM. Thanks!

[minalsha]

LGTM

[martin-gaievski]

@yizheliu-amazon are you looking to the BWC rolling test failures? Looks like it's failing constantly, I've restarted 3-4 times.

[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-1163-to-2.x
# Cherry-pick the merged commit of this pull request and resolve the conflicts
git cherry-pick -x --mainline 1 e8ed3a406123aeae4a2aab80490ec14c07951665
# Push it to GitHub
git push --set-upstream origin backport/backport-1163-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-1163-to-2.x.

[opensearch-trigger-bot]

The backport to 2.19 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.19 2.19
# Navigate to the new working tree
cd .worktrees/backport-2.19
# Create a new branch
git switch --create backport/backport-1163-to-2.19
# Cherry-pick the merged commit of this pull request and resolve the conflicts
git cherry-pick -x --mainline 1 e8ed3a406123aeae4a2aab80490ec14c07951665
# Push it to GitHub
git push --set-upstream origin backport/backport-1163-to-2.19
# Go back to the original working tree
cd ../..
# Delete the working tree
git worktree remove .worktrees/backport-2.19

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

[yizheliu-amazon]

@yizheliu-amazon are you looking to the BWC rolling test failures? Looks like it's failing constantly, I've restarted 3-4 times.

No. Currently I am looking into integ test issue: #1161