-
Notifications
You must be signed in to change notification settings - Fork 773
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Release changes for unstable core components #5530
Comments
I like overall concept. The semantic convention should be reconsidered and released separately from core packages. It should be strictly related to sen conv. releases. As I remember @lmolkova was working on tool sem conv. generation which should make this package more usable. |
Hi, sorry for commenting on closed issue but what is the reason for not releasing stable packages? Is it still waiting for the OpenTelemetry specification? We were considering using |
@klinki |
The following components are considered part of core (defined by the spec) but have not been released stable:
OpenTelemetry.Exporter.Prometheus.AspNetCore
OpenTelemetry.Exporter.Prometheus.HttpListener
OpenTelemetry.SemanticConventions
OpenTelemetry.Shims.OpenTracing
As discussed on the SIG meeting 4/9/2024, we're going to change how these packages are released to make things more consistent and have a defined process for packages which previously had no official process.
We will only release
alpha
&beta
versions of these packages. We have in the past releasedrc
packages of the Prometheus projects but it was decided it doesn't make sense to have a "release candidate" for something we have no intention of releasing.These packages will now depend only on the stable versions of the core packages (API, SDK, etc.). Today they always depend on prerelease versions.
OpenTelemetry.Exporter.Prometheus.AspNetCore
,OpenTelemetry.Exporter.Prometheus.HttpListener
, &OpenTelemetry.Shims.OpenTracing
will be released at a minimum once after a stable release of core packages.OpenTelemetry.SemanticConventions
is rarely changed and has no dependencies so it will only be released after a stable release of core packages if changes were actually made.The text was updated successfully, but these errors were encountered: