lmccay commented on PR #506: URL: https://github.com/apache/incubator-livy/pull/506#issuecomment-3764091267
> As it relates to Java 8. I used to be a system admin, and I am all about backwards compatibility. But for realism sake: Spark is at 3.5 (17) and 4.X. I find it really hard to believe someone would pick up livy trunk today, and say "I really want to run new shiny living on spark 2.3 and hadoop 2.4 on java 8". Likewise I cant imagine anyone using livy-0.7 on spark2 and then saying "i need this critical bug fix in trunk" I would say branch off an old one. Again, this is a community decision and not one to make at a pull request level. Bring it to the dev@ list and drive the DISCUSS, change the PR to pass in current project state or wait for the community to bring it up. It's not getting merged while failing test runs on currently supported Java versions and we aren't dropping support for a java version for a clean up pull request failing tests. There are aspects to consider in dropping the version of java than just dropping support that need to be discussed as well. We will need to determine the near term policy on java 17+ syntax and the effect on backports while previous lines are still technically supported and may need at least security patches. These are the sorts of things that make it a larger discussion. -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: [email protected] For queries about this service, please contact Infrastructure at: [email protected]
