-
Notifications
You must be signed in to change notification settings - Fork 16
feat: bump arrow to 57 #61
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Conversation
|
Let's release a new version. |
|
@WenyXu yes, this time it should be 0.7.0 |
|
Why require |
|
@progval We will create minor version for each major release of arrow. So user of this library will not silently upgrades to a new major arrow version. |
|
I don't follow. Users with a lockfile won't silently upgrade either way, because the array versions is in the lockfile. Users without a lockfile will (assuming they have a semver dependency like And coupling orc-rust versions with arrow version has the issue that if someone wants a bug fix, then it unnecessarily forces them to use a new Arrow version. For example #56 is only in orc-rust 0.7.0, along with this version bump. |
|
I got your point. For example, in datafusion-orc we have datafusion 50 which uses arrow 56 in its interface. If we have But I understand the issue you point out is a real issue. We need to create a patch release 0.6.x for arrow 56 to include bugfix between current 0.6.4 and 0.7.0 |
Hmm, that's a disappointing behavior from Cargo. Users can work around it with
I'm all for that, but it can be significant work to maintain old branches so I'd understand if no one wants to do it. |
|
Yes, I think the release process can be:
|
No description provided.