Skip to content

Milestones

List view

  • Stable Release of Context, Baggage Stable Release of Metrics SDK Resolution to Tokio Tracing vs OTel Tracing API for Distributed Tracing.

    Due by May 30, 2025
    8/8 issues closed
  • 0.29 will focus on bringing improvements to Tracing signal (which has fallen behind logs/metrics), and also resolve the Otel Tracing vs Tokio-Tracing issue. Additionally, this is also expected to improve Stability guarantees for opentelemetry_sdk logs, and metrics to be stable. Update on. Mar 11: 0.29 will focus on Context, Baggage, and making them RC Also, appeder-tracing, logging-sdk to be marked Stable.

    Due by March 21, 2025
    12/12 issues closed
  • Move Metrics SDK and Logs SDK to RC status, Metrics API to Stable.

    Due by February 7, 2025
    27/27 issues closed
  • Due by November 29, 2024
    6/6 issues closed
  • - *Metrics API*: Move to *Release Candidate (RC)* - *Metrics SDK*: Move to *Beta* - *Log Appender (Tracing)*: Move to *RC* - *Log Bridge API*: Move to *RC* - *Bug Fixes & Enhancements*: Focus on addressing shutdown/export issues (postponed from 0.26), further enhancing internal logging, and optimizing the metrics export/collection paths for better performance and code reuse.

    Due by November 8, 2024
    10/10 issues closed
  • Milestone to track Metric API+SDK+OTLPExporter reaching RC status.

    Due by November 30, 2024
  • Covers beta release of Logging Bridge API, SDK, OTLP Exporter, Appender-Tracing

    Due by June 30, 2024
    4/4 issues closed
  • Milestone to track Metric API+SDK+OTLPExporter reaching beta status.

    Due by September 30, 2024
    8/8 issues closed
  • This milestone tracks the stable release of https://github.com/open-telemetry/opentelemetry-rust/tree/main/opentelemetry-appender-tracing

    Due by June 30, 2025
    3/3 issues closed
  • Blockers for the next release

    Due by May 22, 2024
    1/1 issues closed
  • Due by January 31, 2025
    3/3 issues closed
  • Definition according to Opentelemetry: https://opentelemetry.io/docs/reference/specification/versioning-and-stability/#stable Any tickets which would lead toward this goal can and should be added. 1.0 is delayed to June 2025 to declare 1.0 together for all signals.

    Due by June 30, 2025
    12/12 issues closed
  • Definition according to Opentelemetry: https://opentelemetry.io/docs/reference/specification/versioning-and-stability/#stable Any tickets which would lead toward this goal can and should be added.

    Due by December 31, 2024
  • Definition according to Opentelemetry: https://opentelemetry.io/docs/reference/specification/versioning-and-stability/#stable Any tickets which would lead toward this goal can and should be added. 1.0 is delayed to June 2025 to declare 1.0 together for all signals.

    Due by June 30, 2025
    15/15 issues closed