Hi Charly, Java versions have a much bigger impact. The Scala version for the Kafka broker is mostly an implementation detail. The Kafka Streams library for Scala is not as clear, but this is a recent library and I don't think it makes sense to bump the major version for the whole project, we should mention it in the upgrade notes instead.
Apache Kafka 3.0 is likely to happen as part of the KIP-500 (Built-in consensus) effort and that may take a while. I don't think we should wait for that to streamline the development process. As stated in the KIP, Scala 2.12 has been out for 3 years so people have had enough time to migrate. Ismael On Fri, Nov 8, 2019 at 1:07 AM charly molter <charly.mol...@gmail.com> wrote: > This makes sense but as this is a breaking change shouldn’t it be happening > in a major version? > I believe that’s what was done with java7 support isn’t it? > > On Fri, 8 Nov 2019 at 01:56, Gwen Shapira <g...@confluent.io> wrote: > > > About time :) Let's do it. > > > > On Thu, Nov 7, 2019 at 5:35 PM Ismael Juma <ism...@juma.me.uk> wrote: > > > > > > Hi all, > > > > > > I think it's time to simplify our development environment by dropping > > > support for Scala 2.11. Please take a look at the proposal and > > > provide feedback: > > > > > > > > > https://cwiki.apache.org/confluence/display/KAFKA/KIP-531%3A+Drop+support+for+Scala+2.11+in+Kafka+2.5 > > > > > > Ismael > > > -- > Charly Molter >
