We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
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
@alolita has volunteered to be the sponsor for this.
The text was updated successfully, but these errors were encountered:
@open-telemetry/governance-committee , @open-telemetry/technical-committee:
how much does this involve to also have all three of them documented on opentelemetry.io?
We have a meta issue open to standardize those docs across all languages1:
open-telemetry/opentelemetry.io#3229
I think it would be great to think of "stable" as also having proper end-user-facing documentation.
(cc @open-telemetry/docs-approvers)
as far as possible, of course we will anticipate that each language may have there specific wording/details, etc. ↩
Sorry, something went wrong.
I would say this must involve documentation as well. It shouldn't count as stable until there's docs explaining how to use the APIs.
alolita
No branches or pull requests
@alolita has volunteered to be the sponsor for this.
The text was updated successfully, but these errors were encountered: