jdye64 opened a new issue, #123: URL: https://github.com/apache/arrow-datafusion-python/issues/123
Apologies if this isn't the correct venue for discussing this but I want to discuss versioning for `arrow-datafusion-python`. With the `arrow-datafusion` 16.0.0 release in motion I was thinking about the versioning for an upcoming `arrow-datafusion-python`. If the pattern continues the next version would be `0.8.0`. This was confusing to me when first starting with `arrow-datafusion-python` since I was expecting to find the version for the python bindings to match that with the version of `arrow-datafusion` I was using, this isn't the case. So my proposal is, why don't we keep the release versions for `arrow-datafusion-python` in sync with `arrow-datafusion` and have the next release of `arrow-datafusion-python` be `16.0.0`. I believe this helps make things much more clear to the end user about which underlying version of datafusion they are using. If there are bugs in `arrow-datafusion-python` itself that warrant a release then we could just append a post-release fix version to the number. Curious of others thoughts on this? I know software versioning can almost be a religious discussion at times and this is just a very coarse layout -- 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]
