crepererum commented on issue #677: URL: https://github.com/apache/arrow-rs-object-store/issues/677#issuecomment-4160439587
> This is the 0.x.y release series, so strictly by semver, you are allowed to break anything with any release. We are allowed, but from a maintainers & community perspective that would be rather counterproductive, esp. given the size of the ecosystem that now depends on `object-store`. Hence we try to view `0.x+1` bumps as "new major release" and `0.x.y+1` bumps as "new minor release". That's also in line with the [Cargo SemVer Compatibility guidelines](https://doc.rust-lang.org/cargo/reference/semver.html) which state (emphasis added by myself): > This guide uses the terms “major” and “minor” assuming this relates to a “1.0.0” release or later. Initial development releases starting with “0.y.z” **can** treat changes in “y” as a major release, and “z” as a minor release. “0.0.z” releases are always major changes. [...] --- So back to the reported issue: > Changing feature gates should be considered a breaking change not done in patch releases. In #644 we somewhat tried to do that, so at least if you use the default features this isn't breaking. So the issue here only applies to users of `no-default-feature`. Given the limited impact and the churn that rolling back this change would create, I'm somewhat inclined to accept this breaking change and keep that in mind for future 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]
