It seems like people are generally in favor, I'll start a vote thread.
Ismael
On Fri, Dec 22, 2023 at 10:39 AM Ismael Juma wrote:
> Hi all,
>
> I was watching the Java Highlights of 2023 from Nicolai Parlog[1] and it
> became clear that many projects are moving to Java 17 for its developer
>
Hi David,
This KIP complements KIP-750 since it only proposes an additional change to
the broker and tools modules.
Ismael
On Tue, Dec 26, 2023 at 1:38 PM David Arthur
wrote:
> Thanks, Ismael. I'm +1 on the proposal.
>
> Does this KIP essentially replace KIP-750?
>
> On Tue, Dec 26, 2023 at
Hi Divij,
You asked and answered. :) Java 21 is too new and Apache Kafka would be
requiring it before most other projects. Java 17, on the other hand, has
been out for over 2 years and it is on its way to becoming the new baseline
for many popular and related projects.
Ismael
On Tue, Dec 26,
Thanks, Ismael. I'm +1 on the proposal.
Does this KIP essentially replace KIP-750?
On Tue, Dec 26, 2023 at 3:57 PM Ismael Juma wrote:
> Hi Colin,
>
> A couple of comments:
>
> 1. It is true that full support for OpenJDK 11 from Red Hat will end on
> October 2024 (extended life support will
Thanks for starting this conversation Ismael. The proposal sounds great to
me.
I understand that JDK 21 is brand new and that may be the answer here, but
I am curious to learn about your thoughts on moving the broker module
directly to JDK 21 instead with 4.0, instead of JDK 17.
(As a one-off
Hi Colin,
A couple of comments:
1. It is true that full support for OpenJDK 11 from Red Hat will end on
October 2024 (extended life support will continue beyond that), but Temurin
claims to continue until 2027[1].
2. If we set source/target/release to 11, then javac ensures compatibility
with
Hi Ismael,
Looks good to me. Looking forward to programming using features and
types included in JDK17 in 4.0 and not having to program using a 10
year old programming language and library.
Thanks!
--
-José
Hi Ismael,
+1 from me.
Looking at the list of languages features for JDK17, from a developer
productivity standpoint, the biggest wins are probably pattern matching and
java.util.HexFormat.
Also, Java 11 is getting long in the tooth, even though we never adopted it. It
was released 6 years
Hi all,
I was watching the Java Highlights of 2023 from Nicolai Parlog[1] and it
became clear that many projects are moving to Java 17 for its developer
productivity improvements. It occurred to me that there is also an
opportunity for the Apache Kafka project and I wrote a quick KIP with the
