Github user jkbradley commented on the issue:
https://github.com/apache/spark/pull/16623
Thanks for the comments. I definitely agree with many of your combined
statements:
* R has not been declared stable. (Though where in the docs is this even
stated? I was unable to find anything saying it is an alpha component.)
* Some changes are necessary and OK, such as APIs which simply do not work.
* We could still be stricter about some API changes.
If I'm a user of SparkR, I agree I'd expect it to be less stable than the
rest of Spark. But apparent instability from changing APIs can also scare away
users from putting SparkR into actual use. It's a balance, but I'd prefer to
err on the side of stability.
I do like the idea of tagging backports, but it's Ok with me not to as long
as there is proper explanation of the reason within the JIRA.
---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
enabled and wishes so, or if the feature is enabled but not working, please
contact infrastructure at infrastruct...@apache.org or file a JIRA ticket
with INFRA.
---
---------------------------------------------------------------------
To unsubscribe, e-mail: reviews-unsubscr...@spark.apache.org
For additional commands, e-mail: reviews-h...@spark.apache.org
