Github user yu-iskw commented on the pull request:
https://github.com/apache/spark/pull/7883#issuecomment-127141523
Yeah, we could also maintain lintr with the way as you mentioned. However,
it is a little bothersome to me. And there is a risk that it will be technical
debt in future. Since it will depend on persons in charge of the Jenkins. And
from the other developer's point of view, it is a little hard for them to
understand the mechanism without any document.
FWIW, it seems that PEP8 which is a tool for checking python code is
installed on every run with `dev/lint-python`.
What does @JoshRosen think about the way to update lintr?
---
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 [email protected] or file a JIRA ticket
with INFRA.
---
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
