alamb commented on issue #5368: URL: https://github.com/apache/arrow-rs/issues/5368#issuecomment-1932012460
> I think the key to making this work, is to devise a minimally intrusive process where we can still make breaking changes, but still maintain patch releases. I don't really know the best way to achieve this. Here are some options I can think of: 1. Release all versions from main: (merge no breaking API changes to main until we are ready to make another major version, but otherwise keep the release cadence the same) 2. Release minor versions from a maintenance branch (merge anything to main, and backport compatible changes to maintenance branch) I think option 1 is the lowest maintainer overhead approach, but has the drawbacks of: 1. Limits when breaking API changes can be merged 2. We would have to come up with some criteria of "when would we merge such breaking changes" -- 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]
