I understand the sentiment for removing JDK 8 support but as has been stated in this thread there are still significant organizations/companies that use JDK 8, as shocking as it is.
Given this, in my view dropping it even in 1.1.x series is too soon mainly because it's the 1.1.x series that will get new features not 1.0.x and its in everyone's interest to provide an easy path for those still on JDK 8 to move off it. While it is frustrating to deal with JDK 8, this is one of those things where once you build in the structure/support to handle JDK 8, for the most part you don't notice it (this is similar to Scala 2.12 support, the burdon of which now is barely noticaeble). In fact I expect that these recent fixes to Mima is probably going to be one of the latest changes that we need to do to keep up JDK 8 support. That being said, we do need to drop JDK 8 support at some point because it becomes increasingly ridiculous as time goes on. I think 1.2.x is a good time for this, but it should be voted on and signalled strongly. Also we can't drop JDK 8 support right now without code changes, there is usage of misc.sun.unsafe in Pekko core which was changed/removed in JDK 11. On Fri, 14 July 2023, 17:23 PJ Fanning, <[email protected]> wrote: > Hi everyone, > > Is there any appetite for abandoning Java 8 support in Pekko 1.1.0? > > An example discussion: > > https://github.com/apache/incubator-pekko/discussions/482 > > There is also a complication in our MIME checks due to Java 8. > > https://github.com/apache/incubator-pekko/pull/481 > > I'm usually quite reluctant to move away from supporting legacy Java > versions but maybe it's time to start dropping Java 8 support. Java 8 > users can stick with Pekko 1.0.0. > > Does anyone have any thoughts on this? > > Regards, > PJ > > --------------------------------------------------------------------- > To unsubscribe, e-mail: [email protected] > For additional commands, e-mail: [email protected] > >
