Github user steveloughran commented on the issue:
https://github.com/apache/spark/pull/21060
* from the ASF process-police perspective, something like
versioning/backport policy is something which should be done on the ASF dev
list...consider asking in user@ to see what people's preferences are.
Worthwhile mentioning in the project report too.
* from a personal perspective: its good to have a policy, but really good
to leave a little bit of wiggle-room, even if its something like 'a vote on the
developer list can override any policy on a case-by-case basis". That is: you
can do more than just fixes, but its something where the decision is opened up.
This makes clear the cost *and* avoids the "why did you cherry-pick this
without asking me" conversations.
---
---------------------------------------------------------------------
To unsubscribe, e-mail: reviews-unsubscr...@spark.apache.org
For additional commands, e-mail: reviews-h...@spark.apache.org
