Github user cloverhearts commented on the issue:
https://github.com/apache/zeppelin/pull/1659
:)
I listened to your feedback, and tested the current version.
Surely your opinion is correct.
I personally have experienced problems with versioning up tools and
environments.
So I wrote a comment.
I have verified the build test for node 6 and the behavior of the legacy
library.
There were some problems, but it was a problem that is happening in the
current version.
I think this is not a problem in upgrading node 6.
I think that's why we should upgrade to node 6 rather.
(Also for ES6 and other reasons)
Thank you for listening to my comments.
I agree to upgrade the Node 6 version.
LGTM :)
---
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.
---
