alamb commented on code in PR #5737: URL: https://github.com/apache/arrow-rs/pull/5737#discussion_r1607287684
########## README.md: ########## @@ -34,7 +34,33 @@ This repo contains the following main components: The current development version the API documentation in this repo can be found [here](https://arrow.apache.org/rust). -There are two related crates in a different repository +## Release Versioning and Schedule + +The Arrow Rust project releases approximately monthly and follows [Semantic +Versioning](https://semver.org/). Review Comment: > I am a little confused by this statement and others here. My understanding from https://github.com/apache/arrow-rs/issues/5368 and elsewhere was that arrow-rs doesn't follow semver, except maybe with its minor and patch releases. From my perspective arrow-rs follows semver as implemented by rust / cargo. > My understanding of the spirit of semver is that major releases absolutely include breaking changes That may be the "spirit" or ideal, but my understanding is that semver means breaking changes only occur in major versions. > so if arrow-rs releases majors on a schedule and those majors only may include breaking changes, that wouldn't be following semver. Does that match your interpretation? No. However, what we have done in the past is if a scheduled release includes no breaking changes, we did a minor release. However, the API is so large practically all releases have had at least one breaking change (I think I remember one that did not) what I expect to happen is that each quarterly release will include breaking API changes (however small). If they don't have breaking changes we can do a minor relese -- 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]
