We are running into an increasing number of Java libs that we rely on that don't support Java 8.
Can I suggest that we cut v1.1.x branches on some of our worst affected modules and raise the minimum Java version on the main branches to Java 17. Most of the libs that affect us still support Java 11 but there are a few like Aeron and Spring where the latest versions need Java 17. The modules where I think we should start are: * pekko-persistence-jdbc * pekko-connectors (after we do the 1.1.0 release which should be soon) Can I suggest that we call the next releases on these modules where we drop Java 8 support version 2.0.0? Regarding dropping Scala 2.12 support - I think we shouldn't. After checking the download stats for our jars, Scala 2.12 remains popular - way more popular for Pekko users than Scala 3. I'll go with the flow, if people actually think we should drop Scala 2.12 for the dev version of Pekko. There is an argument to say that Scala 2.12 users can stick with Pekko 1.1 or 1.0. We will continue to do bug fixes and critical dependency updates for our legacy release lines. I also think that we should drop some of the connectors in the forward dev version of Pekko Connectors (future Pekko Connectors v1.2.0 or v2.0.0 release). We no longer properly test some of the connectors because the Docker setups are broken. We can always bring back abandoned Connectors if we find some volunteers to help maintain them. On 2024/08/16 15:47:06 PJ Fanning wrote: > We have another discussion open about doing a Pekko 1.1.0 release. > > After we get that released, we will have to do 1.1.0 releases for > other other Pekko modules (HTTP, gRPC, Connectors, etc.). > > At the same time, we would need to decide on what to do about the next > release after that. > > I would suggest that we should consider making that next release a > 2.0.0 release - one where we get to remove some deprecated code and > potentially update the minimum Java and Scala versions that we > support. > We will continue to do patch releases for Pekko 1.0.x and Pekko 1.1.x > so users who are affected by us dropping some things are not going to > be too badly affected. > > * Drop Scala 2.12 support? The Scala 2.12 compiler has some type > inference issues that complicate our code. The next Scala 3 LTS > version looks like it will have some changes that will make it more > different from Scala 2.12. > * Go to Java 11 or even 17 as a minimum Java version? We already have > issues in Pekko Connectors where we are stuck on older dependency > versions because those dependencies have moved on from Java 8. > * Drop the methods and classes that were deprecated in Akka before we > split out Pekko? > * Possibly remove some of the methods and classes that we deprecated in Pekko > 1? > > What does everyone think? > > --------------------------------------------------------------------- > To unsubscribe, e-mail: dev-unsubscr...@pekko.apache.org > For additional commands, e-mail: dev-h...@pekko.apache.org > > --------------------------------------------------------------------- To unsubscribe, e-mail: dev-unsubscr...@pekko.apache.org For additional commands, e-mail: dev-h...@pekko.apache.org
