Github user gatorsmile commented on the issue:
https://github.com/apache/spark/pull/21060
@steveloughran Agree. We always can make an exception if most need it.
- For any external behavior change (even in experimental APIs), we need to
document it and also mention it in the release note. This can simplify the
version upgrade and let our users trust us.
- Need to have more discussion regarding the backport policy (to the
maintenance branches and release candidate branches). This should be discussed
and finalized at least in the dev list. When the policy is completed, we should
also send it to the user list and the committers are responsible for enforcing
it.
I am trying to summarize what we did in the Spark 2.3 release. It took
almost 2 month to release it. Will send the postmortem to the community with
some proposal about the backport policy.
---
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
