Hi Heesung, I support this proposal, but I would have expected you to first reply on the email thread started by Nicolo in February https://lists.apache.org/thread/c0k8p9vy5wyp9l70mt980gdy10smx6qb .
Nicolo Boschi has been working on Java 17 compatibility for months and also brought this up to discussion on the mailing list and in the Pulsar community meetings several times in the past. Last discussion about the Java 17 work was recorded in these community meeting notes: https://lists.apache.org/thread/tq7dsws72zf9r7qzr4l567z9w346ksbm . The credits for Java 17 compatibility goes to Nicolo. I expect that members of the Pulsar community pay more attention to ongoing work that is announced on the dev mailing list. In this case, it would have been fair to provide feedback on the "JDK 17 runtime compatibility" thread that Nicolo started in February or comment on the PR https://github.com/apache/pulsar/pull/14355 which takes the move to use Java 17 for CI and for the Docker images. -Lari On 2022/04/18 18:25:13 Heesung Sohn wrote: > Dear Pulsar dev community, > > My name is Heesung Sohn, and I would like to open a discussion here > about PIP-156: > Build and Run Pulsar Server on Java 17 > <https://github.com/apache/pulsar/issues/15207>. > > > @Nicolò Boschi, > I see your similar PR <https://github.com/apache/pulsar/pull/14355> for the > Java 17 runtime support. Since some of the Java 17 upgrade work could > overlap, it would be great if we can discuss how to collaborate too -- for > this PIP, we need to additionally update the `javac --release` option to > Java 17. > > Regards, > Heesung > -- > > <https://streamnative.io> > > Heesung Sohn > > Platform Engineer > > e: heesung.s...@streamnative.io > > streamnative.io > > <http://github.com/streamnative> > <https://www.linkedin.com/company/streamnative/> > <https://twitter.com/streamnativeio/> >
