API break from 0.22 to 0.30 about opentracing-java

[bhs]

@objectiser ACK, yes. What are the criteria for closing this issue?

[martinjmares]

Hi,
OK. I can accept incompatible differences between 0.22 and 0.30 but I also need some version or promise which I can include into my Java libraries without a risk of incompatible dependencies for users of my library. Something like 1.0 release with compatibility promise for all future versions. Do you plan something like that? If yes, when? If not, what is your expectation - how to use it in libraries?
BTW: Thank you for your library. I like it.

[pavolloffay]

Hi @martinjmares, yes are we planning 1.0 soon, however we don't know the exact date. Here https://github.com/opentracing/opentracing-java/milestone/1 are missing issues to be resolved.

[objectiser]

@bhs issue can be closed. Was mainly to highlight the incompability.

[bhs]

@objectiser makes sense, will close.

@martinjmares I'd echo what @pavolloffay said. The additional API work for 1.0 is small... my main source of concern/delay is just seeing the ActiveSpan stuff "in the wild" for longer.