When is OpenTelemetry.Extensions.Hosting 1.0.1 release date?

[guitarrapc]

Question

What are you trying to achieve?

I want to use OpenTelemetry.Extensions.Hosting but it is still 1.0.0-rc3, therefore could not mix with OpenTelemetry.XXXX 1.0.1 packages.
Any release plan date is appreciated.

[cijothomas]

We don't have an ETA yet. It's received some improvements recently, will allow some time to bake the new features.
Will update when we have an ETA for it.
(Unlike instrumentations, which is dependent on the spec being stable, Ext.hosting has no external dependency. So only blocker is fixing known issues, and giving enough bake time before making stable release) Thanks for your patience.

[cijothomas]

Just realized that we didn't release this package with the new capabilities :D.
Will do a release of it soon. (like an rc4, not stable.)

[guitarrapc]

Sounds very nice, waiting for rc4.

[lukasz-pyrzyk]

@cijothomas do you have any plans for creating a stable release of the non-core components? Is it somehow related to the metrics 1.2.0 release?

[cijothomas]

@cijothomas do you have any plans for creating a stable release of the non-core components? Is it somehow related to the metrics 1.2.0 release?

Stable release of non-core components are blocked on semantic conventions, no ETA.
The extensions.hosting release is not blocked on any spec, but it'll be worked on after metrics feature is done (the focus for 1.2 release is metrics). Sorry, dont have firm ETA on hosting package release.

[lukasz-pyrzyk]

@cijothomas do you have any plans for creating a stable release of the non-core components? Is it somehow related to the metrics 1.2.0 release?

Stable release of non-core components are blocked on semantic conventions, no ETA. The extensions.hosting release is not blocked on any spec, but it'll be worked on after metrics feature is done (the focus for 1.2 release is metrics). Sorry, dont have firm ETA on hosting package release.

what semantic versioning convention is blocking the release of the non-core components?

For me and I guess many other companies, this is having a reference to the non-stable package is a blocker for using OpenTelemetry. It's glad to see that metrics are coming soon and extension.hosting is also going to be shipped in a short time, but still, without Collectors and Exporters we cannot integrate OpenTelemetry, even when we want it very much.

[cijothomas]

what semantic versioning convention is blocking the release of the non-core components?

This blocks all instrumentation libraries -> https://github.com/open-telemetry/opentelemetry-specification/tree/main/specification/trace/semantic_conventions#trace-semantic-conventions

without Collectors and Exporters

I am not sure which Collector are you referring to? If it is the OpenTelemetry collector, then you can check its status/plans here: https://github.com/open-telemetry/opentelemetry-collector

The exporters from this repo are already stable - Zipkin, Jaeger, OTLP, Console, InMemory

[lukasz-pyrzyk]

Sorry, I got the nomenclature wrong. By mentioning Collectors I wanted to say Instrumentation libraries, like Instrumentation.AspNetCore or Instrumentation.Http. It looks like these are the last packages that are not yet stable in any version, what is a blocker for us. Can we expect a stable release sometime soon or do we need to wait for https://github.com/open-telemetry/opentelemetry-specification/tree/main/specification/trace/semantic_conventions#trace-semantic-conventions to become Stable?

[cijothomas]

Sorry, I got the nomenclature wrong. By mentioning Collectors I wanted to say Instrumentation libraries, like Instrumentation.AspNetCore or Instrumentation.Http. It looks like these are the last packages that are not yet stable in any version, what is a blocker for us. Can we expect a stable release sometime soon or do we need to wait for https://github.com/open-telemetry/opentelemetry-specification/tree/main/specification/trace/semantic_conventions#trace-semantic-conventions to become Stable?

They won't be released as stable until semantic conventions get declared stable.