rdblue commented on pull request #30554: URL: https://github.com/apache/spark/pull/30554#issuecomment-737383178
> > Can you point to where this is allowed by the versioning policy? > > Quoted below: > > > The Spark project strives to avoid breaking APIs or silently changing behavior, even at major versions. While this is not always possible, the balance of the following factors should be considered before choosing to break an API. > > We try to avoid breaking changes, but we don't completely forbid it. Breaking changes are allowed when it's justified. We definitely don't allow arbitrary breaking changes. I think that you're misinterpreting it. That means that Spark avoids breaking APIs and behavior even at major releases. It is more strict, not more lax. It does not mean that the rules are flexible and Spark will make breaking behavior changes. This expectation is set in the first paragraph, where it states that Spark will follow semver, except for a small set of multi-module issues. ---------------------------------------------------------------- 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. For queries about this service, please contact Infrastructure at: [email protected] --------------------------------------------------------------------- To unsubscribe, e-mail: [email protected] For additional commands, e-mail: [email protected]
