mbrobbel commented on issue #2263: URL: https://github.com/apache/arrow-adbc/issues/2263#issuecomment-2425951709
> in tree until the Rust APIs have settled a bit I agree with this. Keeping it in tree helps to understand how changes to core traits impact existing drivers, and drivers must be updated as part of PRs that change these traits. > maybe something to explore is versioning the Rust API definitions separately as well so there is a very stable target instead of churning the version number every 2 months for no reason I agree it would be better to track this separately. There are a few things to consider: - I guess this complicates the release process a little bit? - As long as we're still using `0.x.y` versions, applying non-breaking minor bumps is trivial for dependents, especially when they are using something like Dependabot. - We are going to have to release whenever `arrow-rs` releases a new major version (we are using `arrow-rs` types in our public API). Dependents using both `arrow-rs` and `adbc` crates are blocked from updating their arrow related dependencies until we release with the latest `arrow-rs` major version. -- 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]
