Path to Stable Release: Roadmap about opentelemetry-rust HOT 4 OPEN

One very minor naming point

Would it make sense to also include opentelemetry-http as part of the tracing scope? Or part of it, namely opentelemetry_http::HeaderExtractor but from what I've seen everything there is just scaffolding for propagation.

Personally, I think this is important to achieve correct and stable context propagation across processes. Or is the vision that only opentelemetry_sdk::propagation::TraceContextPropagator and opentelemetry::propagation::Extractor would be stabilized and the concrete implementations wouldn't yet?

from opentelemetry-rust.

I also just realized, opentelemetry-http probably should not be stabilized until it is moved to [email protected]. There's already #1674 so I won't go into more detail here, but upgrading it later would be a breaking change.

from opentelemetry-rust.

As discussed in the community meeting today, above post contains the rough plans. We are still editing it, and once done, will create separate milestones for each release along with planned release date for each of them.

from opentelemetry-rust.

Thanks for the feedback. Yes, opentelemetry-http (at the minimum the propagation part) is critical for OTel Tracing stable.

(I'll enquire more about the _ vs - for sdk crate, to see if we can do something to fix.)

from opentelemetry-rust.