aljazerzen commented on issue #5368: URL: https://github.com/apache/arrow-rs/issues/5368#issuecomment-2010576633
> I propose we set a more regular major release cadence (e.g. every 3 months) and only do minor, compatible, releases between those releases. I mean the original one. I found this issue because I'm running into the problem of managing transitive dependencies to arrow-rs. Because I depend on duckdb-rs and because it had not need updated to use arrow-rs 50, I cannot upgrade my dependency on arrow-rs, since I want compatible versions. Other popular crates (such as serde or regex) don't cause this problem because they only publish minor or patch releases. If this was the case with arrow-rs, then duckdb-rs could depend on arrow-rs~=1.49, which would be compatible with a new version of arrow-rs 1.50. Obviously arrow-rs cannot go back to version 1.x, but it could stop releasing new major versions that don't contain breaking changes. It would mean much less toll on downstream maintainers. -- 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]
