open-telemetry
Mark declarative config as stable
Resolves #4374.
We recently cut a release candidate for opentelemetry-configuration. After some additional bake-in time and review, we'd like to cut a stable release.
The stable release needs to coincide with marking key parts of the specification stable, so I'm opening this PR to solicit feedback such that when the time comes, we can mark the specification and opentelemetry-configuration stable is quick succession.
See https://github.com/open-telemetry/opentelemetry-configuration/issues/100 for status of implementations.
cc @open-telemetry/configuration-maintainers
This is ready for review, but SHOULD not be merged. Assuming we get the required approvals, I'll coordinate merging this with cutting the corresponding release of opentelemetry-configuration.
This PR was marked stale due to lack of activity. It will be closed in 7 days.
![github-actions[bot] avatar](https://avatars.githubusercontent.com/in/15368?v=4 "Published by a pub.dev verified publisher"){kind=small}
This PR was marked stale due to lack of activity. It will be closed in 7 days.
This PR was marked stale due to lack of activity. It will be closed in 7 days.
This PR was marked stale due to lack of activity. It will be closed in 7 days.
This PR was marked stale due to lack of activity. It will be closed in 7 days.
A concern I have is that this sort of implies that a spec for the behavior of AutoConfiguredOpenTelemetrySdk.initialize().getOpenTelemetrySdk(); is stable, which I think requires that https://github.com/open-telemetry/opentelemetry-specification/issues/4591 be done.
Can the spec of config be stable before SDK initialization is defined?
This PR was marked stale due to lack of activity. It will be closed in 7 days.
This PR was marked stale due to lack of activity. It will be closed in 7 days.
This PR was marked stale due to lack of activity. It will be closed in 7 days.
This PR was marked stale due to lack of activity. It will be closed in 7 days.
This PR was marked stale due to lack of activity. It will be closed in 7 days.
Closed as inactive. Feel free to reopen if this PR is still being worked on.
Re opened.
@jack-berg
Please look at the merge conflict on the spec compliance matrix, due to recent changes to yaml.
This PR was marked stale due to lack of activity. It will be closed in 7 days.
This PR was marked stale due to lack of activity. It will be closed in 7 days.
This PR was marked stale due to lack of activity. It will be closed in 7 days.
This PR was marked stale due to lack of activity. It will be closed in 7 days.
This PR was marked stale due to lack of activity. It will be closed in 7 days.
The config SIG has been making a lot of progress around the goal of stability and will be looking to stabilize end of 2025 / early 2026. Converting this to a draft until we're ready.
This PR was marked stale due to lack of activity. It will be closed in 7 days.