Adding release notes for 2.11.0

[harshavamsi]

Signed-off-by: Harsha Vamsi Kalluri [email protected]

Description

Adds release notes for the 2.11 release

Issues Resolved

List any issues this PR will resolve, e.g. Closes [...].

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.

[harshavamsi]

https://github.com/opensearch-project/dashboards-search-relevance/pull/324/files?short_path=2aa4917#diff-2aa4917eeff089adcaab073bcf6bd08e9ad83480ccc31d1488077bf41ed09c10

[codecov]

Codecov Report

Merging #324 (a675daf) into main (acb3dd8) will not change coverage.
Report is 1 commits behind head on main.
The diff coverage is n/a.

@@           Coverage Diff           @@
##             main     #324   +/-   ##
=======================================
  Coverage   87.08%   87.08%           
=======================================
  Files          16       16           
  Lines         209      209           
  Branches       43       43           
=======================================
  Hits          182      182           
  Misses         26       26           
  Partials        1        1           

Flag	Coverage Δ
dashboards-search-relevance	87.08% <ø> (ø)

Flags with carried forward coverage won't be shown. Click here to find out more.

[mingshl]

did these two PRs get into 2.11? if so, we need to add into 2.11 release note

#300
#314

[harshavamsi]

did these two PRs get into 2.11? if so, we need to add into 2.11 release note

#300 #314

I don't think these made it to 2.11, looking at the diff -- 2.10...2.11. Will probably need to update this tag to 2.12

[sejli]

The 2.11 branch was a cut a bit earlier than the first RC. I believe these PRs may have gone in, if the RCs are cut from the 2.x branch. May need to verify with the current RCs.

[mingshl]

the release notes LGTM. One to do item, probably should do before generating the release note, is to label the tickets accordingly based on the category. The git-release-notes should be able to auto generate the notes categorized the tickets based on the labels.

[harshavamsi]

the release notes LGTM. One to do item, probably should do before generating the release note, is to label the tickets accordingly based on the category. The git-release-notes should be able to auto generate the notes categorized the tickets based on the labels.

Makes sense. If we have too many changes, let's tag the PRs.