Hi all,
The vote passes with:
* 8 binding votes (Justine Olshan, Satish Duggana, Viktor Somogyi-Vass,
Divij Vaidya, Mickael Maison, Greg Harris, David Arthur, myself)
* 1 non-binding vote (Kamal Chandraprakash)
Thanks,
Ismael
On Wed, Jan 3, 2024 at 2:28 AM Ismael Juma wrote:
> Hi all,
>
> I
+1 binding
Thanks!
David
On Wed, Jan 3, 2024 at 8:19 PM Ismael Juma wrote:
> Hi Mickael,
>
> Good catch. I fixed that and one other (similar) case (they were remnants
> of an earlier version of the proposal).
>
> Ismael
>
> On Wed, Jan 3, 2024 at 8:59 AM Mickael Maison
> wrote:
>
> > Hi
Hi Mickael,
Good catch. I fixed that and one other (similar) case (they were remnants
of an earlier version of the proposal).
Ismael
On Wed, Jan 3, 2024 at 8:59 AM Mickael Maison
wrote:
> Hi Ismael,
>
> I'm +1 (binding) too.
>
> One small typo, the KIP states "The remaining modules (clients,
Hi Ismael,
I'm happy to see the minimum Java version moving forward, even if it's
just for the broker and tools. I hope that this encourages operators
to upgrade to 17+ across-the-board, and will make it easier to drop
support for 11 in the other modules in 5.0.
+1 (binding)
Thanks,
Greg
On
Hi Ismael,
I'm +1 (binding) too.
One small typo, the KIP states "The remaining modules (clients,
streams, connect, tools, etc.) will continue to support Java 11.". I
think we want to remove support for Java 11 in the tools module so it
shouldn't be listed here.
Thanks,
Mickael
On Wed, Jan 3,
+1 (binding)
--
Divij Vaidya
On Wed, Jan 3, 2024 at 11:06 AM Viktor Somogyi-Vass
wrote:
> Hi Ismael,
>
> I think it's important to make this change, the youtube video you posted on
> the discussion thread makes very good arguments and so does the KIP. Java 8
> is almost a liability and Java
Hi Ismael,
I think it's important to make this change, the youtube video you posted on
the discussion thread makes very good arguments and so does the KIP. Java 8
is almost a liability and Java 11 already has smaller (and decreasing)
adoption than 17. It's a +1 (binding) from me.
Thanks,
Viktor
+1 (non-binding).
On Wed, Jan 3, 2024 at 8:01 AM Satish Duggana
wrote:
> Thanks Ismael for the proposal.
>
> Adopting JDK 17 enhances developer productivity and has reached a
> level of maturity that has led to its adoption by several other major
> projects, signifying its reliability and
Thanks Ismael for the proposal.
Adopting JDK 17 enhances developer productivity and has reached a
level of maturity that has led to its adoption by several other major
projects, signifying its reliability and effectiveness.
+1 (binding)
~Satish.
On Wed, 3 Jan 2024 at 06:59, Justine Olshan
Thanks for driving this.
+1 (binding) from me.
Justine
On Tue, Jan 2, 2024 at 4:30 PM Ismael Juma wrote:
> Hi all,
>
> I would like to start a vote on KIP-1013.
>
> As stated in the discussion thread, this KIP was proposed after the KIP
> freeze for Apache Kafka 3.7, but it is purely a
Hi all,
I would like to start a vote on KIP-1013.
As stated in the discussion thread, this KIP was proposed after the KIP
freeze for Apache Kafka 3.7, but it is purely a documentation update (if we
decide to adopt it) and I believe it would serve our users best if we
communicate the deprecation
11 matches
Mail list logo
