zeroshade commented on pull request #11570: URL: https://github.com/apache/arrow/pull/11570#issuecomment-954775055
@emkornfield If we want to keep the major version number the same for the Go lib as it is for the rest of them, then yes we'd need to make this broad change on every major release. It's part of the reason why standard Go library development is to avoid major version upgrades unless you actually make a breaking change. By changing the import path you can actually have a new version and old major version side by side in a project if necessary etc. it's actually easier on consumers surprisingly. I can make a post in the dev@ mailing list about this -- 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]
