[GitHub] [arrow-rs] tustvold commented on issue #2180: Figure out and document the versioning and release cadence for object_store

[GitBox <gi...@apache.org>]

tustvold commented on issue #2180:
URL: https://github.com/apache/arrow-rs/issues/2180#issuecomment-1199530487

   > I am not 100% sure what @tustvold 's plan is in this regard
   
   I would like to at some point provide object_store integration within arrow-rs and parquet, behind an optional feature flag, as particularly in the case of parquet it can be non-obvious how to integrate them. I would expect, however, that in such a case bumping the major version of object_store depended on by arrow/parquet would constitute a breaking change to those crates.
   
   That being said:
   
   * I don't expect object_store to receive breaking changes at the same rate as arrow-rs, etc...
   * I don't see a compelling reason to couple the versions of crates in the repo together, especially not those that change less frequently, e.g. object_store_rs, arrow-flight, parquet_derive, etc... This feels like a release tooling limitation more than anything else
   * If we can avoid bumping object_store_rs to major version > 1, that would be my preference
   * I don't feel particularly strongly about any of this, the version of a crate is somewhat immaterial provided semver is being followed, in practice whether it is 0.5 of 200.0.3 means very little


-- 
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