[Process] TC Review of 1.0 Trace

[jsuereth]

This tracks the status of the TC review for 1.0 Trace release of OpenTelemetry C++

Status

• Review Compliance Matrix
  • Traces
  • Baggage
  • Resource
  • Context Propagation
  • Environment Variables
  • Exporters
• Review Versioning and Stability policy enforcement
  • API
  • SDK
• Ensure Consistent names across implementation
• Avoid confusions across implementation (e.g. same public API has different behaviors)
• Ensure no experimental features (signals) are part of the released packages (e.g. api, sdk, etc.).

Open TODOs / Cleanups

• Clearly denote Build Tool support in doocumentation. #947
• DefaultTracer in API headers should be marked internal / not-for-public use or documented #949
• Helper methods for accessing Span directly from Context in Span API #950
• Span Parent should be determined from Context (and take this as a parameter. #955
• Should to_span_ptr be public? (Fixed: Remove unused public API to_span_ptr #964)
• Document DefaultSpan #956
• Error message must be ignored when status code is ok on Span->SetStatus #957
• Baggage <-> Context interaction on Baggage as static methods? #961
• Semantic conventions are not considered stable and need to be clearly marked as such #968
• OTLP Environment variables do not match specification #971
• detail namespace should be kept compatible or denoted as internal-only usage #972

Optional Cleanup TODOs

• Add schema_url to TracerProvider.get #948
• Baggage API naming deviations
  • Delete vs. RemoveKey
  • GetAllEntries vs. GetAllValues
  • Set vs. SetValue

See open-telemetry/opentelemetry-specification#1418 for process details.

[jsuereth]

Congratulations on the pending 1.0!