List view
- Due by December 1, 2021•4/4 issues closed
Release manager: @albertteoh
Due by November 3, 2021Release manager: @joe-elliott
Due by October 6, 2021•27/27 issues closedRelease manager: @yurishkuro
Due by September 6, 2021•6/6 issues closed- Due by August 4, 2021•21/21 issues closed
Release manager: @pavolloffay
Due by July 7, 2021•21/21 issues closed- No due date•119/119 issues closed
- No due date•2/2 issues closed
Tracker for release 2.0
No due date•8/8 issues closed- No due date•1/1 issues closed
Tracker for release 1.21.0
No due date•2/2 issues closedThis milestone is being used to track when the OpenTelemetry Collector, with custom Jaeger specific components, is at a suitable level of functionality to be considered as a replacement for the Jaeger Collector.
No due date•16/16 issues closed- Due by May 1, 2020
- Due by April 5, 2020•6/6 issues closed
- Due by January 26, 2020•4/4 issues closed
- Due by December 17, 2019•29/29 issues closed
- Due by November 7, 2019•15/15 issues closed
Support for Kafka ingestion.
Due by September 11, 2018•9/9 issues closed* Support gRPC/protobuf endpoints for core backend communications * Collector service (receiving spans) * Query service * Configuration services in the collector (sampling, throttling, baggage restrictions) * All agent to collector communications using gRPC * Spans forwarding * Configuration services * Lock down protobuf-based API 2.x
Due by September 1, 2018•2/2 issues closedhttps://bestpractices.coreinfrastructure.org/ This is a requirement of CNCF graduation (down the road). This isn't a super high priority.
Due by November 1, 2018•5/5 issues closedFeatures for Jaeger backend to be a drop-in replacement for Zipkin backend
No due date•15/15 issues closed