release(v0.19): add initial change log

[TommyCpp]

We are still blocked by some memory issue investigation but once it resolved we should be able to cut a release

[codecov]

Codecov Report

Patch and project coverage have no change.

Comparison is base (8cc3ee3) 69.9% compared to head (023b8b8) 69.9%.

Additional details and impacted files

@@          Coverage Diff          @@
##            main    #965   +/-   ##
=====================================
  Coverage   69.9%   69.9%           
=====================================
  Files        116     116           
  Lines       9027    9027           
=====================================
+ Hits        6310    6315    +5     
+ Misses      2717    2712    -5     

see 2 files with indirect coverage changes

Help us with your feedback. Take ten seconds to tell us how you rate us. Have a feature suggestion? Share it here.

☔ View full report in Codecov by Sentry.
📢 Do you have feedback about the report comment? Let us know in this issue.

[djc]

I think we should deal with #969 before releasing.

Is it intentional that the integration tests job is getting skipped in CI? Should we run it manually before release?

[TommyCpp]

Is it intentional that the integration tests job is getting skipped in CI?

Yeah I intend to expand the integration test coverage so I expect the time to run it grows over time. And it may not needed to run for every commit/PR. But we should run it before release.

[TommyCpp]

Listed the following issues as blocking before 0.19 release, feel free to add more:

• Tonic Interceptor #901 Need review

[hdost]

@TommyCpp Is the blocker still the memory issue?

[TommyCpp]

@TommyCpp Is the blocker still the memory issue?

No the memory issue is false alarm for this repo(the issue is not in our crate) so we are good on that front. I can update the changelog but we probably still need #901 to sign LCA?

[hdost]

Should we place a time limit on the #901 change, if it's not merged by X date then we merge and release?

[TommyCpp]

Should we place a time limit on the #901 change, if it's not merged by X date then we merge and release?

Plan to cut release this weekend. We can do a minor release for #901 if needed

[TommyCpp]

I think that's all changes we want to land in v0.19. PTAL cc @open-telemetry/rust-approvers

[jtescher]

@TommyCpp should we release version 0.20.0 as a follow up once #1000 lands?

[TommyCpp]

@TommyCpp should we release version 0.20.0 as a follow up once #1000 lands?

Yep I think #1000 contains lots of change and maybe released as follow up.

I will wait until tomorrow to gather more thoughts for this release. But if there is not I will merge it.

[glynnmccabe]

@TommyCpp the datadog export is broken for version 05. I made a small fix here: #1002

Tested locally and working as expected.

Would be nice to get this in the release if possible :)

[hdost]

🚀 thank you @TommyCpp