Closed pavolloffay closed 6 years ago
Also note that io.jaegertracing
will be released with 0.27.0-RC1
(initially) which will be the same version as used here.
No, it's fine to cut a new release with deprecation. My only wish is that the deprecation messages should point to some document that explains why the classes are deprecated and what the migration strategy is. I.e. we could create an issue in this repo and use it as a documentation page.
Release was done, waiting to appear in Central
The new release (with deprecated tracer) should be cut to rather sooner to stop using
com.uber.jaeger
@yurishkuro do you want to wait until you try the wrapper approach?