Add 2.0.0-rc1 release notes

[Poojita-Raj]

Signed-off-by: Poojita Raj poojiraj@amazon.com

Description

Adding release notes for the 2.0 release. There was no common branch point to start the release notes from - so it started from commit f14e0a3 - the commit after #2489. Dependabot PRs have been removed for the sake of brevity.

Issues Resolved

[List any issues this PR will resolve]

Check List

• New functionality includes testing.
  • All tests pass
• New functionality has been documented.
  • New functionality has javadoc added
• Commits are signed 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.

[opensearch-ci-bot]

❌   Gradle Check failure c9f75a51d2d763ebc85cb3ab1ffe59dfc06cb88d
Log 4721

Reports 4721

[nknize]

Rebase from main to ensure passing tests.

[dblock]

These notes need to be humanly readable. This isn't really. So I am afraid we need to hand-edit this entire file.

@elfisher @bbarani can agree/disagree

[dblock]

Check out what opensearch-project/job-scheduler#172 looks like, I think I expected something like that here.

[opensearch-ci-bot]

❌   Gradle Check failure cde52c43fecdb51d258ad0b04b469f866b15a09e
Log 4741

Reports 4741

[dblock]

I would just keep the titles and make the GitHub issues clickable. Like in https://github.com/opensearch-project/job-scheduler/pull/172/files.

[dblock]

Much better! Do you think it's worth doing a pass on aligning language/standardizing things like [Remove] Xyz ..., capitalizing consistently, etc.?

[Poojita-Raj]

Much better! Do you think it's worth doing a pass on aligning language/standardizing things like [Remove] Xyz ..., capitalizing consistently, etc.?

I don't think it's worth it since a lot of the titles would require a manual rewrite to ensure they're in the same format - not all of them start with action verbs or tags. But going forward definitely we should ensure all PRs have a check to ensure they're in the right format - referencing the discussion in #1868.

[opensearch-ci-bot]

✅   Gradle Check success d8f1e62
Log 4814

Reports 4814

Changes requested have been addressed.

[kartg]

Kudos for combing through all of the commits and crafting this!

Need to be merged in for release by eod