zeroshade edited a comment on pull request #11570: URL: https://github.com/apache/arrow/pull/11570#issuecomment-954334003
@kou the philosophy for go is that major version upgrades are only ever done for breaking changes, if it's not a breaking change then it shouldn't be a major version upgrade. The only reason I'm advocating it is to keep the version number in line with the other implementations. As such this change is intentionally backwards incompatible, a user would have to explicitly upgrade their import statements if they upgrade to this version. Specifically it would only make them upgrade their import statements, but that would be the case for any major version upgrade, and doesn't have much to do with the shift of the way the modules are defined. -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: [email protected] For queries about this service, please contact Infrastructure at: [email protected]
