alamb commented on issue #2095: URL: https://github.com/apache/arrow-datafusion/issues/2095#issuecomment-1079900357
> Agree to make 3-layer releases: major, minor, bug fix. Arrow C++ does major quarterly releases; I have not seen a minor release (e.g. 6.1.0) in the last year. Occasionally there are patch releases but it is infrequent and typically once per major release. I agree the three release sounds ideal as well. > minor release (from master), every 1 month If we intended to conform to ["semantic versioning"](https://doc.rust-lang.org/cargo/reference/semver.html) in the rust style, it is a challenge to release minor versions from `master`. For the minor (e.g. 7.0.0 to 7.1.0) release to be semantically versioned no breaking API changes can be introduced which would restrict what we can put on master > Another question is whether it is necessary to maintain the same version for different modules, like Ballista, datafusion-data-access (newly splitted one). I do not think it is necessary to keep the same versions. I keep the versions of arrow-rs/arrow-flight/parquet in sync because it lowers the release overhead. -- 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]
