Declare freeze of Trace API Specification 1.0#1121
Declare freeze of Trace API Specification 1.0#1121carlosalberto merged 9 commits intoopen-telemetry:masterfrom
Conversation
|
Please make sure to keep this in ready-for-review state a long enough time and not merge it straight out of draft state. |
|
This PR was marked stale due to lack of activity. It will be closed in 7 days. |
76def07 to
ce81306
Compare
|
This is ready for review, but don't merge. |
There was a problem hiding this comment.
The set of documents frozen does not include resources and common. I think at least common/ needs to be frozen before trace. resources/ also needs to be frozen before tracing goes GA.
EDIT: Semantic conventions are also not included which seems fine. Although maybe exception semantic conventions should be frozen, since we have record_exception referencing it from the trace API spec.
bogdandrutu
left a comment
There was a problem hiding this comment.
Overall LGTM, but need to make sure we close all PRs before merging this.
0ca12f4 to
3de0b2a
Compare
|
Discussed in the Maintainers meeting. For now this PR includes only Trace API, but not Trace SDK. We would like to get this merged today or tomorrow. Please review. |
There was a problem hiding this comment.
I think we need to also freeze the attributes sections of common/common.md: https://github.com/open-telemetry/opentelemetry-specification/blob/master/specification/common/common.md#attributes and for that I'd like to see #1203 resolved. EDIT: And #1213.
There was a problem hiding this comment.
Please also freeze the common as @Oberon00 suggested
201a6a8 to
7dac4a4
Compare
|
|
We want to freeze Trace specification 1.0 so that we no longer accept substantial changes (unless a fundamental problem is found in the spec). Resolves open-telemetry#1120
Co-authored-by: Armin Ruech <armin.ruech@dynatrace.com>
7dac4a4 to
4315893
Compare
Co-authored-by: Armin Ruech <armin.ruech@dynatrace.com>
|
I think this is good to merge. |
|
We got enough approvals and the last two pending issues we had were solved. Merging now! |
* Declare freeze of Trace Specification 1.0 We want to freeze Trace specification 1.0 so that we no longer accept substantial changes (unless a fundamental problem is found in the spec). Resolves open-telemetry#1120
* Declare freeze of Trace Specification 1.0 We want to freeze Trace specification 1.0 so that we no longer accept substantial changes (unless a fundamental problem is found in the spec). Resolves open-telemetry#1120
* Declare freeze of Trace Specification 1.0 We want to freeze Trace specification 1.0 so that we no longer accept substantial changes (unless a fundamental problem is found in the spec). Resolves open-telemetry#1120
Co-authored-by: Liudmila Molkova <limolkova@microsoft.com>
We want to freeze Trace API specification 1.0 so that we no longer accept substantial changes (unless a fundamental problem is found in the spec).
Contributes to #1120