Skip to content
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

Stable (non-alpha) releases #6

Open
arminru opened this issue Dec 22, 2021 · 2 comments
Open

Stable (non-alpha) releases #6

arminru opened this issue Dec 22, 2021 · 2 comments

Comments

@arminru
Copy link
Member

arminru commented Dec 22, 2021

The proto definitions for metrics and traces (including common and resources) are already defined as stable (see opentelemetry-proto#maturity-level). The Java packages published from this repo here are still marked as -alpha, however, and as such also used in the stable opentelemetry-java SDK.
When will stable releases of opentelemetry-proto-java be available? What's still missing to consider it stable?
Thanks!

@anuraaga
Copy link
Contributor

I don't think we want to go through the complexity of publishing two artifacts for stable and alpha, unless a user really asked for this. We would want all the protos to be marked Stable then, to release our artifact of all the signals to be stable. That means logs/* being marked Stable, and trace_config.proto being deleted (though we can workaround the latter here as we don't use it in the SDK, but someone really needs to get to deleting that :P)

@anuraaga
Copy link
Contributor

anuraaga commented Dec 23, 2021

and as such also used in the stable opentelemetry-java SDK.

Ah by the way, we don't use the protos in the SDK itself, we only use them in tests. The SDK has its own marshaling logic that doesn't use the code published from here.

open-telemetry/opentelemetry-specification#1996

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants