-
Notifications
You must be signed in to change notification settings - Fork 897
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Loosen requirement for a major version bump #2510
Conversation
@open-telemetry/python-maintainers @open-telemetry/go-maintainers |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Even though it's a common practice to increment major versions of a package when even an EOL verision of the runtime is dropped in JS, I don't think it makes sense for API and probably SDK.
Bumping in that case would hurt interoperability and adoption immensely long term.
Co-authored-by: Yuri Shkuro <[email protected]>
I think a change in support for a language/runtime version should not necessarily force a major version bump.
Examples where I agree that making a version bump would be an overkill:
However, bumping a minor version in such cases makes sense.
PS. Maybe I wrongly understand what "a drop in support" means.
FYI @open-telemetry/dotnet-maintainers