alamb commented on issue #5368: URL: https://github.com/apache/arrow-rs/issues/5368#issuecomment-2122312282
> I'm sorry to be curt, but I'm growing a bit frustrated that this conversation appears to be going in circles, the core abstractions in arrow-rs are not stable, can't be treated as such, and no amount of release hackery will change this. I agree with this point. Unless/until we have more discipline about keeping the APIs stable, major version bumps are required. I see conventional commits / unstable feature flags, etc as way to improve discipline around keeping APIs stable. Maybe one way to reduce maintainer bandwidth requirements would be to implement a CI check for breaking API. I filed https://github.com/apache/arrow-rs/issues/5791 to track this idea. Anyone interested in helping ease the maintenance burden maybe could help figure out how to automate some of it -- 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]
