Beta readiness tracker

[MikeGoldsmith]

This is a tracking issue for the requirements outlined in the beta release document: https://docs.google.com/document/d/1eviggoIguOS89dgKL-8ntUOCfPP6FLWAoQkGoBDsld0/edit#

Traces

• Stable API of every spec'd feature
• SDK Implementation of every spec'd feature
• Basic tracing
• Named tracers
• Tracers use OTEP 66 Context mechanism - This is an implementation detail and does not affect the API

Metrics

• Documentation
• Examples
• Stable API of every spec'd feature
• SDK Implementation of every spec'd feature
• Basic SDK
• Add observer Combined Metrics API updates for v0.3 (Add Observer instrument, remove Gauge instrument, etc.) opentelemetry-specification#430
• Remove gauge Combined Metrics API updates for v0.3 (Add Observer instrument, remove Gauge instrument, etc.) opentelemetry-specification#430
• Push controller
• Pull controller

Resources

• Stable API of every spec'd feature Update semantic conventions to v1.10.0 #789
• SDK Implementation of every spec'd feature

Context Propagation

• Stable API of every spec'd feature Remove StatusCode::as_str #741
• Basic context mechanism Update sdk trace docs #769
• Global Propagators API Remove unnecessary string allocations from examples #777 feat(trace): jaeger remote sampler #797
• Global Context API (get and set active context) feat(datadog): add sampling priority tag in datadog spans #792
• SDK Implementation of every spec'd feature
• Basic context mechanism Update sdk trace docs #769
• Global Propagators Remove unnecessary string allocations from examples #777

Exporters

• OpenTelemetry Native - Collector Exporter
• gRPC support
• Prometheus
• Jaeger
• Zipkin

Integrations

• HTTP
• gRPC
• SQL

Examples

• Manual tracing hello world example
• HTTP client/server using an instrumented framework
• gRPC client/server

[jtescher]

Closing this as we're moving towards GA spec 👍