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
Minor version release is a breaking change on td-agent #6192
Comments
CC @TeBoring @isukapalli I updated the gemspec to require version 2.3 based on the conversation in this other issue: #1594 (comment) I usually don't work on Ruby so I am not as familiar with it, but it sounded to me like earlier versions were not really supported even if the gemspec allowed them. Have you found that Ruby 2.0 actually works with recent versions of protobuf? |
Updating the ruby version from say 2.2 to 2.3 isn't a breaking change? If that is the issue? The only major ruby repository to treat it as such is rspec, and they're changing that tact. No other major ruby gem to my knowledge does so, and it doesn't really contradict semver? |
Thanks for the response @acozzette and @luke-hill. |
Ok so a couple of points.
Can you re-read my points and try to understand them. It sounds like your plugin is highly sensitive to protobuf so I would advise a |
Thanks @luke-hill for the explanation. |
Now all you need to do is get jruby fixed up as well on one consistent version going forward and you'll make a lot of people happy. |
What version of protobuf and what language are you using?
Version: master/v3.8.0
Language: Ruby
What operating system (Linux, Windows, ...) and version?
Amazon Linux
What runtime / compiler are you using (e.g., python version or gcc version)
What did you do?
Steps to reproduce the behavior:
What did you expect to see
Breaking changes should be released as major version.
What did you see instead?
Make sure you include information that can help us debug (full error message, exception listing, stack trace, logs).
Anything else we should know about your project / environment
The text was updated successfully, but these errors were encountered: