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

Consider distinguishing between API and SDK in the spec compliance matrix #1088

Open
arminru opened this issue Oct 13, 2020 · 2 comments
Open
Assignees
Labels
area:miscellaneous For issues that don't match any other area label help wanted Extra attention is needed priority:p2 Medium priority level release:allowed-for-ga Editorial changes that can still be added before GA since they don't require action by SIGs spec:miscellaneous For issues that don't match any other spec label

Comments

@arminru
Copy link
Member

arminru commented Oct 13, 2020

^^^ from the maintainers and spec meeting

https://github.com/open-telemetry/opentelemetry-specification/blob/master/spec-compliance-matrix.md

@arminru arminru added spec:miscellaneous For issues that don't match any other spec label area:miscellaneous For issues that don't match any other area label release:allowed-for-ga Editorial changes that can still be added before GA since they don't require action by SIGs labels Oct 13, 2020
@arminru
Copy link
Member Author

arminru commented Oct 13, 2020

Assigning @bogdandrutu since you mentioned yesterday you'd tidy up the matrix so that maintainer's can double check it and estimate the effort left to reach GA.

@Oberon00
Copy link
Member

Some (all API?) entries may need to be duplicated then. E.g. "allow creating root span": (1) Does the API allow to specify you want to create a root span, and (2) does the SDK properly implement this?

@andrewhsu andrewhsu added the priority:p2 Medium priority level label Oct 16, 2020
@bogdandrutu bogdandrutu added the help wanted Extra attention is needed label Dec 16, 2021
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
area:miscellaneous For issues that don't match any other area label help wanted Extra attention is needed priority:p2 Medium priority level release:allowed-for-ga Editorial changes that can still be added before GA since they don't require action by SIGs spec:miscellaneous For issues that don't match any other spec label
Projects
None yet
Development

No branches or pull requests

4 participants