Updates 2.0 release notes with latest commits

[tmarkley]

Description

Adds commits from #1552 and #1545. Any new PRs targeted for 2.0 must add an entry to the release notes.

Issues Resolved

Follow-up on #1566

Check List

• Commits are signed per the DCO using --signoff

[codecov-commenter]

Codecov Report

Merging #1575 (01a86c9) into main (0afba22) will not change coverage.
The diff coverage is n/a.

@@           Coverage Diff           @@
##             main    #1575   +/-   ##
=======================================
  Coverage   68.09%   68.09%           
=======================================
  Files        3072     3072           
  Lines       59033    59033           
  Branches     8928     8928           
=======================================
  Hits        40199    40199           
  Misses      16647    16647           
  Partials     2187     2187           

---

Continue to review full report at Codecov.

Legend - Click here to learn more
Δ = absolute <relative> (impact), ø = not affected, ? = missing data
Powered by Codecov. Last update 0afba22...01a86c9. Read the comment docs.

[joshuarrrr]

For my own learning, how are you identifying which commits are missing or creating a diff? Or, in other words, what sort of tooling or processes are in place to check that the release notes exhaustively include all the commits to the release branch?

[kavilla]

For my own learning, how are you identifying which commits are missing or creating a diff? Or, in other words, what sort of tooling or processes are in place to check that the release notes exhaustively include all the commits to the release branch?

I believe for 2.0 RC1 since it's was constructed manually with verification. The assumption that any new commit that gets backported to 2.0 should include an update to the release notes that wasn't released in the RC1 and planned to be released in 2.0.

It might not even be exhaustive but currently better than waiting until the final days before release and then begin looking at which changes got included.

[tmarkley]

Yeah until we introduce something like release notes drafter it's a manual process.

[joshuarrrr]

So we'd look at something like 2.0.0-rc1...2.0 to find the commits, it sounds like.