Github user jongyoul commented on the issue:
https://github.com/apache/zeppelin/pull/2024
I'm not sure who think what now, I just let you know the history. If you
really want to move JDK8, open discussion and reach a "consensus" with
community first. I think moving to JDK8 doesn't
Github user DmytroShkvyra commented on the issue:
https://github.com/apache/zeppelin/pull/2024
@jongyoul May be make sense just create PR only for try moving to JDK8 and
test this with Travis? Anyway nobody will not merge it to zeppelin without
approve.
---
If your project is set
Github user jongyoul commented on the issue:
https://github.com/apache/zeppelin/pull/2024
You don't have to do it because we eventually will move to further JDK
version
---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If
Github user DmytroShkvyra commented on the issue:
https://github.com/apache/zeppelin/pull/2024
@jongyoul Should I close ZEPPELIN-411 as "wont fix"?
---
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
Github user jongyoul commented on the issue:
https://github.com/apache/zeppelin/pull/2024
And concerning your contribution, we discussed it before and concluded it's
too early to move JDK8. If you think it's right time to move on, please start
discussion again in dev@ and user@
---
Github user jongyoul commented on the issue:
https://github.com/apache/zeppelin/pull/2024
In case that you encounter conflicts, you have to rebase your changes onto
the base branch you start working on. AFAIK, ASF doesn't allow write permission
through Github.
---
If your project
