Prepare v0.23 release

[cijothomas]

Preparing the next release.
No change in overall status and breaking changes are still expected in next release.

The next release, which is planned for June 30 2024, is expected to update status of Logs, Metrics to Beta.

Opening as draft to discuss the below in next Community meeting on Tuesday May 14th 9 AM PT.
Blockers to discuss:

• 1. Revisit shutdown_signal_provider methods at API level #1679 - Resolved
• 2. In-flight or upcoming PRs that must be part of this release. - Reviewed during Community call 5/14. Nothing needs to catch this release.
• 3. Blocked by this : OTLP Examples fixed to be consistent #1752 (comment) - Unblocked via Add http-json warning to OTLP Exporter #1765

[codecov]

Codecov Report

All modified and coverable lines are covered by tests ✅

Project coverage is 71.6%. Comparing base (348ec9e) to head (9139894).
Report is 39 commits behind head on main.

❗ Current head 9139894 differs from pull request most recent head d88d7ed. Consider uploading reports for the commit d88d7ed to get more accurate results

Additional details and impacted files

@@           Coverage Diff           @@
##            main   #1738     +/-   ##
=======================================
+ Coverage   71.0%   71.6%   +0.6%     
=======================================
  Files        135     136      +1     
  Lines      20751   20857    +106     
=======================================
+ Hits       14746   14951    +205     
+ Misses      6005    5906     -99     

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

[cijothomas]

Blocked by this : #1752 (comment)

[cijothomas]

Blocked by this : #1752 (comment)

Not really blocked. Http/protobuf is working, Http/json is not. Http/json is a new capability, and we may hide it to unblock this release.

#1755 also has some cleanups, that could be bundled into this release, but don't feel strongly about waiting for that, as they are all existing issues, and this release is still keeping alpha status only.

[TommyCpp]

The next release, which is planned for June 30 2024, is expected to update status of #1733, #1719 to Beta.

Huh I thought the next release will be end of June and bring everything to Beta?

[cijothomas]

The next release, which is planned for June 30 2024, is expected to update status of #1733, #1719 to Beta.

Huh I thought the next release will be end of June and bring everything to Beta?

It's been over three months since our last release, and we've accumulated significant updates, including major changes to logs and resolutions for shutdown issues. I suggest we proceed with this release now to start gathering feedback earlier. This will better position us for the beta release planned for the end of June.

While I recognize that releases with breaking changes will upset a lot of users, timely releases and gathering early feedback is crucial for progressing towards a beta, release candidate, and then stable version within a reasonable timeframe.