[GitHub] [arrow-datafusion-python] jychen7 commented on issue #123: [DISCUSS] arrow-datafusion-python versioning

["jychen7 (via GitHub)" <gi...@apache.org>]

jychen7 commented on issue #123:
URL: https://github.com/apache/arrow-datafusion-python/issues/123#issuecomment-1399798994

   I like the idea of explicit version linking for language binding.
   
   It is hard to have a general rule using Semver for bindings. See https://github.com/semver/semver/issues/352
   
   However, from Datafusion history, it nornally uses major version and rarely use minor version. It haven't use patch version so far. So probably we can specially align on `major.minor` and let bindings use `patch` version.
   
   e.g.
   Rust 16.0.0 -> Python 16.0.0, 16.0.1, etc
   Rust 16.1.0 -> Python 16.1.0, 16.1.1, etc
   
   What if Datafusion Rust starts using patch version? That's a trade off we need to accept. If our rule is aligb on `major.minor`, then I think following is acceptable.
   
   Rust 16.0.0 - Python 16.0.0, 16.0.1, 16.0.2
   Rust 16.0.1 - Python 16.0.3, etc
   
   https://github.com/apache/arrow-datafusion/blob/16.1.0-rc1/dev/release/README.md


-- 
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: github-unsubscribe@arrow.apache.org

For queries about this service, please contact Infrastructure at:
users@infra.apache.org