aljazerzen commented on issue #5368: URL: https://github.com/apache/arrow-rs/issues/5368#issuecomment-2078971411
> But perhaps releasing together doesn’t prevent us from using separate versions? 🤔 I would agree: if ASF release process is fine with arrow-rs having separate releases, it should not have a problem with each crate having its own versioning. > It’s fast moving, and does have a lot of breaking changes. It looks like this is still the case, but not because of change to the `arrow` or the core crates, but because dependencies to pyo3 and object_storage, which are still "fast moving". So my suggestion would be to split the pyarrow feature into a separate crate, which would significantly decrease breaking changes to `arrow` crate itself. Do I have a go-ahead to start a PR that would do 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]
