List view
First Release Candidate. This will require the RC1 from the OpenTelemetry. Until then the Due date is a guess.
Due by November 17, 2020- Due by June 8, 2020•10/10 issues closed
A milestone to aggregate technical debt, for when the project slows down a bit and we can focus on polish.
No due date•2/2 issues closed- Due by May 26, 2020
Meta-work required to release automatically on a regular cadence.
No due date•2/2 issues closed- No due date•4/4 issues closed
- No due date•1/1 issues closed
First public beta release of OT clients. This release should include a stable API for metrics and tracing, a complete SDK, and comprehensive examples.
Due by March 31, 2020•6/6 issues closed- Due by March 16, 2020•18/18 issues closed
Stable version to prepare for RC. Should include examples and integration tests to prove compliance with the spec. See the [specs v0.4 milestone](https://github.com/open-telemetry/opentelemetry-specification/milestone/9).
Due by January 28, 2020•10/10 issues closedAPI package is stable and follows v0.3 spec, interfaces in SDK package are relatively stable and internal data formats are not expected to change significantly after this release. See also the [specs v0.3 milestone](https://github.com/open-telemetry/opentelemetry-specification/milestone/8).
Due by December 6, 2019•11/11 issues closedTracing and metrics SDK and exporters complete, including working Jaeger and Prometheus exporters. At this point it should be possible to demo the end-to-end behavior of the client, although the API is still subject to change. See also the [specs v0.2 milestone](https://github.com/open-telemetry/opentelemetry-specification/milestone/7).
Due by October 28, 2019•10/10 issues closed- Due by October 14, 2019
See <https://docs.google.com/spreadsheets/d/1FHt3uJgQWN-UWbgV4uMIPUr36JiJCfZ7ryQbHfurjKA/edit>. We need a demoable version of * Tracing * Metrics * Context in-so-far as needed for the above and optionally * OpenTelemetry bridge
Due by September 30, 2019•13/13 issues closedDecide on a set of integrations to implement for the first release, focusing on an end-to-end story. 1. Django/Flask 2. requests/httplib 3. threading Decide on a set of tracing and metrics exporters to include in a first release of the library. Implement and test.
No due dateInitial release of the opentelemetry-sdk metrics package. The package should provide a complete implementation of the API.
No due dateInitial release of the opentelemetry-api metrics package. The package should conform to the spec, and be well tested and documented.
No due dateInitial release of the `opentelemetry-sdk` tracing package. The package should provide a complete implementation of the API.
No due date•1/1 issues closedInitial release of the `opentelemetry-api` tracing package. The package should conform to the spec, and be well tested and documented.
Due by July 31, 2019•10/10 issues closed