When are the wild api changes expected to settle down?

[rvowles]

Because we depend on other libraries as well as our own wrapped around open tracing, wild API changes such as have happened from 0.31 -> 0.33 are undesirable. Before making any attempt to upgrade, it would be useful to know when these backwards incompatible API changes will settle down. As such we will stick with 0.31 before investing more time.

[whiskeysierra]

Starting with 1.0, I guess.

[austinlparker]

More seriously, I believe that we expect 0.33 to be somewhat stable as we're building the OpenTracing -> OpenTelemetry adapter against it (see https://medium.com/opentracing/a-roadmap-to-convergence-b074e5815289 for more).

[rvowles]

Thanks Austin - that was really helpful. Willi not so much.

…

On Thu, May 9, 2019 at 3:12 PM Austin Parker ***@***.***> wrote: More seriously, I believe that we expect 0.33 to be somewhat stable as we're building the OpenTracing -> OpenTelemetry adapter against it (see https://medium.com/opentracing/a-roadmap-to-convergence-b074e5815289 for more). — You are receiving this because you authored the thread. Reply to this email directly, view it on GitHub <#349 (comment)>, or mute the thread <https://github.com/notifications/unsubscribe-auth/AAANTWE5MEMT2YK64QL2VOTPUOJAZANCNFSM4HLVVZAQ> .

-- --- Richard Vowles, Full stack - from Kubernetes, through Node & Java, Web and Mobile development in Flutter - software developer for hire! ph: +64275467747, web: www.google.com/+RichardVowles

[whiskeysierra]

Willi not so much.

My statement was a snotty response to the provoking title.

In all seriousness though:

Major version zero (0.y.z) is for initial development. Anything may change at any time. The public API should not be considered stable.

https://semver.org/#spec-item-4

I'm assuming semantic versioning is used based on #114 (comment). A one liner in the readme regarding versioning would be nice.

[austinlparker]

Thanks for the suggestion about making the semver expectations more clear in the readme, @whiskeysierra.

Closing this issue.