This repository has been archived by the owner on May 23, 2023. It is now read-only.
-
Notifications
You must be signed in to change notification settings - Fork 344
When are the wild api changes expected to settle down? #349
Comments
Starting with 1.0, I guess. |
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). |
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
|
My statement was a snotty response to the provoking title. In all seriousness though:
I'm assuming semantic versioning is used based on #114 (comment). A one liner in the readme regarding versioning would be nice. |
Thanks for the suggestion about making the semver expectations more clear in the readme, @whiskeysierra. Closing this issue. |
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
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.
The text was updated successfully, but these errors were encountered: