-
Notifications
You must be signed in to change notification settings - Fork 314
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Drop java 8 #1218
Comments
Not sure many jetcd users are watching this project. P.S. |
fixed |
@liangyuanpeng will you work on this ? |
Yes, assign to me please,Thanks. |
You've done a very bad thing and wasted a week of my time.
Please change this desc. |
@tulayang |
@tulayang
This is true, and this does not affect users. check the build log for java8: https://github.com/liangyuanpeng/jetcd/actions/runs/6269397502/job/17025771942 |
Forward my concern from the Apache Kyuubi community.
BTW, any specific issues for keeping support for Java8? |
#1181 (comment) vvv
@pan3793 Actually, there are not some specific issues for it, Except it is currently not possible to build with java8. Jetcd depends on vertx-grpc. Currently, vertx-grpc 5.x CI no longer has java8, so may encounter obstacles when upgrading the vertx-grpc component in the future. This issue just a notification now, I think we will still support java8 for some time to come. |
@liangyuanpeng thanks for supplying background, I just leave my concerns from the Apache Kyuubi aspect and it's up to the project maintainer for final decision. |
Java 8 will be dropped with v0.8.x releases |
So far Jetcd still has only one active maintainer, and is active on personal time.
In order to reduce the pressure of maintenance and follow the development of java version, I think it is a good thing that jetcd no longer supports java 8.
Jetcd's maintenance requirements for the java version will likely be LTS-2, it's mean to drop java 8 when after java 21 GA.
The following is the impact on the user list:
✔️ -> No change.
❌ -> Breaking change.
The text was updated successfully, but these errors were encountered: