Re: [DISCUSS] Apache Kafka 3.8.0 release

[Josep Prat]

I'm starting with the process now.

Best,

On Thu, Jul 18, 2024 at 2:12 AM Greg Harris 
wrote:

> Hi all,
>
> We found a blocker in 3.8.0-rc1
> https://issues.apache.org/jira/browse/KAFKA-17150 that is now merged to
> trunk and backported to 3.8.
> Additionally I've merged and backported the lower-severity
> https://issues.apache.org/jira/browse/KAFKA-17148 to trunk, 3.8, and 3.7
> because Dmitry Werner provided a very prompt fix.
> Thanks to Chia-Ping, Chris, and Josep for prompt reviews. At this time I am
> not aware of any more blockers for 3.8.0 and we can proceed with rc2.
>
> Thanks!
> Greg
>
> On Wed, Jul 10, 2024 at 10:49 PM Josep Prat 
> wrote:
>
> > Hi Greg,
> >
> > I'll make sure the PR with the fix (
> > https://github.com/apache/kafka/pull/16565) gets merged today. Thanks
> for
> > bringing this up!
> >
> > Best,
> >
> > --
> > Josep Prat
> > Open Source Engineering Director, Aiven
> > josep.p...@aiven.io   |   +491715557497 | aiven.io
> > Aiven Deutschland GmbH
> > Alexanderufer 3-7, 10117 Berlin
> > Geschäftsführer: Oskari Saarenmaa & Hannu Valtonen
> > Amtsgericht Charlottenburg, HRB 209739 B
> >
> > On Wed, Jul 10, 2024, 22:55 Greg Harris 
> > wrote:
> >
> > > Hi Josep,
> > >
> > > A contributor just raised a regression [1] that I think should be
> > addressed
> > > in 3.8.0 prior to the release.
> > >
> > > Summary: This change [2] causes multiple ERROR logs to appear during
> > worker
> > > startup when operators install other, unrelated plugins that package
> the
> > > Jackson library.
> > > Severity: Workers will continue to operate normally and the errors will
> > be
> > > cosmetic. Operators and automatic systems that watch logs may roll-back
> > > upgrades due to the perception of a severe problem.
> > > Impact: I found 12 out of 250 third-party plugins that package the
> > Jackson
> > > library and trigger this error on upgrade. This will almost certainly
> > > affect several users upon upgrades, and does not require obscure
> setups.
> > > Risk: The contributor has opened a simple fix PR [3], and I have
> verified
> > > that it addresses the problem, and can be merged tomorrow. As an
> > > alternative, we can revert the performance change completely [4] but I
> > want
> > > to avoid this.
> > >
> > > With the above, what would you like to do for this release? Merge the
> > fix,
> > > revert, or leave as-is?
> > >
> > > Thanks,
> > > Greg
> > >
> > > [1] https://issues.apache.org/jira/browse/KAFKA-17111
> > > [2] https://issues.apache.org/jira/browse/KAFKA-15996
> > > [3] https://github.com/apache/kafka/pull/16565
> > > [4] https://github.com/apache/kafka/pull/16568
> > >
> > > On Wed, Jul 10, 2024 at 7:37 AM Mickael Maison <
> mickael.mai...@gmail.com
> > >
> > > wrote:
> > >
> > > > Hi Dongjin,
> > > >
> > > > It's great to see you back!
> > > > I hope what we did with KIP-390 matches your expectations. Looking
> > > > forward to seeing the reboot of KIP-780.
> > > >
> > > > Thanks,
> > > > Mickael
> > > >
> > > > On Wed, Jul 10, 2024 at 4:21 PM Dongjin Lee 
> > wrote:
> > > > >
> > > > > Hi Josep,
> > > > >
> > > > > OMG, what happened while I could not be involved with the Kafka
> > > > community?
> > > > > Thanks for digging down the whole situation.
> > > > >
> > > > > @Mickael I greatly appreciate your effort in finalizing the
> feature.
> > It
> > > > > seems like I only have to re-boot the KIP-780.
> > > > >
> > > > > Thanks,
> > > > > Dongjin
> > > > >
> > > > > On Tue, Jul 9, 2024 at 12:52 AM Josep Prat
> >  > > >
> > > > > wrote:
> > > > >
> > > > > > Hi Dongjin,
> > > > > >
> > > > > > KIP-390 is part of the 3.8 release because the JIRA associated
> with
> > > it:
> > > > > > https://issues.apache.org/jira/browse/KAFKA-7632 is closed as
> > > > resolved,
> > > > > > hence the KIP is declared done and ready. I did some digging,
> and I
> > > saw
> > > > > > that Mickael was the one doing the PR that closed the JIRA
> ticket:
> > > > > > https://github.com/apache/kafka/pull/15516
> > > > > > This means that the KIP work is merged and unfortunately it is
> now
> > > > quite
> > > > > > late to perform a rollback for this feature.
> > > > > >
> > > > > > @Mickael Maison  let me know if
> > anything I
> > > > > > mentioned is not accurate (as you were the one bringing the KIP
> to
> > > > > > completion).
> > > > > >
> > > > > > Best,
> > > > > >
> > > > > > On Mon, Jul 8, 2024 at 5:38 PM Dongjin Lee 
> > > wrote:
> > > > > >
> > > > > > > Hi Josep,
> > > > > > >
> > > > > > > Thanks for managing the 3.8 release. I have a request: could
> you
> > > > please
> > > > > > > move the KIP-390 into the 3.9 release?
> > > > > > >
> > > > > > > Here is the background: KIP-390 was adopted first but hasn't
> been
> > > > > > released
> > > > > > > for a long time. After some time, I proposed KIP-780 with
> further
> > > > > > > improvements and also corrected an obvious design error
> > > > > > > (`compression.level` → `compression.(gzip|lz4|zstd). level`),
> but
> > 

Re: [DISCUSS] Apache Kafka 3.8.0 release

[Greg Harris]

Hi all,

We found a blocker in 3.8.0-rc1
https://issues.apache.org/jira/browse/KAFKA-17150 that is now merged to
trunk and backported to 3.8.
Additionally I've merged and backported the lower-severity
https://issues.apache.org/jira/browse/KAFKA-17148 to trunk, 3.8, and 3.7
because Dmitry Werner provided a very prompt fix.
Thanks to Chia-Ping, Chris, and Josep for prompt reviews. At this time I am
not aware of any more blockers for 3.8.0 and we can proceed with rc2.

Thanks!
Greg

On Wed, Jul 10, 2024 at 10:49 PM Josep Prat 
wrote:

> Hi Greg,
>
> I'll make sure the PR with the fix (
> https://github.com/apache/kafka/pull/16565) gets merged today. Thanks for
> bringing this up!
>
> Best,
>
> --
> Josep Prat
> Open Source Engineering Director, Aiven
> josep.p...@aiven.io   |   +491715557497 | aiven.io
> Aiven Deutschland GmbH
> Alexanderufer 3-7, 10117 Berlin
> Geschäftsführer: Oskari Saarenmaa & Hannu Valtonen
> Amtsgericht Charlottenburg, HRB 209739 B
>
> On Wed, Jul 10, 2024, 22:55 Greg Harris 
> wrote:
>
> > Hi Josep,
> >
> > A contributor just raised a regression [1] that I think should be
> addressed
> > in 3.8.0 prior to the release.
> >
> > Summary: This change [2] causes multiple ERROR logs to appear during
> worker
> > startup when operators install other, unrelated plugins that package the
> > Jackson library.
> > Severity: Workers will continue to operate normally and the errors will
> be
> > cosmetic. Operators and automatic systems that watch logs may roll-back
> > upgrades due to the perception of a severe problem.
> > Impact: I found 12 out of 250 third-party plugins that package the
> Jackson
> > library and trigger this error on upgrade. This will almost certainly
> > affect several users upon upgrades, and does not require obscure setups.
> > Risk: The contributor has opened a simple fix PR [3], and I have verified
> > that it addresses the problem, and can be merged tomorrow. As an
> > alternative, we can revert the performance change completely [4] but I
> want
> > to avoid this.
> >
> > With the above, what would you like to do for this release? Merge the
> fix,
> > revert, or leave as-is?
> >
> > Thanks,
> > Greg
> >
> > [1] https://issues.apache.org/jira/browse/KAFKA-17111
> > [2] https://issues.apache.org/jira/browse/KAFKA-15996
> > [3] https://github.com/apache/kafka/pull/16565
> > [4] https://github.com/apache/kafka/pull/16568
> >
> > On Wed, Jul 10, 2024 at 7:37 AM Mickael Maison  >
> > wrote:
> >
> > > Hi Dongjin,
> > >
> > > It's great to see you back!
> > > I hope what we did with KIP-390 matches your expectations. Looking
> > > forward to seeing the reboot of KIP-780.
> > >
> > > Thanks,
> > > Mickael
> > >
> > > On Wed, Jul 10, 2024 at 4:21 PM Dongjin Lee 
> wrote:
> > > >
> > > > Hi Josep,
> > > >
> > > > OMG, what happened while I could not be involved with the Kafka
> > > community?
> > > > Thanks for digging down the whole situation.
> > > >
> > > > @Mickael I greatly appreciate your effort in finalizing the feature.
> It
> > > > seems like I only have to re-boot the KIP-780.
> > > >
> > > > Thanks,
> > > > Dongjin
> > > >
> > > > On Tue, Jul 9, 2024 at 12:52 AM Josep Prat
>  > >
> > > > wrote:
> > > >
> > > > > Hi Dongjin,
> > > > >
> > > > > KIP-390 is part of the 3.8 release because the JIRA associated with
> > it:
> > > > > https://issues.apache.org/jira/browse/KAFKA-7632 is closed as
> > > resolved,
> > > > > hence the KIP is declared done and ready. I did some digging, and I
> > saw
> > > > > that Mickael was the one doing the PR that closed the JIRA ticket:
> > > > > https://github.com/apache/kafka/pull/15516
> > > > > This means that the KIP work is merged and unfortunately it is now
> > > quite
> > > > > late to perform a rollback for this feature.
> > > > >
> > > > > @Mickael Maison  let me know if
> anything I
> > > > > mentioned is not accurate (as you were the one bringing the KIP to
> > > > > completion).
> > > > >
> > > > > Best,
> > > > >
> > > > > On Mon, Jul 8, 2024 at 5:38 PM Dongjin Lee 
> > wrote:
> > > > >
> > > > > > Hi Josep,
> > > > > >
> > > > > > Thanks for managing the 3.8 release. I have a request: could you
> > > please
> > > > > > move the KIP-390 into the 3.9 release?
> > > > > >
> > > > > > Here is the background: KIP-390 was adopted first but hasn't been
> > > > > released
> > > > > > for a long time. After some time, I proposed KIP-780 with further
> > > > > > improvements and also corrected an obvious design error
> > > > > > (`compression.level` → `compression.(gzip|lz4|zstd). level`), but
> > it
> > > > > hasn't
> > > > > > been adopted due to the community's lack of response, my changing
> > > job,
> > > > > > focusing the in-house fork, etc. And last weekend, I found that
> > > KIP-380
> > > > > has
> > > > > > been included in the 3.8 release plan.
> > > > > >
> > > > > > - KIP-390:
> > > > > >
> > > > > >
> > > > >
> > >
> >
> https://cwiki.apache.org/confluence/display/KAFKA/KIP-390%3A+Support+Compression+Level
> 

Re: [DISCUSS] Apache Kafka 3.8.0 release

[Josep Prat]

Hi Greg,

I'll make sure the PR with the fix (
https://github.com/apache/kafka/pull/16565) gets merged today. Thanks for
bringing this up!

Best,

--
Josep Prat
Open Source Engineering Director, Aiven
josep.p...@aiven.io   |   +491715557497 | aiven.io
Aiven Deutschland GmbH
Alexanderufer 3-7, 10117 Berlin
Geschäftsführer: Oskari Saarenmaa & Hannu Valtonen
Amtsgericht Charlottenburg, HRB 209739 B

On Wed, Jul 10, 2024, 22:55 Greg Harris 
wrote:

> Hi Josep,
>
> A contributor just raised a regression [1] that I think should be addressed
> in 3.8.0 prior to the release.
>
> Summary: This change [2] causes multiple ERROR logs to appear during worker
> startup when operators install other, unrelated plugins that package the
> Jackson library.
> Severity: Workers will continue to operate normally and the errors will be
> cosmetic. Operators and automatic systems that watch logs may roll-back
> upgrades due to the perception of a severe problem.
> Impact: I found 12 out of 250 third-party plugins that package the Jackson
> library and trigger this error on upgrade. This will almost certainly
> affect several users upon upgrades, and does not require obscure setups.
> Risk: The contributor has opened a simple fix PR [3], and I have verified
> that it addresses the problem, and can be merged tomorrow. As an
> alternative, we can revert the performance change completely [4] but I want
> to avoid this.
>
> With the above, what would you like to do for this release? Merge the fix,
> revert, or leave as-is?
>
> Thanks,
> Greg
>
> [1] https://issues.apache.org/jira/browse/KAFKA-17111
> [2] https://issues.apache.org/jira/browse/KAFKA-15996
> [3] https://github.com/apache/kafka/pull/16565
> [4] https://github.com/apache/kafka/pull/16568
>
> On Wed, Jul 10, 2024 at 7:37 AM Mickael Maison 
> wrote:
>
> > Hi Dongjin,
> >
> > It's great to see you back!
> > I hope what we did with KIP-390 matches your expectations. Looking
> > forward to seeing the reboot of KIP-780.
> >
> > Thanks,
> > Mickael
> >
> > On Wed, Jul 10, 2024 at 4:21 PM Dongjin Lee  wrote:
> > >
> > > Hi Josep,
> > >
> > > OMG, what happened while I could not be involved with the Kafka
> > community?
> > > Thanks for digging down the whole situation.
> > >
> > > @Mickael I greatly appreciate your effort in finalizing the feature. It
> > > seems like I only have to re-boot the KIP-780.
> > >
> > > Thanks,
> > > Dongjin
> > >
> > > On Tue, Jul 9, 2024 at 12:52 AM Josep Prat  >
> > > wrote:
> > >
> > > > Hi Dongjin,
> > > >
> > > > KIP-390 is part of the 3.8 release because the JIRA associated with
> it:
> > > > https://issues.apache.org/jira/browse/KAFKA-7632 is closed as
> > resolved,
> > > > hence the KIP is declared done and ready. I did some digging, and I
> saw
> > > > that Mickael was the one doing the PR that closed the JIRA ticket:
> > > > https://github.com/apache/kafka/pull/15516
> > > > This means that the KIP work is merged and unfortunately it is now
> > quite
> > > > late to perform a rollback for this feature.
> > > >
> > > > @Mickael Maison  let me know if anything I
> > > > mentioned is not accurate (as you were the one bringing the KIP to
> > > > completion).
> > > >
> > > > Best,
> > > >
> > > > On Mon, Jul 8, 2024 at 5:38 PM Dongjin Lee 
> wrote:
> > > >
> > > > > Hi Josep,
> > > > >
> > > > > Thanks for managing the 3.8 release. I have a request: could you
> > please
> > > > > move the KIP-390 into the 3.9 release?
> > > > >
> > > > > Here is the background: KIP-390 was adopted first but hasn't been
> > > > released
> > > > > for a long time. After some time, I proposed KIP-780 with further
> > > > > improvements and also corrected an obvious design error
> > > > > (`compression.level` → `compression.(gzip|lz4|zstd). level`), but
> it
> > > > hasn't
> > > > > been adopted due to the community's lack of response, my changing
> > job,
> > > > > focusing the in-house fork, etc. And last weekend, I found that
> > KIP-380
> > > > has
> > > > > been included in the 3.8 release plan.
> > > > >
> > > > > - KIP-390:
> > > > >
> > > > >
> > > >
> >
> https://cwiki.apache.org/confluence/display/KAFKA/KIP-390%3A+Support+Compression+Level
> > > > > - KIP-780:
> > > > >
> > > > >
> > > >
> >
> https://cwiki.apache.org/confluence/display/KAFKA/KIP-780%3A+Support+fine-grained+compression+options
> > > > >
> > > > > However, shipping those two features at once has the following
> > benefits:
> > > > >
> > > > > 1. Full functionality without design error.
> > > > >
> > > > > We can provide full functionality, particularly useful with tiered
> > > > storage
> > > > > feature at once. I found that several users of tiered storage use
> > > > > server-side recompression and want to improve the compression
> > efficiency.
> > > > > Of course, it does not include any design errors :)
> > > > >
> > > > > 2. More chance of testing.
> > > > >
> > > > > Currently, I am managing an in-house fork of Apache Kafka and
> Cruise
> > > > > Control[^1], running 

Re: [DISCUSS] Apache Kafka 3.8.0 release

[Greg Harris]

Hi Josep,

A contributor just raised a regression [1] that I think should be addressed
in 3.8.0 prior to the release.

Summary: This change [2] causes multiple ERROR logs to appear during worker
startup when operators install other, unrelated plugins that package the
Jackson library.
Severity: Workers will continue to operate normally and the errors will be
cosmetic. Operators and automatic systems that watch logs may roll-back
upgrades due to the perception of a severe problem.
Impact: I found 12 out of 250 third-party plugins that package the Jackson
library and trigger this error on upgrade. This will almost certainly
affect several users upon upgrades, and does not require obscure setups.
Risk: The contributor has opened a simple fix PR [3], and I have verified
that it addresses the problem, and can be merged tomorrow. As an
alternative, we can revert the performance change completely [4] but I want
to avoid this.

With the above, what would you like to do for this release? Merge the fix,
revert, or leave as-is?

Thanks,
Greg

[1] https://issues.apache.org/jira/browse/KAFKA-17111
[2] https://issues.apache.org/jira/browse/KAFKA-15996
[3] https://github.com/apache/kafka/pull/16565
[4] https://github.com/apache/kafka/pull/16568

On Wed, Jul 10, 2024 at 7:37 AM Mickael Maison 
wrote:

> Hi Dongjin,
>
> It's great to see you back!
> I hope what we did with KIP-390 matches your expectations. Looking
> forward to seeing the reboot of KIP-780.
>
> Thanks,
> Mickael
>
> On Wed, Jul 10, 2024 at 4:21 PM Dongjin Lee  wrote:
> >
> > Hi Josep,
> >
> > OMG, what happened while I could not be involved with the Kafka
> community?
> > Thanks for digging down the whole situation.
> >
> > @Mickael I greatly appreciate your effort in finalizing the feature. It
> > seems like I only have to re-boot the KIP-780.
> >
> > Thanks,
> > Dongjin
> >
> > On Tue, Jul 9, 2024 at 12:52 AM Josep Prat 
> > wrote:
> >
> > > Hi Dongjin,
> > >
> > > KIP-390 is part of the 3.8 release because the JIRA associated with it:
> > > https://issues.apache.org/jira/browse/KAFKA-7632 is closed as
> resolved,
> > > hence the KIP is declared done and ready. I did some digging, and I saw
> > > that Mickael was the one doing the PR that closed the JIRA ticket:
> > > https://github.com/apache/kafka/pull/15516
> > > This means that the KIP work is merged and unfortunately it is now
> quite
> > > late to perform a rollback for this feature.
> > >
> > > @Mickael Maison  let me know if anything I
> > > mentioned is not accurate (as you were the one bringing the KIP to
> > > completion).
> > >
> > > Best,
> > >
> > > On Mon, Jul 8, 2024 at 5:38 PM Dongjin Lee  wrote:
> > >
> > > > Hi Josep,
> > > >
> > > > Thanks for managing the 3.8 release. I have a request: could you
> please
> > > > move the KIP-390 into the 3.9 release?
> > > >
> > > > Here is the background: KIP-390 was adopted first but hasn't been
> > > released
> > > > for a long time. After some time, I proposed KIP-780 with further
> > > > improvements and also corrected an obvious design error
> > > > (`compression.level` → `compression.(gzip|lz4|zstd). level`), but it
> > > hasn't
> > > > been adopted due to the community's lack of response, my changing
> job,
> > > > focusing the in-house fork, etc. And last weekend, I found that
> KIP-380
> > > has
> > > > been included in the 3.8 release plan.
> > > >
> > > > - KIP-390:
> > > >
> > > >
> > >
> https://cwiki.apache.org/confluence/display/KAFKA/KIP-390%3A+Support+Compression+Level
> > > > - KIP-780:
> > > >
> > > >
> > >
> https://cwiki.apache.org/confluence/display/KAFKA/KIP-780%3A+Support+fine-grained+compression+options
> > > >
> > > > However, shipping those two features at once has the following
> benefits:
> > > >
> > > > 1. Full functionality without design error.
> > > >
> > > > We can provide full functionality, particularly useful with tiered
> > > storage
> > > > feature at once. I found that several users of tiered storage use
> > > > server-side recompression and want to improve the compression
> efficiency.
> > > > Of course, it does not include any design errors :)
> > > >
> > > > 2. More chance of testing.
> > > >
> > > > Currently, I am managing an in-house fork of Apache Kafka and Cruise
> > > > Control[^1], running on thousands of clusters on k8s. With our
> ongoing
> > > work
> > > > on the tiered storage plugin, we can test both KIPs at once. Since
> we are
> > > > planning to move the terabytes of logs from thousands of
> microservices
> > > into
> > > > the object storage, some of them can be ideal testbeds.
> > > >
> > > > If you are okay, I will re-initiate the discussion of KIP-780 and
> rework
> > > > KIP-380 on the latest trunk.
> > > >
> > > > Thanks,
> > > > Dongjin
> > > >
> > > > [^1]: For example:
> https://github.com/linkedin/cruise-control/pull/2145
> > > >
> > > > On Mon, Feb 26, 2024 at 8:38 PM Josep Prat
> 
> > > > wrote:
> > > >
> > > > > Hi all,
> > > > >
> > > > > I'd like to volunteer as release manager 

Re: [DISCUSS] Apache Kafka 3.8.0 release

[Mickael Maison]

Hi Dongjin,

It's great to see you back!
I hope what we did with KIP-390 matches your expectations. Looking
forward to seeing the reboot of KIP-780.

Thanks,
Mickael

On Wed, Jul 10, 2024 at 4:21 PM Dongjin Lee  wrote:
>
> Hi Josep,
>
> OMG, what happened while I could not be involved with the Kafka community?
> Thanks for digging down the whole situation.
>
> @Mickael I greatly appreciate your effort in finalizing the feature. It
> seems like I only have to re-boot the KIP-780.
>
> Thanks,
> Dongjin
>
> On Tue, Jul 9, 2024 at 12:52 AM Josep Prat 
> wrote:
>
> > Hi Dongjin,
> >
> > KIP-390 is part of the 3.8 release because the JIRA associated with it:
> > https://issues.apache.org/jira/browse/KAFKA-7632 is closed as resolved,
> > hence the KIP is declared done and ready. I did some digging, and I saw
> > that Mickael was the one doing the PR that closed the JIRA ticket:
> > https://github.com/apache/kafka/pull/15516
> > This means that the KIP work is merged and unfortunately it is now quite
> > late to perform a rollback for this feature.
> >
> > @Mickael Maison  let me know if anything I
> > mentioned is not accurate (as you were the one bringing the KIP to
> > completion).
> >
> > Best,
> >
> > On Mon, Jul 8, 2024 at 5:38 PM Dongjin Lee  wrote:
> >
> > > Hi Josep,
> > >
> > > Thanks for managing the 3.8 release. I have a request: could you please
> > > move the KIP-390 into the 3.9 release?
> > >
> > > Here is the background: KIP-390 was adopted first but hasn't been
> > released
> > > for a long time. After some time, I proposed KIP-780 with further
> > > improvements and also corrected an obvious design error
> > > (`compression.level` → `compression.(gzip|lz4|zstd). level`), but it
> > hasn't
> > > been adopted due to the community's lack of response, my changing job,
> > > focusing the in-house fork, etc. And last weekend, I found that KIP-380
> > has
> > > been included in the 3.8 release plan.
> > >
> > > - KIP-390:
> > >
> > >
> > https://cwiki.apache.org/confluence/display/KAFKA/KIP-390%3A+Support+Compression+Level
> > > - KIP-780:
> > >
> > >
> > https://cwiki.apache.org/confluence/display/KAFKA/KIP-780%3A+Support+fine-grained+compression+options
> > >
> > > However, shipping those two features at once has the following benefits:
> > >
> > > 1. Full functionality without design error.
> > >
> > > We can provide full functionality, particularly useful with tiered
> > storage
> > > feature at once. I found that several users of tiered storage use
> > > server-side recompression and want to improve the compression efficiency.
> > > Of course, it does not include any design errors :)
> > >
> > > 2. More chance of testing.
> > >
> > > Currently, I am managing an in-house fork of Apache Kafka and Cruise
> > > Control[^1], running on thousands of clusters on k8s. With our ongoing
> > work
> > > on the tiered storage plugin, we can test both KIPs at once. Since we are
> > > planning to move the terabytes of logs from thousands of microservices
> > into
> > > the object storage, some of them can be ideal testbeds.
> > >
> > > If you are okay, I will re-initiate the discussion of KIP-780 and rework
> > > KIP-380 on the latest trunk.
> > >
> > > Thanks,
> > > Dongjin
> > >
> > > [^1]: For example: https://github.com/linkedin/cruise-control/pull/2145
> > >
> > > On Mon, Feb 26, 2024 at 8:38 PM Josep Prat 
> > > wrote:
> > >
> > > > Hi all,
> > > >
> > > > I'd like to volunteer as release manager for the Apache Kafka 3.8.0
> > > > release.
> > > > If there are no objections, I'll start building a release plan (or
> > > adapting
> > > > the one Colin made some weeks ago) in the wiki in the next days.
> > > >
> > > > Thank you.
> > > >
> > > > --
> > > > [image: Aiven] 
> > > >
> > > > *Josep Prat*
> > > > Open Source Engineering Director, *Aiven*
> > > > josep.p...@aiven.io   |   +491715557497
> > > > aiven.io    |   <
> > > https://www.facebook.com/aivencloud
> > > > >
> > > >      <
> > > > https://twitter.com/aiven_io>
> > > > *Aiven Deutschland GmbH*
> > > > Alexanderufer 3-7, 10117 Berlin
> > > > Geschäftsführer: Oskari Saarenmaa & Hannu Valtonen
> > > > Amtsgericht Charlottenburg, HRB 209739 B
> > > >
> > >
> > >
> > > --
> > > *Dongjin Lee*
> > >
> > > *A hitchhiker in the mathematical world.*
> > >
> > >
> > >
> > > *github:  github.com/dongjinleekr
> > > keybase:
> > https://keybase.io/dongjinleekr
> > > linkedin:
> > kr.linkedin.com/in/dongjinleekr
> > > speakerdeck:
> > > speakerdeck.com/dongjin
> > > *
> > >
> >
> >
> > --
> > [image: Aiven] 
> >
> > *Josep Prat*
> > Open Source Engineering Director, *Aiven*
> > josep.p...@aiven.io   |   +491715557497
> > aiven.io    |   

Re: [DISCUSS] Apache Kafka 3.8.0 release

[Dongjin Lee]

Hi Josep,

OMG, what happened while I could not be involved with the Kafka community?
Thanks for digging down the whole situation.

@Mickael I greatly appreciate your effort in finalizing the feature. It
seems like I only have to re-boot the KIP-780.

Thanks,
Dongjin

On Tue, Jul 9, 2024 at 12:52 AM Josep Prat 
wrote:

> Hi Dongjin,
>
> KIP-390 is part of the 3.8 release because the JIRA associated with it:
> https://issues.apache.org/jira/browse/KAFKA-7632 is closed as resolved,
> hence the KIP is declared done and ready. I did some digging, and I saw
> that Mickael was the one doing the PR that closed the JIRA ticket:
> https://github.com/apache/kafka/pull/15516
> This means that the KIP work is merged and unfortunately it is now quite
> late to perform a rollback for this feature.
>
> @Mickael Maison  let me know if anything I
> mentioned is not accurate (as you were the one bringing the KIP to
> completion).
>
> Best,
>
> On Mon, Jul 8, 2024 at 5:38 PM Dongjin Lee  wrote:
>
> > Hi Josep,
> >
> > Thanks for managing the 3.8 release. I have a request: could you please
> > move the KIP-390 into the 3.9 release?
> >
> > Here is the background: KIP-390 was adopted first but hasn't been
> released
> > for a long time. After some time, I proposed KIP-780 with further
> > improvements and also corrected an obvious design error
> > (`compression.level` → `compression.(gzip|lz4|zstd). level`), but it
> hasn't
> > been adopted due to the community's lack of response, my changing job,
> > focusing the in-house fork, etc. And last weekend, I found that KIP-380
> has
> > been included in the 3.8 release plan.
> >
> > - KIP-390:
> >
> >
> https://cwiki.apache.org/confluence/display/KAFKA/KIP-390%3A+Support+Compression+Level
> > - KIP-780:
> >
> >
> https://cwiki.apache.org/confluence/display/KAFKA/KIP-780%3A+Support+fine-grained+compression+options
> >
> > However, shipping those two features at once has the following benefits:
> >
> > 1. Full functionality without design error.
> >
> > We can provide full functionality, particularly useful with tiered
> storage
> > feature at once. I found that several users of tiered storage use
> > server-side recompression and want to improve the compression efficiency.
> > Of course, it does not include any design errors :)
> >
> > 2. More chance of testing.
> >
> > Currently, I am managing an in-house fork of Apache Kafka and Cruise
> > Control[^1], running on thousands of clusters on k8s. With our ongoing
> work
> > on the tiered storage plugin, we can test both KIPs at once. Since we are
> > planning to move the terabytes of logs from thousands of microservices
> into
> > the object storage, some of them can be ideal testbeds.
> >
> > If you are okay, I will re-initiate the discussion of KIP-780 and rework
> > KIP-380 on the latest trunk.
> >
> > Thanks,
> > Dongjin
> >
> > [^1]: For example: https://github.com/linkedin/cruise-control/pull/2145
> >
> > On Mon, Feb 26, 2024 at 8:38 PM Josep Prat 
> > wrote:
> >
> > > Hi all,
> > >
> > > I'd like to volunteer as release manager for the Apache Kafka 3.8.0
> > > release.
> > > If there are no objections, I'll start building a release plan (or
> > adapting
> > > the one Colin made some weeks ago) in the wiki in the next days.
> > >
> > > Thank you.
> > >
> > > --
> > > [image: Aiven] 
> > >
> > > *Josep Prat*
> > > Open Source Engineering Director, *Aiven*
> > > josep.p...@aiven.io   |   +491715557497
> > > aiven.io    |   <
> > https://www.facebook.com/aivencloud
> > > >
> > >      <
> > > https://twitter.com/aiven_io>
> > > *Aiven Deutschland GmbH*
> > > Alexanderufer 3-7, 10117 Berlin
> > > Geschäftsführer: Oskari Saarenmaa & Hannu Valtonen
> > > Amtsgericht Charlottenburg, HRB 209739 B
> > >
> >
> >
> > --
> > *Dongjin Lee*
> >
> > *A hitchhiker in the mathematical world.*
> >
> >
> >
> > *github:  github.com/dongjinleekr
> > keybase:
> https://keybase.io/dongjinleekr
> > linkedin:
> kr.linkedin.com/in/dongjinleekr
> > speakerdeck:
> > speakerdeck.com/dongjin
> > *
> >
>
>
> --
> [image: Aiven] 
>
> *Josep Prat*
> Open Source Engineering Director, *Aiven*
> josep.p...@aiven.io   |   +491715557497
> aiven.io    |    >
>      <
> https://twitter.com/aiven_io>
> *Aiven Deutschland GmbH*
> Alexanderufer 3-7, 10117 Berlin
> Geschäftsführer: Oskari Saarenmaa & Hannu Valtonen
> Amtsgericht Charlottenburg, HRB 209739 B
>


-- 
*Dongjin Lee*

*A hitchhiker in the mathematical world.*



*github:  github.com/dongjinleekr
keybase: https://keybase.io/dongjinleekr
linkedin: 

Re: [DISCUSS] Apache Kafka 3.8.0 release

[Josep Prat]

Thanks for the update,

I'm looking closely to this PR. I'll start working on the first RC shortly
after it's merged.

Best,

--
Josep Prat
Open Source Engineering Director, Aiven
josep.p...@aiven.io   |   +491715557497 | aiven.io
Aiven Deutschland GmbH
Alexanderufer 3-7, 10117 Berlin
Geschäftsführer: Oskari Saarenmaa & Hannu Valtonen
Amtsgericht Charlottenburg, HRB 209739 B

On Tue, Jul 9, 2024, 17:57 Matthias J. Sax  wrote:

> The KS system test did surface a bug. Bruno put a PR up for it, which is
> already approved.
>
> We should get it into 3.8 asap to unblock the release from our side.
>
>
> -Matthias
>
> On 7/8/24 8:51 AM, Josep Prat wrote:
> > Hi Dongjin,
> >
> > KIP-390 is part of the 3.8 release because the JIRA associated with it:
> > https://issues.apache.org/jira/browse/KAFKA-7632 is closed as resolved,
> > hence the KIP is declared done and ready. I did some digging, and I saw
> > that Mickael was the one doing the PR that closed the JIRA ticket:
> > https://github.com/apache/kafka/pull/15516
> > This means that the KIP work is merged and unfortunately it is now quite
> > late to perform a rollback for this feature.
> >
> > @Mickael Maison  let me know if anything I
> > mentioned is not accurate (as you were the one bringing the KIP to
> > completion).
> >
> > Best,
> >
> > On Mon, Jul 8, 2024 at 5:38 PM Dongjin Lee  wrote:
> >
> >> Hi Josep,
> >>
> >> Thanks for managing the 3.8 release. I have a request: could you please
> >> move the KIP-390 into the 3.9 release?
> >>
> >> Here is the background: KIP-390 was adopted first but hasn't been
> released
> >> for a long time. After some time, I proposed KIP-780 with further
> >> improvements and also corrected an obvious design error
> >> (`compression.level` → `compression.(gzip|lz4|zstd). level`), but it
> hasn't
> >> been adopted due to the community's lack of response, my changing job,
> >> focusing the in-house fork, etc. And last weekend, I found that KIP-380
> has
> >> been included in the 3.8 release plan.
> >>
> >> - KIP-390:
> >>
> >>
> https://cwiki.apache.org/confluence/display/KAFKA/KIP-390%3A+Support+Compression+Level
> >> - KIP-780:
> >>
> >>
> https://cwiki.apache.org/confluence/display/KAFKA/KIP-780%3A+Support+fine-grained+compression+options
> >>
> >> However, shipping those two features at once has the following benefits:
> >>
> >> 1. Full functionality without design error.
> >>
> >> We can provide full functionality, particularly useful with tiered
> storage
> >> feature at once. I found that several users of tiered storage use
> >> server-side recompression and want to improve the compression
> efficiency.
> >> Of course, it does not include any design errors :)
> >>
> >> 2. More chance of testing.
> >>
> >> Currently, I am managing an in-house fork of Apache Kafka and Cruise
> >> Control[^1], running on thousands of clusters on k8s. With our ongoing
> work
> >> on the tiered storage plugin, we can test both KIPs at once. Since we
> are
> >> planning to move the terabytes of logs from thousands of microservices
> into
> >> the object storage, some of them can be ideal testbeds.
> >>
> >> If you are okay, I will re-initiate the discussion of KIP-780 and rework
> >> KIP-380 on the latest trunk.
> >>
> >> Thanks,
> >> Dongjin
> >>
> >> [^1]: For example: https://github.com/linkedin/cruise-control/pull/2145
> >>
> >> On Mon, Feb 26, 2024 at 8:38 PM Josep Prat  >
> >> wrote:
> >>
> >>> Hi all,
> >>>
> >>> I'd like to volunteer as release manager for the Apache Kafka 3.8.0
> >>> release.
> >>> If there are no objections, I'll start building a release plan (or
> >> adapting
> >>> the one Colin made some weeks ago) in the wiki in the next days.
> >>>
> >>> Thank you.
> >>>
> >>> --
> >>> [image: Aiven] 
> >>>
> >>> *Josep Prat*
> >>> Open Source Engineering Director, *Aiven*
> >>> josep.p...@aiven.io   |   +491715557497
> >>> aiven.io    |   <
> >> https://www.facebook.com/aivencloud
> 
> >>>   <
> >>> https://twitter.com/aiven_io>
> >>> *Aiven Deutschland GmbH*
> >>> Alexanderufer 3-7, 10117 Berlin
> >>> Geschäftsführer: Oskari Saarenmaa & Hannu Valtonen
> >>> Amtsgericht Charlottenburg, HRB 209739 B
> >>>
> >>
> >>
> >> --
> >> *Dongjin Lee*
> >>
> >> *A hitchhiker in the mathematical world.*
> >>
> >>
> >>
> >> *github:  github.com/dongjinleekr
> >> keybase:
> https://keybase.io/dongjinleekr
> >> linkedin:
> kr.linkedin.com/in/dongjinleekr
> >> speakerdeck:
> >> speakerdeck.com/dongjin
> >> *
> >>
> >
> >
>

Re: [DISCUSS] Apache Kafka 3.8.0 release

[Matthias J. Sax]

The KS system test did surface a bug. Bruno put a PR up for it, which is 
already approved.


We should get it into 3.8 asap to unblock the release from our side.


-Matthias

On 7/8/24 8:51 AM, Josep Prat wrote:

Hi Dongjin,

KIP-390 is part of the 3.8 release because the JIRA associated with it:
https://issues.apache.org/jira/browse/KAFKA-7632 is closed as resolved,
hence the KIP is declared done and ready. I did some digging, and I saw
that Mickael was the one doing the PR that closed the JIRA ticket:
https://github.com/apache/kafka/pull/15516
This means that the KIP work is merged and unfortunately it is now quite
late to perform a rollback for this feature.

@Mickael Maison  let me know if anything I
mentioned is not accurate (as you were the one bringing the KIP to
completion).

Best,

On Mon, Jul 8, 2024 at 5:38 PM Dongjin Lee  wrote:


Hi Josep,

Thanks for managing the 3.8 release. I have a request: could you please
move the KIP-390 into the 3.9 release?

Here is the background: KIP-390 was adopted first but hasn't been released
for a long time. After some time, I proposed KIP-780 with further
improvements and also corrected an obvious design error
(`compression.level` → `compression.(gzip|lz4|zstd). level`), but it hasn't
been adopted due to the community's lack of response, my changing job,
focusing the in-house fork, etc. And last weekend, I found that KIP-380 has
been included in the 3.8 release plan.

- KIP-390:

https://cwiki.apache.org/confluence/display/KAFKA/KIP-390%3A+Support+Compression+Level
- KIP-780:

https://cwiki.apache.org/confluence/display/KAFKA/KIP-780%3A+Support+fine-grained+compression+options

However, shipping those two features at once has the following benefits:

1. Full functionality without design error.

We can provide full functionality, particularly useful with tiered storage
feature at once. I found that several users of tiered storage use
server-side recompression and want to improve the compression efficiency.
Of course, it does not include any design errors :)

2. More chance of testing.

Currently, I am managing an in-house fork of Apache Kafka and Cruise
Control[^1], running on thousands of clusters on k8s. With our ongoing work
on the tiered storage plugin, we can test both KIPs at once. Since we are
planning to move the terabytes of logs from thousands of microservices into
the object storage, some of them can be ideal testbeds.

If you are okay, I will re-initiate the discussion of KIP-780 and rework
KIP-380 on the latest trunk.

Thanks,
Dongjin

[^1]: For example: https://github.com/linkedin/cruise-control/pull/2145

On Mon, Feb 26, 2024 at 8:38 PM Josep Prat 
wrote:


Hi all,

I'd like to volunteer as release manager for the Apache Kafka 3.8.0
release.
If there are no objections, I'll start building a release plan (or

adapting

the one Colin made some weeks ago) in the wiki in the next days.

Thank you.

--
[image: Aiven] 

*Josep Prat*
Open Source Engineering Director, *Aiven*
josep.p...@aiven.io   |   +491715557497
aiven.io    |   <

https://www.facebook.com/aivencloud



      <
https://twitter.com/aiven_io>
*Aiven Deutschland GmbH*
Alexanderufer 3-7, 10117 Berlin
Geschäftsführer: Oskari Saarenmaa & Hannu Valtonen
Amtsgericht Charlottenburg, HRB 209739 B




--
*Dongjin Lee*

*A hitchhiker in the mathematical world.*



*github:  github.com/dongjinleekr
keybase: https://keybase.io/dongjinleekr
linkedin: kr.linkedin.com/in/dongjinleekr
speakerdeck:
speakerdeck.com/dongjin
*

Re: [DISCUSS] Apache Kafka 3.8.0 release

[Josep Prat]

Hi Dongjin,

KIP-390 is part of the 3.8 release because the JIRA associated with it:
https://issues.apache.org/jira/browse/KAFKA-7632 is closed as resolved,
hence the KIP is declared done and ready. I did some digging, and I saw
that Mickael was the one doing the PR that closed the JIRA ticket:
https://github.com/apache/kafka/pull/15516
This means that the KIP work is merged and unfortunately it is now quite
late to perform a rollback for this feature.

@Mickael Maison  let me know if anything I
mentioned is not accurate (as you were the one bringing the KIP to
completion).

Best,

On Mon, Jul 8, 2024 at 5:38 PM Dongjin Lee  wrote:

> Hi Josep,
>
> Thanks for managing the 3.8 release. I have a request: could you please
> move the KIP-390 into the 3.9 release?
>
> Here is the background: KIP-390 was adopted first but hasn't been released
> for a long time. After some time, I proposed KIP-780 with further
> improvements and also corrected an obvious design error
> (`compression.level` → `compression.(gzip|lz4|zstd). level`), but it hasn't
> been adopted due to the community's lack of response, my changing job,
> focusing the in-house fork, etc. And last weekend, I found that KIP-380 has
> been included in the 3.8 release plan.
>
> - KIP-390:
>
> https://cwiki.apache.org/confluence/display/KAFKA/KIP-390%3A+Support+Compression+Level
> - KIP-780:
>
> https://cwiki.apache.org/confluence/display/KAFKA/KIP-780%3A+Support+fine-grained+compression+options
>
> However, shipping those two features at once has the following benefits:
>
> 1. Full functionality without design error.
>
> We can provide full functionality, particularly useful with tiered storage
> feature at once. I found that several users of tiered storage use
> server-side recompression and want to improve the compression efficiency.
> Of course, it does not include any design errors :)
>
> 2. More chance of testing.
>
> Currently, I am managing an in-house fork of Apache Kafka and Cruise
> Control[^1], running on thousands of clusters on k8s. With our ongoing work
> on the tiered storage plugin, we can test both KIPs at once. Since we are
> planning to move the terabytes of logs from thousands of microservices into
> the object storage, some of them can be ideal testbeds.
>
> If you are okay, I will re-initiate the discussion of KIP-780 and rework
> KIP-380 on the latest trunk.
>
> Thanks,
> Dongjin
>
> [^1]: For example: https://github.com/linkedin/cruise-control/pull/2145
>
> On Mon, Feb 26, 2024 at 8:38 PM Josep Prat 
> wrote:
>
> > Hi all,
> >
> > I'd like to volunteer as release manager for the Apache Kafka 3.8.0
> > release.
> > If there are no objections, I'll start building a release plan (or
> adapting
> > the one Colin made some weeks ago) in the wiki in the next days.
> >
> > Thank you.
> >
> > --
> > [image: Aiven] 
> >
> > *Josep Prat*
> > Open Source Engineering Director, *Aiven*
> > josep.p...@aiven.io   |   +491715557497
> > aiven.io    |   <
> https://www.facebook.com/aivencloud
> > >
> >      <
> > https://twitter.com/aiven_io>
> > *Aiven Deutschland GmbH*
> > Alexanderufer 3-7, 10117 Berlin
> > Geschäftsführer: Oskari Saarenmaa & Hannu Valtonen
> > Amtsgericht Charlottenburg, HRB 209739 B
> >
>
>
> --
> *Dongjin Lee*
>
> *A hitchhiker in the mathematical world.*
>
>
>
> *github:  github.com/dongjinleekr
> keybase: https://keybase.io/dongjinleekr
> linkedin: kr.linkedin.com/in/dongjinleekr
> speakerdeck:
> speakerdeck.com/dongjin
> *
>


-- 
[image: Aiven] 

*Josep Prat*
Open Source Engineering Director, *Aiven*
josep.p...@aiven.io   |   +491715557497
aiven.io    |   
     
*Aiven Deutschland GmbH*
Alexanderufer 3-7, 10117 Berlin
Geschäftsführer: Oskari Saarenmaa & Hannu Valtonen
Amtsgericht Charlottenburg, HRB 209739 B

Re: [DISCUSS] Apache Kafka 3.8.0 release

[Dongjin Lee]

Hi Josep,

Thanks for managing the 3.8 release. I have a request: could you please
move the KIP-390 into the 3.9 release?

Here is the background: KIP-390 was adopted first but hasn't been released
for a long time. After some time, I proposed KIP-780 with further
improvements and also corrected an obvious design error
(`compression.level` → `compression.(gzip|lz4|zstd). level`), but it hasn't
been adopted due to the community's lack of response, my changing job,
focusing the in-house fork, etc. And last weekend, I found that KIP-380 has
been included in the 3.8 release plan.

- KIP-390:
https://cwiki.apache.org/confluence/display/KAFKA/KIP-390%3A+Support+Compression+Level
- KIP-780:
https://cwiki.apache.org/confluence/display/KAFKA/KIP-780%3A+Support+fine-grained+compression+options

However, shipping those two features at once has the following benefits:

1. Full functionality without design error.

We can provide full functionality, particularly useful with tiered storage
feature at once. I found that several users of tiered storage use
server-side recompression and want to improve the compression efficiency.
Of course, it does not include any design errors :)

2. More chance of testing.

Currently, I am managing an in-house fork of Apache Kafka and Cruise
Control[^1], running on thousands of clusters on k8s. With our ongoing work
on the tiered storage plugin, we can test both KIPs at once. Since we are
planning to move the terabytes of logs from thousands of microservices into
the object storage, some of them can be ideal testbeds.

If you are okay, I will re-initiate the discussion of KIP-780 and rework
KIP-380 on the latest trunk.

Thanks,
Dongjin

[^1]: For example: https://github.com/linkedin/cruise-control/pull/2145

On Mon, Feb 26, 2024 at 8:38 PM Josep Prat 
wrote:

> Hi all,
>
> I'd like to volunteer as release manager for the Apache Kafka 3.8.0
> release.
> If there are no objections, I'll start building a release plan (or adapting
> the one Colin made some weeks ago) in the wiki in the next days.
>
> Thank you.
>
> --
> [image: Aiven] 
>
> *Josep Prat*
> Open Source Engineering Director, *Aiven*
> josep.p...@aiven.io   |   +491715557497
> aiven.io    |    >
>      <
> https://twitter.com/aiven_io>
> *Aiven Deutschland GmbH*
> Alexanderufer 3-7, 10117 Berlin
> Geschäftsführer: Oskari Saarenmaa & Hannu Valtonen
> Amtsgericht Charlottenburg, HRB 209739 B
>


-- 
*Dongjin Lee*

*A hitchhiker in the mathematical world.*



*github:  github.com/dongjinleekr
keybase: https://keybase.io/dongjinleekr
linkedin: kr.linkedin.com/in/dongjinleekr
speakerdeck: speakerdeck.com/dongjin
*

Re: [DISCUSS] Apache Kafka 3.8.0 release

[Josep Prat]

Hi Bruno,

I'd be in for merging the fix into 3.8. Given the solution is already found
and it seems easy enough to reason and with very limited scope, I believe
it is fairly safe to merge this one. Let's work towards merging the fix and
see if the system tests improve and await for your soak testing.


Best,


On Mon, Jul 8, 2024 at 9:39 AM Bruno Cadonna  wrote:

> Hi Josep,
>
> we found a bug in Streams. The bug is in the state updater that we
> enabled by default for 3.8.
>
> I have already created a fix for it:
> https://github.com/apache/kafka/pull/16545
>
> As you can see the fix is small and limited to a location in the code,
> so I do not think that it is risky.
>
> The bug is not strictly a regression since the state updater was
> disabled in previous releases. However, for this release we soaked
> mainly with state updater enabled. So we need to soak Streams for a bit
> (couple of days? one week?) with state updater disabled to be confident
> that disabling does not introduce a real regression since the two code
> paths are interleaved.
>
> Reverting the PRs of the state updater is not an option since they are
> many and they were merged over quite some time which makes reverts at
> least very risky and work intensive. Reverting would delay the release
> for sure.
>
> In addition to the fix, I also opened a PR to disable the state updater:
> https://github.com/apache/kafka/pull/16542
>
> I have already started soak testing for both PRs.
>
> We did not find this bug before, because it manifests in a specific
> situation that occurs rather seldomly even in our soak where we inject
> various errors and infrastructure events.
>
> The state updater is a long awaited improvement that besides other
> improvements solves a long-standing timeout issue with exactly-once
> processing: https://issues.apache.org/jira/browse/KAFKA-13295
>
> Let me know, whether you prefer to disable the state updater or whether
> I should merge the fix into 3.8.
>
> Best,
> Bruno
>
> On 7/5/24 12:01 PM, Josep Prat wrote:
> > Hi all,
> > Unfortunately, after 4 runs of the systems tests, we still can't have a
> > combined run with no errors. I created the JIRAs linked below to track
> > these.
> > I would think these are blockers for the release, but I'd be extremely
> > happy to be corrected!
> >
> > KRaft Upgrade Failures:
> https://issues.apache.org/jira/browse/KAFKA-17083
> > Network Degrade Failures:
> https://issues.apache.org/jira/browse/KAFKA-17084
> > Streams Cooperative Rebalance Upgrade Failures
> > https://issues.apache.org/jira/browse/KAFKA-17085.
> > These system tests above fail consistently on CI and on my machine. If
> > anyone has the means to run system tests and can make these pass, please
> > let me know.
> >
> > These add up to the existing
> > https://issues.apache.org/jira/browse/KAFKA-16138 (discovered during
> 3.7)
> > for the Quota test failures that can pass locally.
> >
> > The status of the test runs as well as the logs of the runs can be found
> > here:
> >
> https://docs.google.com/document/d/1wbcyzO6GM2SYQaqTMITBTBjHgZgM7mmiAt7TUfh1xt8/edit
> >
> > Best,
> >
> > On Thu, Jul 4, 2024 at 3:27 PM Josep Prat  wrote:
> >
> >> Thanks Luke!
> >>
> >> --
> >> Josep Prat
> >> Open Source Engineering Director, Aiven
> >> josep.p...@aiven.io   |   +491715557497 | aiven.io
> >> Aiven Deutschland GmbH
> >> Alexanderufer 3-7, 10117 Berlin
> >> Geschäftsführer: Oskari Saarenmaa & Hannu Valtonen
> >> Amtsgericht Charlottenburg, HRB 209739 B
> >>
> >> On Thu, Jul 4, 2024, 14:04 Luke Chen  wrote:
> >>
> >>> Hi Josep,
> >>>
> >>> I had run tests for tests/kafkatest/tests/client/quota_test.py based on
> >>> 3.8
> >>> branch, and they all passed.
> >>>
> >>> *19:54:24*
> >>>
> *19:54:24*
> >>>   SESSION REPORT (ALL TESTS)*19:54:24*  ducktape version:
> >>> 0.11.4*19:54:24*  session_id:   2024-07-04--001*19:54:24*  run
> >>> time: 12 minutes 39.940 seconds*19:54:24*  tests run:
> >>> 9*19:54:24*  passed:   9*19:54:24*  flaky:
> >>> 0*19:54:24*  failed:   0*19:54:24*  ignored:
> >>> 0*19:54:24*
> >>>
> *19:54:24*
> >>>   test_id:
> >>>
> kafkatest.tests.client.quota_test.QuotaTest.test_quota.quota_type=client-id.consumer_num=2*19:54:24*
> >>>   status: PASS*19:54:24*  run time:   3 minutes 51.280
> >>> seconds*19:54:24*
> >>>
> >>>
> *19:54:24*
> >>>   test_id:
> >>>
> kafkatest.tests.client.quota_test.QuotaTest.test_quota.quota_type=.user.client-id.override_quota=True*19:54:24*
> >>>   status: PASS*19:54:24*  run time:   4 minutes 21.082
> >>> seconds*19:54:24*
> >>>
> >>>
> *19:54:24*
> >>>   test_id:
> >>>
> 

Re: [DISCUSS] Apache Kafka 3.8.0 release

[Bruno Cadonna]

Hi Josep,

we found a bug in Streams. The bug is in the state updater that we 
enabled by default for 3.8.


I have already created a fix for it: 
https://github.com/apache/kafka/pull/16545


As you can see the fix is small and limited to a location in the code, 
so I do not think that it is risky.


The bug is not strictly a regression since the state updater was 
disabled in previous releases. However, for this release we soaked 
mainly with state updater enabled. So we need to soak Streams for a bit 
(couple of days? one week?) with state updater disabled to be confident 
that disabling does not introduce a real regression since the two code 
paths are interleaved.


Reverting the PRs of the state updater is not an option since they are 
many and they were merged over quite some time which makes reverts at 
least very risky and work intensive. Reverting would delay the release 
for sure.


In addition to the fix, I also opened a PR to disable the state updater: 
https://github.com/apache/kafka/pull/16542


I have already started soak testing for both PRs.

We did not find this bug before, because it manifests in a specific 
situation that occurs rather seldomly even in our soak where we inject 
various errors and infrastructure events.


The state updater is a long awaited improvement that besides other 
improvements solves a long-standing timeout issue with exactly-once 
processing: https://issues.apache.org/jira/browse/KAFKA-13295


Let me know, whether you prefer to disable the state updater or whether 
I should merge the fix into 3.8.


Best,
Bruno

On 7/5/24 12:01 PM, Josep Prat wrote:

Hi all,
Unfortunately, after 4 runs of the systems tests, we still can't have a
combined run with no errors. I created the JIRAs linked below to track
these.
I would think these are blockers for the release, but I'd be extremely
happy to be corrected!

KRaft Upgrade Failures: https://issues.apache.org/jira/browse/KAFKA-17083
Network Degrade Failures: https://issues.apache.org/jira/browse/KAFKA-17084
Streams Cooperative Rebalance Upgrade Failures
https://issues.apache.org/jira/browse/KAFKA-17085.
These system tests above fail consistently on CI and on my machine. If
anyone has the means to run system tests and can make these pass, please
let me know.

These add up to the existing
https://issues.apache.org/jira/browse/KAFKA-16138 (discovered during 3.7)
for the Quota test failures that can pass locally.

The status of the test runs as well as the logs of the runs can be found
here:
https://docs.google.com/document/d/1wbcyzO6GM2SYQaqTMITBTBjHgZgM7mmiAt7TUfh1xt8/edit

Best,

On Thu, Jul 4, 2024 at 3:27 PM Josep Prat  wrote:


Thanks Luke!

--
Josep Prat
Open Source Engineering Director, Aiven
josep.p...@aiven.io   |   +491715557497 | aiven.io
Aiven Deutschland GmbH
Alexanderufer 3-7, 10117 Berlin
Geschäftsführer: Oskari Saarenmaa & Hannu Valtonen
Amtsgericht Charlottenburg, HRB 209739 B

On Thu, Jul 4, 2024, 14:04 Luke Chen  wrote:


Hi Josep,

I had run tests for tests/kafkatest/tests/client/quota_test.py based on
3.8
branch, and they all passed.

*19:54:24*
*19:54:24*
  SESSION REPORT (ALL TESTS)*19:54:24*  ducktape version:
0.11.4*19:54:24*  session_id:   2024-07-04--001*19:54:24*  run
time: 12 minutes 39.940 seconds*19:54:24*  tests run:
9*19:54:24*  passed:   9*19:54:24*  flaky:
0*19:54:24*  failed:   0*19:54:24*  ignored:
0*19:54:24*
*19:54:24*
  test_id:
kafkatest.tests.client.quota_test.QuotaTest.test_quota.quota_type=client-id.consumer_num=2*19:54:24*
  status: PASS*19:54:24*  run time:   3 minutes 51.280
seconds*19:54:24*

*19:54:24*
  test_id:
kafkatest.tests.client.quota_test.QuotaTest.test_quota.quota_type=.user.client-id.override_quota=True*19:54:24*
  status: PASS*19:54:24*  run time:   4 minutes 21.082
seconds*19:54:24*

*19:54:24*
  test_id:
kafkatest.tests.client.quota_test.QuotaTest.test_quota.quota_type=.user.client-id.override_quota=False*19:54:24*
  status: PASS*19:54:24*  run time:   5 minutes 14.854
seconds*19:54:24*

*19:54:24*
  test_id:
kafkatest.tests.client.quota_test.QuotaTest.test_quota.quota_type=client-id.old_broker_throttling_behavior=True*19:54:24*
  status: PASS*19:54:24*  run time:   3 minutes 0.505
seconds*19:54:24*

*19:54:24*
  test_id:
kafkatest.tests.client.quota_test.QuotaTest.test_quota.quota_type=client-id.old_client_throttling_behavior=True*19:54:24*
  status: PASS*19:54:24*  run time:   3 minutes 19.629
seconds*19:54:24*

Re: [DISCUSS] Apache Kafka 3.8.0 release

[Josep Prat]

Hi all,
Unfortunately, after 4 runs of the systems tests, we still can't have a
combined run with no errors. I created the JIRAs linked below to track
these.
I would think these are blockers for the release, but I'd be extremely
happy to be corrected!

KRaft Upgrade Failures: https://issues.apache.org/jira/browse/KAFKA-17083
Network Degrade Failures: https://issues.apache.org/jira/browse/KAFKA-17084
Streams Cooperative Rebalance Upgrade Failures
https://issues.apache.org/jira/browse/KAFKA-17085.
These system tests above fail consistently on CI and on my machine. If
anyone has the means to run system tests and can make these pass, please
let me know.

These add up to the existing
https://issues.apache.org/jira/browse/KAFKA-16138 (discovered during 3.7)
for the Quota test failures that can pass locally.

The status of the test runs as well as the logs of the runs can be found
here:
https://docs.google.com/document/d/1wbcyzO6GM2SYQaqTMITBTBjHgZgM7mmiAt7TUfh1xt8/edit

Best,

On Thu, Jul 4, 2024 at 3:27 PM Josep Prat  wrote:

> Thanks Luke!
>
> --
> Josep Prat
> Open Source Engineering Director, Aiven
> josep.p...@aiven.io   |   +491715557497 | aiven.io
> Aiven Deutschland GmbH
> Alexanderufer 3-7, 10117 Berlin
> Geschäftsführer: Oskari Saarenmaa & Hannu Valtonen
> Amtsgericht Charlottenburg, HRB 209739 B
>
> On Thu, Jul 4, 2024, 14:04 Luke Chen  wrote:
>
>> Hi Josep,
>>
>> I had run tests for tests/kafkatest/tests/client/quota_test.py based on
>> 3.8
>> branch, and they all passed.
>>
>> *19:54:24*
>> *19:54:24*
>>  SESSION REPORT (ALL TESTS)*19:54:24*  ducktape version:
>> 0.11.4*19:54:24*  session_id:   2024-07-04--001*19:54:24*  run
>> time: 12 minutes 39.940 seconds*19:54:24*  tests run:
>> 9*19:54:24*  passed:   9*19:54:24*  flaky:
>> 0*19:54:24*  failed:   0*19:54:24*  ignored:
>> 0*19:54:24*
>> *19:54:24*
>>  test_id:
>> kafkatest.tests.client.quota_test.QuotaTest.test_quota.quota_type=client-id.consumer_num=2*19:54:24*
>>  status: PASS*19:54:24*  run time:   3 minutes 51.280
>> seconds*19:54:24*
>>
>> *19:54:24*
>>  test_id:
>> kafkatest.tests.client.quota_test.QuotaTest.test_quota.quota_type=.user.client-id.override_quota=True*19:54:24*
>>  status: PASS*19:54:24*  run time:   4 minutes 21.082
>> seconds*19:54:24*
>>
>> *19:54:24*
>>  test_id:
>> kafkatest.tests.client.quota_test.QuotaTest.test_quota.quota_type=.user.client-id.override_quota=False*19:54:24*
>>  status: PASS*19:54:24*  run time:   5 minutes 14.854
>> seconds*19:54:24*
>>
>> *19:54:24*
>>  test_id:
>> kafkatest.tests.client.quota_test.QuotaTest.test_quota.quota_type=client-id.old_broker_throttling_behavior=True*19:54:24*
>>  status: PASS*19:54:24*  run time:   3 minutes 0.505
>> seconds*19:54:24*
>>
>> *19:54:24*
>>  test_id:
>> kafkatest.tests.client.quota_test.QuotaTest.test_quota.quota_type=client-id.old_client_throttling_behavior=True*19:54:24*
>>  status: PASS*19:54:24*  run time:   3 minutes 19.629
>> seconds*19:54:24*
>>
>> *19:54:24*
>>  test_id:
>> kafkatest.tests.client.quota_test.QuotaTest.test_quota.quota_type=client-id.override_quota=False*19:54:24*
>>  status: PASS*19:54:24*  run time:   4 minutes 11.296
>> seconds*19:54:24*
>>
>> *19:54:24*
>>  test_id:
>> kafkatest.tests.client.quota_test.QuotaTest.test_quota.quota_type=client-id.override_quota=True*19:54:24*
>>  status: PASS*19:54:24*  run time:   4 minutes 10.578
>> seconds*19:54:24*
>>
>> *19:54:24*
>>  test_id:
>> kafkatest.tests.client.quota_test.QuotaTest.test_quota.quota_type=user.override_quota=False*19:54:24*
>>  status: PASS*19:54:24*  run time:   4 minutes 19.187
>> seconds*19:54:24*
>>
>> *19:54:24*
>>  test_id:
>> kafkatest.tests.client.quota_test.QuotaTest.test_quota.quota_type=user.override_quota=True*19:54:24*
>>  status: PASS*19:54:24*  run time:   3 minutes 13.666
>> seconds*19:54:24*
>>
>> 
>>
>>
>> Thanks.
>> Luke
>>
>> On Thu, Jul 4, 2024 at 6:01 PM Josep Prat 
>> wrote:
>>
>> > Hi Luke,
>> >
>> > Thanks for the pointer, if you have an environment where you can run the
>> > tests I would highly appreciate it!

Re: [DISCUSS] Apache Kafka 3.8.0 release

[Josep Prat]

Thanks Luke!

--
Josep Prat
Open Source Engineering Director, Aiven
josep.p...@aiven.io   |   +491715557497 | aiven.io
Aiven Deutschland GmbH
Alexanderufer 3-7, 10117 Berlin
Geschäftsführer: Oskari Saarenmaa & Hannu Valtonen
Amtsgericht Charlottenburg, HRB 209739 B

On Thu, Jul 4, 2024, 14:04 Luke Chen  wrote:

> Hi Josep,
>
> I had run tests for tests/kafkatest/tests/client/quota_test.py based on 3.8
> branch, and they all passed.
>
> *19:54:24*
> *19:54:24*
>  SESSION REPORT (ALL TESTS)*19:54:24*  ducktape version:
> 0.11.4*19:54:24*  session_id:   2024-07-04--001*19:54:24*  run
> time: 12 minutes 39.940 seconds*19:54:24*  tests run:
> 9*19:54:24*  passed:   9*19:54:24*  flaky:
> 0*19:54:24*  failed:   0*19:54:24*  ignored:
> 0*19:54:24*
> *19:54:24*
>  test_id:
> kafkatest.tests.client.quota_test.QuotaTest.test_quota.quota_type=client-id.consumer_num=2*19:54:24*
>  status: PASS*19:54:24*  run time:   3 minutes 51.280
> seconds*19:54:24*
>
> *19:54:24*
>  test_id:
> kafkatest.tests.client.quota_test.QuotaTest.test_quota.quota_type=.user.client-id.override_quota=True*19:54:24*
>  status: PASS*19:54:24*  run time:   4 minutes 21.082
> seconds*19:54:24*
>
> *19:54:24*
>  test_id:
> kafkatest.tests.client.quota_test.QuotaTest.test_quota.quota_type=.user.client-id.override_quota=False*19:54:24*
>  status: PASS*19:54:24*  run time:   5 minutes 14.854
> seconds*19:54:24*
>
> *19:54:24*
>  test_id:
> kafkatest.tests.client.quota_test.QuotaTest.test_quota.quota_type=client-id.old_broker_throttling_behavior=True*19:54:24*
>  status: PASS*19:54:24*  run time:   3 minutes 0.505
> seconds*19:54:24*
>
> *19:54:24*
>  test_id:
> kafkatest.tests.client.quota_test.QuotaTest.test_quota.quota_type=client-id.old_client_throttling_behavior=True*19:54:24*
>  status: PASS*19:54:24*  run time:   3 minutes 19.629
> seconds*19:54:24*
>
> *19:54:24*
>  test_id:
> kafkatest.tests.client.quota_test.QuotaTest.test_quota.quota_type=client-id.override_quota=False*19:54:24*
>  status: PASS*19:54:24*  run time:   4 minutes 11.296
> seconds*19:54:24*
>
> *19:54:24*
>  test_id:
> kafkatest.tests.client.quota_test.QuotaTest.test_quota.quota_type=client-id.override_quota=True*19:54:24*
>  status: PASS*19:54:24*  run time:   4 minutes 10.578
> seconds*19:54:24*
>
> *19:54:24*
>  test_id:
> kafkatest.tests.client.quota_test.QuotaTest.test_quota.quota_type=user.override_quota=False*19:54:24*
>  status: PASS*19:54:24*  run time:   4 minutes 19.187
> seconds*19:54:24*
>
> *19:54:24*
>  test_id:
> kafkatest.tests.client.quota_test.QuotaTest.test_quota.quota_type=user.override_quota=True*19:54:24*
>  status: PASS*19:54:24*  run time:   3 minutes 13.666
> seconds*19:54:24*
>
> 
>
>
> Thanks.
> Luke
>
> On Thu, Jul 4, 2024 at 6:01 PM Josep Prat 
> wrote:
>
> > Hi Luke,
> >
> > Thanks for the pointer, if you have an environment where you can run the
> > tests I would highly appreciate it!
> >
> > I managed to run this test suite locally and currently only this one
> fails
> > consistently, the rest pass:
> >
> > Module: kafkatest.tests.client.quota_test
> > Class:  QuotaTest
> > Method: test_quota
> > Arguments:
> > {
> >   "old_client_throttling_behavior": true,
> >   "quota_type": "client-id"
> > }
> >
> > Failure:
> > TimeoutError("Timed out waiting 600 seconds for service nodes to
> > finish. These nodes are still alive:
> > ['ProducerPerformanceService-0-140496695824336 node 1 on worker3']")
> > Traceback (most recent call last):
> >   File
> >
> "/home/jlprat/projects/kafka/tests/venv39/lib64/python3.9/site-packages/ducktape-0.8.14-py3.9.egg/ducktape/tests/runner_client.py",
> > line 184, in _do_run
> > data = self.run_test()
> >   File
> >
> "/home/jlprat/projects/kafka/tests/venv39/lib64/python3.9/site-packages/ducktape-0.8.14-py3.9.egg/ducktape/tests/runner_client.py",
> > line 262, in run_test
> > return self.test_context.function(self.test)
> >   File
> >
> "/home/jlprat/projects/kafka/tests/venv39/lib64/python3.9/site-packages/ducktape-0.8.14-py3.9.egg/ducktape/mark/_mark.py",
> > line 

Re: [DISCUSS] Apache Kafka 3.8.0 release

[Luke Chen]

Hi Josep,

I had run tests for tests/kafkatest/tests/client/quota_test.py based on 3.8
branch, and they all passed.

*19:54:24*  
*19:54:24*
 SESSION REPORT (ALL TESTS)*19:54:24*  ducktape version:
0.11.4*19:54:24*  session_id:   2024-07-04--001*19:54:24*  run
time: 12 minutes 39.940 seconds*19:54:24*  tests run:
9*19:54:24*  passed:   9*19:54:24*  flaky:
0*19:54:24*  failed:   0*19:54:24*  ignored:
0*19:54:24*  
*19:54:24*
 test_id:
kafkatest.tests.client.quota_test.QuotaTest.test_quota.quota_type=client-id.consumer_num=2*19:54:24*
 status: PASS*19:54:24*  run time:   3 minutes 51.280
seconds*19:54:24*
*19:54:24*
 test_id:
kafkatest.tests.client.quota_test.QuotaTest.test_quota.quota_type=.user.client-id.override_quota=True*19:54:24*
 status: PASS*19:54:24*  run time:   4 minutes 21.082
seconds*19:54:24*
*19:54:24*
 test_id:
kafkatest.tests.client.quota_test.QuotaTest.test_quota.quota_type=.user.client-id.override_quota=False*19:54:24*
 status: PASS*19:54:24*  run time:   5 minutes 14.854
seconds*19:54:24*
*19:54:24*
 test_id:
kafkatest.tests.client.quota_test.QuotaTest.test_quota.quota_type=client-id.old_broker_throttling_behavior=True*19:54:24*
 status: PASS*19:54:24*  run time:   3 minutes 0.505
seconds*19:54:24*
*19:54:24*
 test_id:
kafkatest.tests.client.quota_test.QuotaTest.test_quota.quota_type=client-id.old_client_throttling_behavior=True*19:54:24*
 status: PASS*19:54:24*  run time:   3 minutes 19.629
seconds*19:54:24*
*19:54:24*
 test_id:
kafkatest.tests.client.quota_test.QuotaTest.test_quota.quota_type=client-id.override_quota=False*19:54:24*
 status: PASS*19:54:24*  run time:   4 minutes 11.296
seconds*19:54:24*
*19:54:24*
 test_id:
kafkatest.tests.client.quota_test.QuotaTest.test_quota.quota_type=client-id.override_quota=True*19:54:24*
 status: PASS*19:54:24*  run time:   4 minutes 10.578
seconds*19:54:24*
*19:54:24*
 test_id:
kafkatest.tests.client.quota_test.QuotaTest.test_quota.quota_type=user.override_quota=False*19:54:24*
 status: PASS*19:54:24*  run time:   4 minutes 19.187
seconds*19:54:24*
*19:54:24*
 test_id:
kafkatest.tests.client.quota_test.QuotaTest.test_quota.quota_type=user.override_quota=True*19:54:24*
 status: PASS*19:54:24*  run time:   3 minutes 13.666
seconds*19:54:24*



Thanks.
Luke

On Thu, Jul 4, 2024 at 6:01 PM Josep Prat 
wrote:

> Hi Luke,
>
> Thanks for the pointer, if you have an environment where you can run the
> tests I would highly appreciate it!
>
> I managed to run this test suite locally and currently only this one fails
> consistently, the rest pass:
>
> Module: kafkatest.tests.client.quota_test
> Class:  QuotaTest
> Method: test_quota
> Arguments:
> {
>   "old_client_throttling_behavior": true,
>   "quota_type": "client-id"
> }
>
> Failure:
> TimeoutError("Timed out waiting 600 seconds for service nodes to
> finish. These nodes are still alive:
> ['ProducerPerformanceService-0-140496695824336 node 1 on worker3']")
> Traceback (most recent call last):
>   File
> "/home/jlprat/projects/kafka/tests/venv39/lib64/python3.9/site-packages/ducktape-0.8.14-py3.9.egg/ducktape/tests/runner_client.py",
> line 184, in _do_run
> data = self.run_test()
>   File
> "/home/jlprat/projects/kafka/tests/venv39/lib64/python3.9/site-packages/ducktape-0.8.14-py3.9.egg/ducktape/tests/runner_client.py",
> line 262, in run_test
> return self.test_context.function(self.test)
>   File
> "/home/jlprat/projects/kafka/tests/venv39/lib64/python3.9/site-packages/ducktape-0.8.14-py3.9.egg/ducktape/mark/_mark.py",
> line 433, in wrapper
> return functools.partial(f, *args, **kwargs)(*w_args, **w_kwargs)
>   File
> "/home/jlprat/projects/kafka/tests/kafkatest/tests/client/quota_test.py",
> line 157, in test_quota
> producer.run()
>   File
> "/home/jlprat/projects/kafka/tests/venv39/lib64/python3.9/site-packages/ducktape-0.8.14-py3.9.egg/ducktape/services/service.py",
> line 345, in run
> self.wait()
>   File
> 

Re: [DISCUSS] Apache Kafka 3.8.0 release

[Josep Prat]

Hi Luke,

Thanks for the pointer, if you have an environment where you can run the
tests I would highly appreciate it!

I managed to run this test suite locally and currently only this one fails
consistently, the rest pass:

Module: kafkatest.tests.client.quota_test
Class:  QuotaTest
Method: test_quota
Arguments:
{
  "old_client_throttling_behavior": true,
  "quota_type": "client-id"
}

Failure:
TimeoutError("Timed out waiting 600 seconds for service nodes to
finish. These nodes are still alive:
['ProducerPerformanceService-0-140496695824336 node 1 on worker3']")
Traceback (most recent call last):
  File 
"/home/jlprat/projects/kafka/tests/venv39/lib64/python3.9/site-packages/ducktape-0.8.14-py3.9.egg/ducktape/tests/runner_client.py",
line 184, in _do_run
data = self.run_test()
  File 
"/home/jlprat/projects/kafka/tests/venv39/lib64/python3.9/site-packages/ducktape-0.8.14-py3.9.egg/ducktape/tests/runner_client.py",
line 262, in run_test
return self.test_context.function(self.test)
  File 
"/home/jlprat/projects/kafka/tests/venv39/lib64/python3.9/site-packages/ducktape-0.8.14-py3.9.egg/ducktape/mark/_mark.py",
line 433, in wrapper
return functools.partial(f, *args, **kwargs)(*w_args, **w_kwargs)
  File "/home/jlprat/projects/kafka/tests/kafkatest/tests/client/quota_test.py",
line 157, in test_quota
producer.run()
  File 
"/home/jlprat/projects/kafka/tests/venv39/lib64/python3.9/site-packages/ducktape-0.8.14-py3.9.egg/ducktape/services/service.py",
line 345, in run
self.wait()
  File 
"/home/jlprat/projects/kafka/tests/venv39/lib64/python3.9/site-packages/ducktape-0.8.14-py3.9.egg/ducktape/services/background_thread.py",
line 72, in wait
super(BackgroundThreadService, self).wait(timeout_sec)
  File 
"/home/jlprat/projects/kafka/tests/venv39/lib64/python3.9/site-packages/ducktape-0.8.14-py3.9.egg/ducktape/services/service.py",
line 293, in wait
raise TimeoutError("Timed out waiting %s seconds for service nodes
to finish. " % str(timeout_sec)
ducktape.errors.TimeoutError: Timed out waiting 600 seconds for
service nodes to finish. These nodes are still alive:
['ProducerPerformanceService-0-140496695824336 node 1 on worker3']


On Thu, Jul 4, 2024 at 11:57 AM Luke Chen  wrote:

> Hi Josep,
>
> For this
> - QuotaTest --> speaking with Bruno we suspect there is a problem with the
> test setup, failed with "ValueError: max() arg is an empty sequence"
>
> It's a known issue: KAFKA-16138
>  .
> It should be passed with local specific tests run.
> Do you want me help verify it by running it in my environment?
>
> Thanks.
> Luke
>
>
>
> On Thu, Jul 4, 2024 at 4:03 PM Josep Prat 
> wrote:
>
> > Hi all,
> >
> > We have had 2[1][2] runs of the system tests since the last blocker was
> > merged on 3.8. So far we have 19 tests that failed on both runs. I've
> > compiled them in this list[3].
> >
> > There seems to these different categories of failing tests:
> > - QuotaTest --> speaking with Bruno we suspect there is a problem with
> the
> > test setup, failed with "ValueError: max() arg is an empty sequence"
> > - Streams cooperative rebalance upgrade --> It fails on versions 2.3.1 or
> > older, failed with Timeout
> > - KRaft Upgrade --> from dev with Isolated and combined KRaft, failed
> with
> > RemoteCommandError
> > - Network degrade test -> failed with RemoteCommandError
> > - Replica verification tool test --> Timeout for KRaft, but ZK failed on
> > the first run but worked on the second
> >
> > If someone has further ideas on what could be causing these failures,
> > please let me know. Given holidays in the US, the possible test setup
> > problem might not be able to be fixed today.
> >
> > [1]:
> >
> >
> https://confluent-open-source-kafka-system-test-results.s3-us-west-2.amazonaws.com/3.8/2024-07-02--001.05d6b151-356a-47e5-b724-6fcd79493422--1719991984--confluentinc--3.8--49d2ee3db9/report.html
> > [2]:
> >
> >
> https://confluent-open-source-kafka-branch-builder-system-test-results.s3-us-west-2.amazonaws.com/trunk/2024-07-03--001.4803d99b-52df-4f6d-82c2-3f050a6207fa--1720038529--apache--3.8--2fbe32ecb9/report.html
> > [3]:
> >
> >
> https://docs.google.com/document/d/1wbcyzO6GM2SYQaqTMITBTBjHgZgM7mmiAt7TUfh1xt8/edit
> >
> > Best,
> >
> > On Tue, Jul 2, 2024 at 7:29 PM Josep Prat  wrote:
> >
> > > Hi all,
> > > Thanks for reviewing and merging the latest blockers for 3.8.0.
> Tomorrow,
> > > I will start with the process to get the first RC out.
> > >
> > > Best!
> > >
> > > On Sat, Jun 29, 2024 at 9:04 PM Josep Prat 
> wrote:
> > >
> > >> Hi Justine,
> > >>
> > >> Marking MV 3.8-IV0 as latest
> > >> production MV is done in this PR (I did both together)
> > >> https://github.com/apache/kafka/pull/16400
> > >>
> > >> Best,
> > >>
> > >> --
> > >> Josep Prat
> > >> Open Source Engineering Director, Aiven
> > >> josep.p...@aiven.io   |   +491715557497 | aiven.io
> > >> Aiven Deutschland GmbH
> > >> Alexanderufer 3-7, 

Re: [DISCUSS] Apache Kafka 3.8.0 release

[Luke Chen]

Hi Josep,

For this
- QuotaTest --> speaking with Bruno we suspect there is a problem with the
test setup, failed with "ValueError: max() arg is an empty sequence"

It's a known issue: KAFKA-16138
 .
It should be passed with local specific tests run.
Do you want me help verify it by running it in my environment?

Thanks.
Luke



On Thu, Jul 4, 2024 at 4:03 PM Josep Prat 
wrote:

> Hi all,
>
> We have had 2[1][2] runs of the system tests since the last blocker was
> merged on 3.8. So far we have 19 tests that failed on both runs. I've
> compiled them in this list[3].
>
> There seems to these different categories of failing tests:
> - QuotaTest --> speaking with Bruno we suspect there is a problem with the
> test setup, failed with "ValueError: max() arg is an empty sequence"
> - Streams cooperative rebalance upgrade --> It fails on versions 2.3.1 or
> older, failed with Timeout
> - KRaft Upgrade --> from dev with Isolated and combined KRaft, failed with
> RemoteCommandError
> - Network degrade test -> failed with RemoteCommandError
> - Replica verification tool test --> Timeout for KRaft, but ZK failed on
> the first run but worked on the second
>
> If someone has further ideas on what could be causing these failures,
> please let me know. Given holidays in the US, the possible test setup
> problem might not be able to be fixed today.
>
> [1]:
>
> https://confluent-open-source-kafka-system-test-results.s3-us-west-2.amazonaws.com/3.8/2024-07-02--001.05d6b151-356a-47e5-b724-6fcd79493422--1719991984--confluentinc--3.8--49d2ee3db9/report.html
> [2]:
>
> https://confluent-open-source-kafka-branch-builder-system-test-results.s3-us-west-2.amazonaws.com/trunk/2024-07-03--001.4803d99b-52df-4f6d-82c2-3f050a6207fa--1720038529--apache--3.8--2fbe32ecb9/report.html
> [3]:
>
> https://docs.google.com/document/d/1wbcyzO6GM2SYQaqTMITBTBjHgZgM7mmiAt7TUfh1xt8/edit
>
> Best,
>
> On Tue, Jul 2, 2024 at 7:29 PM Josep Prat  wrote:
>
> > Hi all,
> > Thanks for reviewing and merging the latest blockers for 3.8.0. Tomorrow,
> > I will start with the process to get the first RC out.
> >
> > Best!
> >
> > On Sat, Jun 29, 2024 at 9:04 PM Josep Prat  wrote:
> >
> >> Hi Justine,
> >>
> >> Marking MV 3.8-IV0 as latest
> >> production MV is done in this PR (I did both together)
> >> https://github.com/apache/kafka/pull/16400
> >>
> >> Best,
> >>
> >> --
> >> Josep Prat
> >> Open Source Engineering Director, Aiven
> >> josep.p...@aiven.io   |   +491715557497 | aiven.io
> >> Aiven Deutschland GmbH
> >> Alexanderufer 3-7, 10117 Berlin
> >> Geschäftsführer: Oskari Saarenmaa & Hannu Valtonen
> >> Amtsgericht Charlottenburg, HRB 209739 B
> >>
> >> On Sat, Jun 29, 2024, 00:52 Justine Olshan  >
> >> wrote:
> >>
> >>> The PR is merged. I lowered the severity of the blocker ticket as we
> >>> still
> >>> have the change in trunk to merge. However, the 3.8 release is no
> longer
> >>> blocked by KAFKA-17050.
> >>> I think that was the remaining blocker. The other ones are either
> already
> >>> fixed for 3.8 (KAFKA-17011) or diverted to 3.9 (KAFKA-16840)
> >>>
> >>> I think there was one more needed change to mark MV 3.8-IV0 as latest
> >>> production MV. I will follow up with that.
> >>>
> >>> Justine
> >>>
> >>> On Thu, Jun 27, 2024 at 2:34 PM Justine Olshan 
> >>> wrote:
> >>>
> >>> > Here is the PR: https://github.com/apache/kafka/pull/16478
> >>> >
> >>> > Justine
> >>> >
> >>> > On Thu, Jun 27, 2024 at 2:21 PM Justine Olshan  >
> >>> > wrote:
> >>> >
> >>> >> Hey all,
> >>> >> Thanks for your patience. After some discussion, we decided to
> revert
> >>> >> group version from 3.8 since there were too many complexities
> >>> associated
> >>> >> with getting it to work.
> >>> >> I've downgraded the severity of KAFKA-17011 to not be a blocker and
> >>> >> opened a ticket (https://issues.apache.org/jira/browse/KAFKA-17050)
> >>> to
> >>> >> revert from 3.8 (and 3.9) as a blocker instead. I hope to get the PR
> >>> out
> >>> >> shortly.
> >>> >> This one should be less controversial and merged quickly.
> >>> >>
> >>> >> Thanks again,
> >>> >> Justine
> >>> >>
> >>> >> On Thu, Jun 27, 2024 at 1:22 AM Josep Prat
> >>> 
> >>> >> wrote:
> >>> >>
> >>> >>> Hi all,
> >>> >>>
> >>> >>> I just wanted to ask again for your help in reviewing these 2 last
> >>> >>> blockers
> >>> >>> for the 3.8.0 release:
> >>> >>> https://github.com/apache/kafka/pull/16400
> >>> >>> https://github.com/apache/kafka/pull/16420
> >>> >>>
> >>> >>> Thanks!
> >>> >>>
> >>> >>>
> >>> >>> On Mon, Jun 24, 2024 at 9:27 AM Josep Prat 
> >>> wrote:
> >>> >>>
> >>> >>> > Hi all,
> >>> >>> >
> >>> >>> > We currently have a couple of blockers for the 3.8.0 release.
> >>> These are
> >>> >>> > the following:
> >>> >>> > - Reverting commit KAFKA-16154 and mark latest production
> metadata
> >>> as
> >>> >>> > 3.8.0: https://github.com/apache/kafka/pull/16400
> >>> >>> > - Fix some failing system tests:
> >>> >>> > 

Re: [DISCUSS] Apache Kafka 3.8.0 release

[Josep Prat]

Hi all,

We have had 2[1][2] runs of the system tests since the last blocker was
merged on 3.8. So far we have 19 tests that failed on both runs. I've
compiled them in this list[3].

There seems to these different categories of failing tests:
- QuotaTest --> speaking with Bruno we suspect there is a problem with the
test setup, failed with "ValueError: max() arg is an empty sequence"
- Streams cooperative rebalance upgrade --> It fails on versions 2.3.1 or
older, failed with Timeout
- KRaft Upgrade --> from dev with Isolated and combined KRaft, failed with
RemoteCommandError
- Network degrade test -> failed with RemoteCommandError
- Replica verification tool test --> Timeout for KRaft, but ZK failed on
the first run but worked on the second

If someone has further ideas on what could be causing these failures,
please let me know. Given holidays in the US, the possible test setup
problem might not be able to be fixed today.

[1]:
https://confluent-open-source-kafka-system-test-results.s3-us-west-2.amazonaws.com/3.8/2024-07-02--001.05d6b151-356a-47e5-b724-6fcd79493422--1719991984--confluentinc--3.8--49d2ee3db9/report.html
[2]:
https://confluent-open-source-kafka-branch-builder-system-test-results.s3-us-west-2.amazonaws.com/trunk/2024-07-03--001.4803d99b-52df-4f6d-82c2-3f050a6207fa--1720038529--apache--3.8--2fbe32ecb9/report.html
[3]:
https://docs.google.com/document/d/1wbcyzO6GM2SYQaqTMITBTBjHgZgM7mmiAt7TUfh1xt8/edit

Best,

On Tue, Jul 2, 2024 at 7:29 PM Josep Prat  wrote:

> Hi all,
> Thanks for reviewing and merging the latest blockers for 3.8.0. Tomorrow,
> I will start with the process to get the first RC out.
>
> Best!
>
> On Sat, Jun 29, 2024 at 9:04 PM Josep Prat  wrote:
>
>> Hi Justine,
>>
>> Marking MV 3.8-IV0 as latest
>> production MV is done in this PR (I did both together)
>> https://github.com/apache/kafka/pull/16400
>>
>> Best,
>>
>> --
>> Josep Prat
>> Open Source Engineering Director, Aiven
>> josep.p...@aiven.io   |   +491715557497 | aiven.io
>> Aiven Deutschland GmbH
>> Alexanderufer 3-7, 10117 Berlin
>> Geschäftsführer: Oskari Saarenmaa & Hannu Valtonen
>> Amtsgericht Charlottenburg, HRB 209739 B
>>
>> On Sat, Jun 29, 2024, 00:52 Justine Olshan 
>> wrote:
>>
>>> The PR is merged. I lowered the severity of the blocker ticket as we
>>> still
>>> have the change in trunk to merge. However, the 3.8 release is no longer
>>> blocked by KAFKA-17050.
>>> I think that was the remaining blocker. The other ones are either already
>>> fixed for 3.8 (KAFKA-17011) or diverted to 3.9 (KAFKA-16840)
>>>
>>> I think there was one more needed change to mark MV 3.8-IV0 as latest
>>> production MV. I will follow up with that.
>>>
>>> Justine
>>>
>>> On Thu, Jun 27, 2024 at 2:34 PM Justine Olshan 
>>> wrote:
>>>
>>> > Here is the PR: https://github.com/apache/kafka/pull/16478
>>> >
>>> > Justine
>>> >
>>> > On Thu, Jun 27, 2024 at 2:21 PM Justine Olshan 
>>> > wrote:
>>> >
>>> >> Hey all,
>>> >> Thanks for your patience. After some discussion, we decided to revert
>>> >> group version from 3.8 since there were too many complexities
>>> associated
>>> >> with getting it to work.
>>> >> I've downgraded the severity of KAFKA-17011 to not be a blocker and
>>> >> opened a ticket (https://issues.apache.org/jira/browse/KAFKA-17050)
>>> to
>>> >> revert from 3.8 (and 3.9) as a blocker instead. I hope to get the PR
>>> out
>>> >> shortly.
>>> >> This one should be less controversial and merged quickly.
>>> >>
>>> >> Thanks again,
>>> >> Justine
>>> >>
>>> >> On Thu, Jun 27, 2024 at 1:22 AM Josep Prat
>>> 
>>> >> wrote:
>>> >>
>>> >>> Hi all,
>>> >>>
>>> >>> I just wanted to ask again for your help in reviewing these 2 last
>>> >>> blockers
>>> >>> for the 3.8.0 release:
>>> >>> https://github.com/apache/kafka/pull/16400
>>> >>> https://github.com/apache/kafka/pull/16420
>>> >>>
>>> >>> Thanks!
>>> >>>
>>> >>>
>>> >>> On Mon, Jun 24, 2024 at 9:27 AM Josep Prat 
>>> wrote:
>>> >>>
>>> >>> > Hi all,
>>> >>> >
>>> >>> > We currently have a couple of blockers for the 3.8.0 release.
>>> These are
>>> >>> > the following:
>>> >>> > - Reverting commit KAFKA-16154 and mark latest production metadata
>>> as
>>> >>> > 3.8.0: https://github.com/apache/kafka/pull/16400
>>> >>> > - Fix some failing system tests:
>>> >>> > https://github.com/apache/kafka/pull/16420
>>> >>> > Can we get some eyes on these 2 PRs? Thanks!
>>> >>> >
>>> >>> > To easily track this in feature releases, I created a new label
>>> called
>>> >>> > "Blocker" the idea is to mark PRs that are solving an Issue marked
>>> as
>>> >>> > "blocker". This might increase visibility and help getting those
>>> >>> reviewed
>>> >>> > promptly. Here is the link to the PRs with this label:
>>> >>> > https://github.com/apache/kafka/labels/Blocker
>>> >>> >
>>> >>> > Best,
>>> >>> >
>>> >>> > On Thu, Jun 20, 2024 at 7:09 PM Josep Prat 
>>> >>> wrote:
>>> >>> >
>>> >>> >> Thanks for the heads up Justine!
>>> >>> >>
>>> >>> >> On Thu, Jun 20, 2024 at 5:54 PM 

Re: [DISCUSS] Apache Kafka 3.8.0 release

[Josep Prat]

Hi all,
Thanks for reviewing and merging the latest blockers for 3.8.0. Tomorrow, I
will start with the process to get the first RC out.

Best!

On Sat, Jun 29, 2024 at 9:04 PM Josep Prat  wrote:

> Hi Justine,
>
> Marking MV 3.8-IV0 as latest
> production MV is done in this PR (I did both together)
> https://github.com/apache/kafka/pull/16400
>
> Best,
>
> --
> Josep Prat
> Open Source Engineering Director, Aiven
> josep.p...@aiven.io   |   +491715557497 | aiven.io
> Aiven Deutschland GmbH
> Alexanderufer 3-7, 10117 Berlin
> Geschäftsführer: Oskari Saarenmaa & Hannu Valtonen
> Amtsgericht Charlottenburg, HRB 209739 B
>
> On Sat, Jun 29, 2024, 00:52 Justine Olshan 
> wrote:
>
>> The PR is merged. I lowered the severity of the blocker ticket as we still
>> have the change in trunk to merge. However, the 3.8 release is no longer
>> blocked by KAFKA-17050.
>> I think that was the remaining blocker. The other ones are either already
>> fixed for 3.8 (KAFKA-17011) or diverted to 3.9 (KAFKA-16840)
>>
>> I think there was one more needed change to mark MV 3.8-IV0 as latest
>> production MV. I will follow up with that.
>>
>> Justine
>>
>> On Thu, Jun 27, 2024 at 2:34 PM Justine Olshan 
>> wrote:
>>
>> > Here is the PR: https://github.com/apache/kafka/pull/16478
>> >
>> > Justine
>> >
>> > On Thu, Jun 27, 2024 at 2:21 PM Justine Olshan 
>> > wrote:
>> >
>> >> Hey all,
>> >> Thanks for your patience. After some discussion, we decided to revert
>> >> group version from 3.8 since there were too many complexities
>> associated
>> >> with getting it to work.
>> >> I've downgraded the severity of KAFKA-17011 to not be a blocker and
>> >> opened a ticket (https://issues.apache.org/jira/browse/KAFKA-17050) to
>> >> revert from 3.8 (and 3.9) as a blocker instead. I hope to get the PR
>> out
>> >> shortly.
>> >> This one should be less controversial and merged quickly.
>> >>
>> >> Thanks again,
>> >> Justine
>> >>
>> >> On Thu, Jun 27, 2024 at 1:22 AM Josep Prat > >
>> >> wrote:
>> >>
>> >>> Hi all,
>> >>>
>> >>> I just wanted to ask again for your help in reviewing these 2 last
>> >>> blockers
>> >>> for the 3.8.0 release:
>> >>> https://github.com/apache/kafka/pull/16400
>> >>> https://github.com/apache/kafka/pull/16420
>> >>>
>> >>> Thanks!
>> >>>
>> >>>
>> >>> On Mon, Jun 24, 2024 at 9:27 AM Josep Prat 
>> wrote:
>> >>>
>> >>> > Hi all,
>> >>> >
>> >>> > We currently have a couple of blockers for the 3.8.0 release. These
>> are
>> >>> > the following:
>> >>> > - Reverting commit KAFKA-16154 and mark latest production metadata
>> as
>> >>> > 3.8.0: https://github.com/apache/kafka/pull/16400
>> >>> > - Fix some failing system tests:
>> >>> > https://github.com/apache/kafka/pull/16420
>> >>> > Can we get some eyes on these 2 PRs? Thanks!
>> >>> >
>> >>> > To easily track this in feature releases, I created a new label
>> called
>> >>> > "Blocker" the idea is to mark PRs that are solving an Issue marked
>> as
>> >>> > "blocker". This might increase visibility and help getting those
>> >>> reviewed
>> >>> > promptly. Here is the link to the PRs with this label:
>> >>> > https://github.com/apache/kafka/labels/Blocker
>> >>> >
>> >>> > Best,
>> >>> >
>> >>> > On Thu, Jun 20, 2024 at 7:09 PM Josep Prat 
>> >>> wrote:
>> >>> >
>> >>> >> Thanks for the heads up Justine!
>> >>> >>
>> >>> >> On Thu, Jun 20, 2024 at 5:54 PM Justine Olshan
>> >>> >>  wrote:
>> >>> >>
>> >>> >>> Sorry to derail this conversation, but just wanted to share we
>> have a
>> >>> >>> system test blocker with
>> >>> >>> https://issues.apache.org/jira/browse/KAFKA-16990.
>> >>> >>> Hopefully we can fix this in the next day or so.
>> >>> >>>
>> >>> >>> Justine
>> >>> >>>
>> >>> >>> On Mon, Jun 17, 2024 at 12:19 PM David Jacot <
>> david.ja...@gmail.com>
>> >>> >>> wrote:
>> >>> >>>
>> >>> >>> > I meant it from a time perspective, not from a branching point
>> >>> >>> perspective.
>> >>> >>> > Sorry for the confusion. As said in the other thread, doing it
>> four
>> >>> >>> months
>> >>> >>> > after 3.9 is desirable for KIP-848 as I expect that we will need
>> >>> time
>> >>> >>> to
>> >>> >>> > stabilize everything after switching all the default configs
>> once
>> >>> 3.9
>> >>> >>> is
>> >>> >>> > cut.
>> >>> >>> >
>> >>> >>> > David
>> >>> >>> >
>> >>> >>> > Le lun. 17 juin 2024 à 19:33, Matthias J. Sax 
>> a
>> >>> >>> écrit :
>> >>> >>> >
>> >>> >>> > > Why would 4.0 be based on 3.8? My understanding is, that it
>> will
>> >>> be
>> >>> >>> > > based on 3.9.
>> >>> >>> > >
>> >>> >>> > > -Matthias
>> >>> >>> > >
>> >>> >>> > > On 6/14/24 11:22 PM, David Jacot wrote:
>> >>> >>> > > > I agree that we should keep 4.0 time-based. My question is
>> >>> based on
>> >>> >>> > which
>> >>> >>> > > > release. If I understand you, you would like to keep it
>> based
>> >>> on
>> >>> >>> 3.8.
>> >>> >>> > > This
>> >>> >>> > > > means that 4.0 would be released in October. It would be
>> >>> helpful
>> >>> >>> to fix
>> >>> >>> > > the
>> >>> >>> > > 

Re: [DISCUSS] Apache Kafka 3.8.0 release

[Josep Prat]

Hi Justine,

Marking MV 3.8-IV0 as latest
production MV is done in this PR (I did both together)
https://github.com/apache/kafka/pull/16400

Best,

--
Josep Prat
Open Source Engineering Director, Aiven
josep.p...@aiven.io   |   +491715557497 | aiven.io
Aiven Deutschland GmbH
Alexanderufer 3-7, 10117 Berlin
Geschäftsführer: Oskari Saarenmaa & Hannu Valtonen
Amtsgericht Charlottenburg, HRB 209739 B

On Sat, Jun 29, 2024, 00:52 Justine Olshan 
wrote:

> The PR is merged. I lowered the severity of the blocker ticket as we still
> have the change in trunk to merge. However, the 3.8 release is no longer
> blocked by KAFKA-17050.
> I think that was the remaining blocker. The other ones are either already
> fixed for 3.8 (KAFKA-17011) or diverted to 3.9 (KAFKA-16840)
>
> I think there was one more needed change to mark MV 3.8-IV0 as latest
> production MV. I will follow up with that.
>
> Justine
>
> On Thu, Jun 27, 2024 at 2:34 PM Justine Olshan 
> wrote:
>
> > Here is the PR: https://github.com/apache/kafka/pull/16478
> >
> > Justine
> >
> > On Thu, Jun 27, 2024 at 2:21 PM Justine Olshan 
> > wrote:
> >
> >> Hey all,
> >> Thanks for your patience. After some discussion, we decided to revert
> >> group version from 3.8 since there were too many complexities associated
> >> with getting it to work.
> >> I've downgraded the severity of KAFKA-17011 to not be a blocker and
> >> opened a ticket (https://issues.apache.org/jira/browse/KAFKA-17050) to
> >> revert from 3.8 (and 3.9) as a blocker instead. I hope to get the PR out
> >> shortly.
> >> This one should be less controversial and merged quickly.
> >>
> >> Thanks again,
> >> Justine
> >>
> >> On Thu, Jun 27, 2024 at 1:22 AM Josep Prat  >
> >> wrote:
> >>
> >>> Hi all,
> >>>
> >>> I just wanted to ask again for your help in reviewing these 2 last
> >>> blockers
> >>> for the 3.8.0 release:
> >>> https://github.com/apache/kafka/pull/16400
> >>> https://github.com/apache/kafka/pull/16420
> >>>
> >>> Thanks!
> >>>
> >>>
> >>> On Mon, Jun 24, 2024 at 9:27 AM Josep Prat 
> wrote:
> >>>
> >>> > Hi all,
> >>> >
> >>> > We currently have a couple of blockers for the 3.8.0 release. These
> are
> >>> > the following:
> >>> > - Reverting commit KAFKA-16154 and mark latest production metadata as
> >>> > 3.8.0: https://github.com/apache/kafka/pull/16400
> >>> > - Fix some failing system tests:
> >>> > https://github.com/apache/kafka/pull/16420
> >>> > Can we get some eyes on these 2 PRs? Thanks!
> >>> >
> >>> > To easily track this in feature releases, I created a new label
> called
> >>> > "Blocker" the idea is to mark PRs that are solving an Issue marked as
> >>> > "blocker". This might increase visibility and help getting those
> >>> reviewed
> >>> > promptly. Here is the link to the PRs with this label:
> >>> > https://github.com/apache/kafka/labels/Blocker
> >>> >
> >>> > Best,
> >>> >
> >>> > On Thu, Jun 20, 2024 at 7:09 PM Josep Prat 
> >>> wrote:
> >>> >
> >>> >> Thanks for the heads up Justine!
> >>> >>
> >>> >> On Thu, Jun 20, 2024 at 5:54 PM Justine Olshan
> >>> >>  wrote:
> >>> >>
> >>> >>> Sorry to derail this conversation, but just wanted to share we
> have a
> >>> >>> system test blocker with
> >>> >>> https://issues.apache.org/jira/browse/KAFKA-16990.
> >>> >>> Hopefully we can fix this in the next day or so.
> >>> >>>
> >>> >>> Justine
> >>> >>>
> >>> >>> On Mon, Jun 17, 2024 at 12:19 PM David Jacot <
> david.ja...@gmail.com>
> >>> >>> wrote:
> >>> >>>
> >>> >>> > I meant it from a time perspective, not from a branching point
> >>> >>> perspective.
> >>> >>> > Sorry for the confusion. As said in the other thread, doing it
> four
> >>> >>> months
> >>> >>> > after 3.9 is desirable for KIP-848 as I expect that we will need
> >>> time
> >>> >>> to
> >>> >>> > stabilize everything after switching all the default configs once
> >>> 3.9
> >>> >>> is
> >>> >>> > cut.
> >>> >>> >
> >>> >>> > David
> >>> >>> >
> >>> >>> > Le lun. 17 juin 2024 à 19:33, Matthias J. Sax 
> a
> >>> >>> écrit :
> >>> >>> >
> >>> >>> > > Why would 4.0 be based on 3.8? My understanding is, that it
> will
> >>> be
> >>> >>> > > based on 3.9.
> >>> >>> > >
> >>> >>> > > -Matthias
> >>> >>> > >
> >>> >>> > > On 6/14/24 11:22 PM, David Jacot wrote:
> >>> >>> > > > I agree that we should keep 4.0 time-based. My question is
> >>> based on
> >>> >>> > which
> >>> >>> > > > release. If I understand you, you would like to keep it based
> >>> on
> >>> >>> 3.8.
> >>> >>> > > This
> >>> >>> > > > means that 4.0 would be released in October. It would be
> >>> helpful
> >>> >>> to fix
> >>> >>> > > the
> >>> >>> > > > dates so we can plan accordingly. I will start a separate
> >>> thread on
> >>> >>> > > Monday.
> >>> >>> > > >
> >>> >>> > > > David
> >>> >>> > > >
> >>> >>> > > > Le sam. 15 juin 2024 à 00:44, Colin McCabe <
> cmcc...@apache.org>
> >>> a
> >>> >>> > écrit
> >>> >>> > > :
> >>> >>> > > >
> >>> >>> > > >> +1. I think it would be good to keep 4.0 time-based. Most of
> >>> the
> 

Re: [DISCUSS] Apache Kafka 3.8.0 release

[Justine Olshan]

The PR is merged. I lowered the severity of the blocker ticket as we still
have the change in trunk to merge. However, the 3.8 release is no longer
blocked by KAFKA-17050.
I think that was the remaining blocker. The other ones are either already
fixed for 3.8 (KAFKA-17011) or diverted to 3.9 (KAFKA-16840)

I think there was one more needed change to mark MV 3.8-IV0 as latest
production MV. I will follow up with that.

Justine

On Thu, Jun 27, 2024 at 2:34 PM Justine Olshan  wrote:

> Here is the PR: https://github.com/apache/kafka/pull/16478
>
> Justine
>
> On Thu, Jun 27, 2024 at 2:21 PM Justine Olshan 
> wrote:
>
>> Hey all,
>> Thanks for your patience. After some discussion, we decided to revert
>> group version from 3.8 since there were too many complexities associated
>> with getting it to work.
>> I've downgraded the severity of KAFKA-17011 to not be a blocker and
>> opened a ticket (https://issues.apache.org/jira/browse/KAFKA-17050) to
>> revert from 3.8 (and 3.9) as a blocker instead. I hope to get the PR out
>> shortly.
>> This one should be less controversial and merged quickly.
>>
>> Thanks again,
>> Justine
>>
>> On Thu, Jun 27, 2024 at 1:22 AM Josep Prat 
>> wrote:
>>
>>> Hi all,
>>>
>>> I just wanted to ask again for your help in reviewing these 2 last
>>> blockers
>>> for the 3.8.0 release:
>>> https://github.com/apache/kafka/pull/16400
>>> https://github.com/apache/kafka/pull/16420
>>>
>>> Thanks!
>>>
>>>
>>> On Mon, Jun 24, 2024 at 9:27 AM Josep Prat  wrote:
>>>
>>> > Hi all,
>>> >
>>> > We currently have a couple of blockers for the 3.8.0 release. These are
>>> > the following:
>>> > - Reverting commit KAFKA-16154 and mark latest production metadata as
>>> > 3.8.0: https://github.com/apache/kafka/pull/16400
>>> > - Fix some failing system tests:
>>> > https://github.com/apache/kafka/pull/16420
>>> > Can we get some eyes on these 2 PRs? Thanks!
>>> >
>>> > To easily track this in feature releases, I created a new label called
>>> > "Blocker" the idea is to mark PRs that are solving an Issue marked as
>>> > "blocker". This might increase visibility and help getting those
>>> reviewed
>>> > promptly. Here is the link to the PRs with this label:
>>> > https://github.com/apache/kafka/labels/Blocker
>>> >
>>> > Best,
>>> >
>>> > On Thu, Jun 20, 2024 at 7:09 PM Josep Prat 
>>> wrote:
>>> >
>>> >> Thanks for the heads up Justine!
>>> >>
>>> >> On Thu, Jun 20, 2024 at 5:54 PM Justine Olshan
>>> >>  wrote:
>>> >>
>>> >>> Sorry to derail this conversation, but just wanted to share we have a
>>> >>> system test blocker with
>>> >>> https://issues.apache.org/jira/browse/KAFKA-16990.
>>> >>> Hopefully we can fix this in the next day or so.
>>> >>>
>>> >>> Justine
>>> >>>
>>> >>> On Mon, Jun 17, 2024 at 12:19 PM David Jacot 
>>> >>> wrote:
>>> >>>
>>> >>> > I meant it from a time perspective, not from a branching point
>>> >>> perspective.
>>> >>> > Sorry for the confusion. As said in the other thread, doing it four
>>> >>> months
>>> >>> > after 3.9 is desirable for KIP-848 as I expect that we will need
>>> time
>>> >>> to
>>> >>> > stabilize everything after switching all the default configs once
>>> 3.9
>>> >>> is
>>> >>> > cut.
>>> >>> >
>>> >>> > David
>>> >>> >
>>> >>> > Le lun. 17 juin 2024 à 19:33, Matthias J. Sax  a
>>> >>> écrit :
>>> >>> >
>>> >>> > > Why would 4.0 be based on 3.8? My understanding is, that it will
>>> be
>>> >>> > > based on 3.9.
>>> >>> > >
>>> >>> > > -Matthias
>>> >>> > >
>>> >>> > > On 6/14/24 11:22 PM, David Jacot wrote:
>>> >>> > > > I agree that we should keep 4.0 time-based. My question is
>>> based on
>>> >>> > which
>>> >>> > > > release. If I understand you, you would like to keep it based
>>> on
>>> >>> 3.8.
>>> >>> > > This
>>> >>> > > > means that 4.0 would be released in October. It would be
>>> helpful
>>> >>> to fix
>>> >>> > > the
>>> >>> > > > dates so we can plan accordingly. I will start a separate
>>> thread on
>>> >>> > > Monday.
>>> >>> > > >
>>> >>> > > > David
>>> >>> > > >
>>> >>> > > > Le sam. 15 juin 2024 à 00:44, Colin McCabe 
>>> a
>>> >>> > écrit
>>> >>> > > :
>>> >>> > > >
>>> >>> > > >> +1. I think it would be good to keep 4.0 time-based. Most of
>>> the
>>> >>> > > refactors
>>> >>> > > >> we want to do are optional in some sense and can be descoped
>>> if
>>> >>> time
>>> >>> > > runs
>>> >>> > > >> out. For example, we can drop support for JDK 8 without
>>> >>> immediately
>>> >>> > > >> refactoring everything that could benefit from the
>>> improvements in
>>> >>> > > JDK9+.
>>> >>> > > >>
>>> >>> > > >> best,
>>> >>> > > >> Colin
>>> >>> > > >>
>>> >>> > > >>
>>> >>> > > >> On Fri, Jun 14, 2024, at 15:37, Matthias J. Sax wrote:
>>> >>> > > >>> That's my understanding, and I would advocate strongly to
>>> keep
>>> >>> the
>>> >>> > 4.0
>>> >>> > > >>> release schedule as planed originally.
>>> >>> > > >>>
>>> >>> > > >>> The 3.9 one should really be an additional "out of schedule"
>>> >>> release
>>> >>> > > not
>>> >>> > > >>> 

Re: [DISCUSS] Apache Kafka 3.8.0 release

[Justine Olshan]

Here is the PR: https://github.com/apache/kafka/pull/16478

Justine

On Thu, Jun 27, 2024 at 2:21 PM Justine Olshan  wrote:

> Hey all,
> Thanks for your patience. After some discussion, we decided to revert
> group version from 3.8 since there were too many complexities associated
> with getting it to work.
> I've downgraded the severity of KAFKA-17011 to not be a blocker and opened
> a ticket (https://issues.apache.org/jira/browse/KAFKA-17050) to revert
> from 3.8 (and 3.9) as a blocker instead. I hope to get the PR out shortly.
> This one should be less controversial and merged quickly.
>
> Thanks again,
> Justine
>
> On Thu, Jun 27, 2024 at 1:22 AM Josep Prat 
> wrote:
>
>> Hi all,
>>
>> I just wanted to ask again for your help in reviewing these 2 last
>> blockers
>> for the 3.8.0 release:
>> https://github.com/apache/kafka/pull/16400
>> https://github.com/apache/kafka/pull/16420
>>
>> Thanks!
>>
>>
>> On Mon, Jun 24, 2024 at 9:27 AM Josep Prat  wrote:
>>
>> > Hi all,
>> >
>> > We currently have a couple of blockers for the 3.8.0 release. These are
>> > the following:
>> > - Reverting commit KAFKA-16154 and mark latest production metadata as
>> > 3.8.0: https://github.com/apache/kafka/pull/16400
>> > - Fix some failing system tests:
>> > https://github.com/apache/kafka/pull/16420
>> > Can we get some eyes on these 2 PRs? Thanks!
>> >
>> > To easily track this in feature releases, I created a new label called
>> > "Blocker" the idea is to mark PRs that are solving an Issue marked as
>> > "blocker". This might increase visibility and help getting those
>> reviewed
>> > promptly. Here is the link to the PRs with this label:
>> > https://github.com/apache/kafka/labels/Blocker
>> >
>> > Best,
>> >
>> > On Thu, Jun 20, 2024 at 7:09 PM Josep Prat  wrote:
>> >
>> >> Thanks for the heads up Justine!
>> >>
>> >> On Thu, Jun 20, 2024 at 5:54 PM Justine Olshan
>> >>  wrote:
>> >>
>> >>> Sorry to derail this conversation, but just wanted to share we have a
>> >>> system test blocker with
>> >>> https://issues.apache.org/jira/browse/KAFKA-16990.
>> >>> Hopefully we can fix this in the next day or so.
>> >>>
>> >>> Justine
>> >>>
>> >>> On Mon, Jun 17, 2024 at 12:19 PM David Jacot 
>> >>> wrote:
>> >>>
>> >>> > I meant it from a time perspective, not from a branching point
>> >>> perspective.
>> >>> > Sorry for the confusion. As said in the other thread, doing it four
>> >>> months
>> >>> > after 3.9 is desirable for KIP-848 as I expect that we will need
>> time
>> >>> to
>> >>> > stabilize everything after switching all the default configs once
>> 3.9
>> >>> is
>> >>> > cut.
>> >>> >
>> >>> > David
>> >>> >
>> >>> > Le lun. 17 juin 2024 à 19:33, Matthias J. Sax  a
>> >>> écrit :
>> >>> >
>> >>> > > Why would 4.0 be based on 3.8? My understanding is, that it will
>> be
>> >>> > > based on 3.9.
>> >>> > >
>> >>> > > -Matthias
>> >>> > >
>> >>> > > On 6/14/24 11:22 PM, David Jacot wrote:
>> >>> > > > I agree that we should keep 4.0 time-based. My question is
>> based on
>> >>> > which
>> >>> > > > release. If I understand you, you would like to keep it based on
>> >>> 3.8.
>> >>> > > This
>> >>> > > > means that 4.0 would be released in October. It would be helpful
>> >>> to fix
>> >>> > > the
>> >>> > > > dates so we can plan accordingly. I will start a separate
>> thread on
>> >>> > > Monday.
>> >>> > > >
>> >>> > > > David
>> >>> > > >
>> >>> > > > Le sam. 15 juin 2024 à 00:44, Colin McCabe 
>> a
>> >>> > écrit
>> >>> > > :
>> >>> > > >
>> >>> > > >> +1. I think it would be good to keep 4.0 time-based. Most of
>> the
>> >>> > > refactors
>> >>> > > >> we want to do are optional in some sense and can be descoped if
>> >>> time
>> >>> > > runs
>> >>> > > >> out. For example, we can drop support for JDK 8 without
>> >>> immediately
>> >>> > > >> refactoring everything that could benefit from the
>> improvements in
>> >>> > > JDK9+.
>> >>> > > >>
>> >>> > > >> best,
>> >>> > > >> Colin
>> >>> > > >>
>> >>> > > >>
>> >>> > > >> On Fri, Jun 14, 2024, at 15:37, Matthias J. Sax wrote:
>> >>> > > >>> That's my understanding, and I would advocate strongly to keep
>> >>> the
>> >>> > 4.0
>> >>> > > >>> release schedule as planed originally.
>> >>> > > >>>
>> >>> > > >>> The 3.9 one should really be an additional "out of schedule"
>> >>> release
>> >>> > > not
>> >>> > > >>> impacting any other releases.
>> >>> > > >>>
>> >>> > > >>>
>> >>> > > >>> -Matthias
>> >>> > > >>>
>> >>> > > >>> On 6/14/24 1:29 PM, David Jacot wrote:
>> >>> > >  The plan sounds good to me. I suppose that we will follow our
>> >>> > regular
>> >>> > >  cadence for 4.0 and release it four months after 3.9 (in
>> >>> November?).
>> >>> > > Is
>> >>> > >  this correct?
>> >>> > > 
>> >>> > >  Best,
>> >>> > >  David
>> >>> > > 
>> >>> > >  Le ven. 14 juin 2024 à 21:57, José Armando García Sancio
>> >>> > >   a écrit :
>> >>> > > 
>> >>> > > > +1 on the proposed release plan for 3.8.
>> >>> > > >
>> >>> > > 

Re: [DISCUSS] Apache Kafka 3.8.0 release

[Justine Olshan]

Hey all,
Thanks for your patience. After some discussion, we decided to revert group
version from 3.8 since there were too many complexities associated with
getting it to work.
I've downgraded the severity of KAFKA-17011 to not be a blocker and opened
a ticket (https://issues.apache.org/jira/browse/KAFKA-17050) to revert from
3.8 (and 3.9) as a blocker instead. I hope to get the PR out shortly.
This one should be less controversial and merged quickly.

Thanks again,
Justine

On Thu, Jun 27, 2024 at 1:22 AM Josep Prat 
wrote:

> Hi all,
>
> I just wanted to ask again for your help in reviewing these 2 last blockers
> for the 3.8.0 release:
> https://github.com/apache/kafka/pull/16400
> https://github.com/apache/kafka/pull/16420
>
> Thanks!
>
>
> On Mon, Jun 24, 2024 at 9:27 AM Josep Prat  wrote:
>
> > Hi all,
> >
> > We currently have a couple of blockers for the 3.8.0 release. These are
> > the following:
> > - Reverting commit KAFKA-16154 and mark latest production metadata as
> > 3.8.0: https://github.com/apache/kafka/pull/16400
> > - Fix some failing system tests:
> > https://github.com/apache/kafka/pull/16420
> > Can we get some eyes on these 2 PRs? Thanks!
> >
> > To easily track this in feature releases, I created a new label called
> > "Blocker" the idea is to mark PRs that are solving an Issue marked as
> > "blocker". This might increase visibility and help getting those reviewed
> > promptly. Here is the link to the PRs with this label:
> > https://github.com/apache/kafka/labels/Blocker
> >
> > Best,
> >
> > On Thu, Jun 20, 2024 at 7:09 PM Josep Prat  wrote:
> >
> >> Thanks for the heads up Justine!
> >>
> >> On Thu, Jun 20, 2024 at 5:54 PM Justine Olshan
> >>  wrote:
> >>
> >>> Sorry to derail this conversation, but just wanted to share we have a
> >>> system test blocker with
> >>> https://issues.apache.org/jira/browse/KAFKA-16990.
> >>> Hopefully we can fix this in the next day or so.
> >>>
> >>> Justine
> >>>
> >>> On Mon, Jun 17, 2024 at 12:19 PM David Jacot 
> >>> wrote:
> >>>
> >>> > I meant it from a time perspective, not from a branching point
> >>> perspective.
> >>> > Sorry for the confusion. As said in the other thread, doing it four
> >>> months
> >>> > after 3.9 is desirable for KIP-848 as I expect that we will need time
> >>> to
> >>> > stabilize everything after switching all the default configs once 3.9
> >>> is
> >>> > cut.
> >>> >
> >>> > David
> >>> >
> >>> > Le lun. 17 juin 2024 à 19:33, Matthias J. Sax  a
> >>> écrit :
> >>> >
> >>> > > Why would 4.0 be based on 3.8? My understanding is, that it will be
> >>> > > based on 3.9.
> >>> > >
> >>> > > -Matthias
> >>> > >
> >>> > > On 6/14/24 11:22 PM, David Jacot wrote:
> >>> > > > I agree that we should keep 4.0 time-based. My question is based
> on
> >>> > which
> >>> > > > release. If I understand you, you would like to keep it based on
> >>> 3.8.
> >>> > > This
> >>> > > > means that 4.0 would be released in October. It would be helpful
> >>> to fix
> >>> > > the
> >>> > > > dates so we can plan accordingly. I will start a separate thread
> on
> >>> > > Monday.
> >>> > > >
> >>> > > > David
> >>> > > >
> >>> > > > Le sam. 15 juin 2024 à 00:44, Colin McCabe 
> a
> >>> > écrit
> >>> > > :
> >>> > > >
> >>> > > >> +1. I think it would be good to keep 4.0 time-based. Most of the
> >>> > > refactors
> >>> > > >> we want to do are optional in some sense and can be descoped if
> >>> time
> >>> > > runs
> >>> > > >> out. For example, we can drop support for JDK 8 without
> >>> immediately
> >>> > > >> refactoring everything that could benefit from the improvements
> in
> >>> > > JDK9+.
> >>> > > >>
> >>> > > >> best,
> >>> > > >> Colin
> >>> > > >>
> >>> > > >>
> >>> > > >> On Fri, Jun 14, 2024, at 15:37, Matthias J. Sax wrote:
> >>> > > >>> That's my understanding, and I would advocate strongly to keep
> >>> the
> >>> > 4.0
> >>> > > >>> release schedule as planed originally.
> >>> > > >>>
> >>> > > >>> The 3.9 one should really be an additional "out of schedule"
> >>> release
> >>> > > not
> >>> > > >>> impacting any other releases.
> >>> > > >>>
> >>> > > >>>
> >>> > > >>> -Matthias
> >>> > > >>>
> >>> > > >>> On 6/14/24 1:29 PM, David Jacot wrote:
> >>> > >  The plan sounds good to me. I suppose that we will follow our
> >>> > regular
> >>> > >  cadence for 4.0 and release it four months after 3.9 (in
> >>> November?).
> >>> > > Is
> >>> > >  this correct?
> >>> > > 
> >>> > >  Best,
> >>> > >  David
> >>> > > 
> >>> > >  Le ven. 14 juin 2024 à 21:57, José Armando García Sancio
> >>> > >   a écrit :
> >>> > > 
> >>> > > > +1 on the proposed release plan for 3.8.
> >>> > > >
> >>> > > > Thanks!
> >>> > > >
> >>> > > > On Fri, Jun 14, 2024 at 3:33 PM Ismael Juma <
> m...@ismaeljuma.com
> >>> >
> >>> > > wrote:
> >>> > > >>
> >>> > > >> +1 to the plan we converged on in this thread.
> >>> > > >>
> >>> > > >> Ismael
> >>> > > >>
> >>> > > >> On Fri, 

Re: [DISCUSS] Apache Kafka 3.8.0 release

[Josep Prat]

Hi all,

I just wanted to ask again for your help in reviewing these 2 last blockers
for the 3.8.0 release:
https://github.com/apache/kafka/pull/16400
https://github.com/apache/kafka/pull/16420

Thanks!


On Mon, Jun 24, 2024 at 9:27 AM Josep Prat  wrote:

> Hi all,
>
> We currently have a couple of blockers for the 3.8.0 release. These are
> the following:
> - Reverting commit KAFKA-16154 and mark latest production metadata as
> 3.8.0: https://github.com/apache/kafka/pull/16400
> - Fix some failing system tests:
> https://github.com/apache/kafka/pull/16420
> Can we get some eyes on these 2 PRs? Thanks!
>
> To easily track this in feature releases, I created a new label called
> "Blocker" the idea is to mark PRs that are solving an Issue marked as
> "blocker". This might increase visibility and help getting those reviewed
> promptly. Here is the link to the PRs with this label:
> https://github.com/apache/kafka/labels/Blocker
>
> Best,
>
> On Thu, Jun 20, 2024 at 7:09 PM Josep Prat  wrote:
>
>> Thanks for the heads up Justine!
>>
>> On Thu, Jun 20, 2024 at 5:54 PM Justine Olshan
>>  wrote:
>>
>>> Sorry to derail this conversation, but just wanted to share we have a
>>> system test blocker with
>>> https://issues.apache.org/jira/browse/KAFKA-16990.
>>> Hopefully we can fix this in the next day or so.
>>>
>>> Justine
>>>
>>> On Mon, Jun 17, 2024 at 12:19 PM David Jacot 
>>> wrote:
>>>
>>> > I meant it from a time perspective, not from a branching point
>>> perspective.
>>> > Sorry for the confusion. As said in the other thread, doing it four
>>> months
>>> > after 3.9 is desirable for KIP-848 as I expect that we will need time
>>> to
>>> > stabilize everything after switching all the default configs once 3.9
>>> is
>>> > cut.
>>> >
>>> > David
>>> >
>>> > Le lun. 17 juin 2024 à 19:33, Matthias J. Sax  a
>>> écrit :
>>> >
>>> > > Why would 4.0 be based on 3.8? My understanding is, that it will be
>>> > > based on 3.9.
>>> > >
>>> > > -Matthias
>>> > >
>>> > > On 6/14/24 11:22 PM, David Jacot wrote:
>>> > > > I agree that we should keep 4.0 time-based. My question is based on
>>> > which
>>> > > > release. If I understand you, you would like to keep it based on
>>> 3.8.
>>> > > This
>>> > > > means that 4.0 would be released in October. It would be helpful
>>> to fix
>>> > > the
>>> > > > dates so we can plan accordingly. I will start a separate thread on
>>> > > Monday.
>>> > > >
>>> > > > David
>>> > > >
>>> > > > Le sam. 15 juin 2024 à 00:44, Colin McCabe  a
>>> > écrit
>>> > > :
>>> > > >
>>> > > >> +1. I think it would be good to keep 4.0 time-based. Most of the
>>> > > refactors
>>> > > >> we want to do are optional in some sense and can be descoped if
>>> time
>>> > > runs
>>> > > >> out. For example, we can drop support for JDK 8 without
>>> immediately
>>> > > >> refactoring everything that could benefit from the improvements in
>>> > > JDK9+.
>>> > > >>
>>> > > >> best,
>>> > > >> Colin
>>> > > >>
>>> > > >>
>>> > > >> On Fri, Jun 14, 2024, at 15:37, Matthias J. Sax wrote:
>>> > > >>> That's my understanding, and I would advocate strongly to keep
>>> the
>>> > 4.0
>>> > > >>> release schedule as planed originally.
>>> > > >>>
>>> > > >>> The 3.9 one should really be an additional "out of schedule"
>>> release
>>> > > not
>>> > > >>> impacting any other releases.
>>> > > >>>
>>> > > >>>
>>> > > >>> -Matthias
>>> > > >>>
>>> > > >>> On 6/14/24 1:29 PM, David Jacot wrote:
>>> > >  The plan sounds good to me. I suppose that we will follow our
>>> > regular
>>> > >  cadence for 4.0 and release it four months after 3.9 (in
>>> November?).
>>> > > Is
>>> > >  this correct?
>>> > > 
>>> > >  Best,
>>> > >  David
>>> > > 
>>> > >  Le ven. 14 juin 2024 à 21:57, José Armando García Sancio
>>> > >   a écrit :
>>> > > 
>>> > > > +1 on the proposed release plan for 3.8.
>>> > > >
>>> > > > Thanks!
>>> > > >
>>> > > > On Fri, Jun 14, 2024 at 3:33 PM Ismael Juma >> >
>>> > > wrote:
>>> > > >>
>>> > > >> +1 to the plan we converged on in this thread.
>>> > > >>
>>> > > >> Ismael
>>> > > >>
>>> > > >> On Fri, Jun 14, 2024 at 10:46 AM Josep Prat
>>> > > >> >> > > >>
>>> > > >> wrote:
>>> > > >>
>>> > > >>> Hi all,
>>> > > >>>
>>> > > >>> Thanks Colin, yes go ahead.
>>> > > >>>
>>> > > >>> As we are now past code freeze I would like to ask everyone
>>> > > involved
>>> > > > in a
>>> > > >>> KIP that is not yet complete, to verify if what landed on
>>> the 3.8
>>> > > > branch
>>> > > >>> needs to be reverted or if it can stay. Additionally, I'll be
>>> > > pinging
>>> > > > KIPs
>>> > > >>> and Jira reporters asking for their status as some Jiras
>>> seem to
>>> > > have
>>> > > > all
>>> > > >>> related GitHub PRs merged but their status is still Open or
>>> In
>>> > > > Progress.
>>> > > >>> I'll be checking all the open blockers and check if they are
>>> > > 

Re: [DISCUSS] Apache Kafka 3.8.0 release

[Josep Prat]

Hi all,

We currently have a couple of blockers for the 3.8.0 release. These are the
following:
- Reverting commit KAFKA-16154 and mark latest production metadata as
3.8.0: https://github.com/apache/kafka/pull/16400
- Fix some failing system tests: https://github.com/apache/kafka/pull/16420
Can we get some eyes on these 2 PRs? Thanks!

To easily track this in feature releases, I created a new label called
"Blocker" the idea is to mark PRs that are solving an Issue marked as
"blocker". This might increase visibility and help getting those reviewed
promptly. Here is the link to the PRs with this label:
https://github.com/apache/kafka/labels/Blocker

Best,

On Thu, Jun 20, 2024 at 7:09 PM Josep Prat  wrote:

> Thanks for the heads up Justine!
>
> On Thu, Jun 20, 2024 at 5:54 PM Justine Olshan
>  wrote:
>
>> Sorry to derail this conversation, but just wanted to share we have a
>> system test blocker with
>> https://issues.apache.org/jira/browse/KAFKA-16990.
>> Hopefully we can fix this in the next day or so.
>>
>> Justine
>>
>> On Mon, Jun 17, 2024 at 12:19 PM David Jacot 
>> wrote:
>>
>> > I meant it from a time perspective, not from a branching point
>> perspective.
>> > Sorry for the confusion. As said in the other thread, doing it four
>> months
>> > after 3.9 is desirable for KIP-848 as I expect that we will need time to
>> > stabilize everything after switching all the default configs once 3.9 is
>> > cut.
>> >
>> > David
>> >
>> > Le lun. 17 juin 2024 à 19:33, Matthias J. Sax  a
>> écrit :
>> >
>> > > Why would 4.0 be based on 3.8? My understanding is, that it will be
>> > > based on 3.9.
>> > >
>> > > -Matthias
>> > >
>> > > On 6/14/24 11:22 PM, David Jacot wrote:
>> > > > I agree that we should keep 4.0 time-based. My question is based on
>> > which
>> > > > release. If I understand you, you would like to keep it based on
>> 3.8.
>> > > This
>> > > > means that 4.0 would be released in October. It would be helpful to
>> fix
>> > > the
>> > > > dates so we can plan accordingly. I will start a separate thread on
>> > > Monday.
>> > > >
>> > > > David
>> > > >
>> > > > Le sam. 15 juin 2024 à 00:44, Colin McCabe  a
>> > écrit
>> > > :
>> > > >
>> > > >> +1. I think it would be good to keep 4.0 time-based. Most of the
>> > > refactors
>> > > >> we want to do are optional in some sense and can be descoped if
>> time
>> > > runs
>> > > >> out. For example, we can drop support for JDK 8 without immediately
>> > > >> refactoring everything that could benefit from the improvements in
>> > > JDK9+.
>> > > >>
>> > > >> best,
>> > > >> Colin
>> > > >>
>> > > >>
>> > > >> On Fri, Jun 14, 2024, at 15:37, Matthias J. Sax wrote:
>> > > >>> That's my understanding, and I would advocate strongly to keep the
>> > 4.0
>> > > >>> release schedule as planed originally.
>> > > >>>
>> > > >>> The 3.9 one should really be an additional "out of schedule"
>> release
>> > > not
>> > > >>> impacting any other releases.
>> > > >>>
>> > > >>>
>> > > >>> -Matthias
>> > > >>>
>> > > >>> On 6/14/24 1:29 PM, David Jacot wrote:
>> > >  The plan sounds good to me. I suppose that we will follow our
>> > regular
>> > >  cadence for 4.0 and release it four months after 3.9 (in
>> November?).
>> > > Is
>> > >  this correct?
>> > > 
>> > >  Best,
>> > >  David
>> > > 
>> > >  Le ven. 14 juin 2024 à 21:57, José Armando García Sancio
>> > >   a écrit :
>> > > 
>> > > > +1 on the proposed release plan for 3.8.
>> > > >
>> > > > Thanks!
>> > > >
>> > > > On Fri, Jun 14, 2024 at 3:33 PM Ismael Juma 
>> > > wrote:
>> > > >>
>> > > >> +1 to the plan we converged on in this thread.
>> > > >>
>> > > >> Ismael
>> > > >>
>> > > >> On Fri, Jun 14, 2024 at 10:46 AM Josep Prat
>> > > >> > > > >>
>> > > >> wrote:
>> > > >>
>> > > >>> Hi all,
>> > > >>>
>> > > >>> Thanks Colin, yes go ahead.
>> > > >>>
>> > > >>> As we are now past code freeze I would like to ask everyone
>> > > involved
>> > > > in a
>> > > >>> KIP that is not yet complete, to verify if what landed on the
>> 3.8
>> > > > branch
>> > > >>> needs to be reverted or if it can stay. Additionally, I'll be
>> > > pinging
>> > > > KIPs
>> > > >>> and Jira reporters asking for their status as some Jiras seem
>> to
>> > > have
>> > > > all
>> > > >>> related GitHub PRs merged but their status is still Open or In
>> > > > Progress.
>> > > >>> I'll be checking all the open blockers and check if they are
>> > > really a
>> > > >>> blocker or can be pushed.
>> > > >>>
>> > > >>>
>> > > >>> Regarding timeline, I'll attempt to generate the first RC on
>> > > >> Wednesday
>> > > > or
>> > > >>> Thursday, so please revert any changes
>> > > <
>> >
>> https://www.google.com/maps/search/,+so+please+revert+any+changes+?entry=gmail=g
>> > >you
>> > > deem necessary by then. If
>> > > > you
>> > > >>> need more time, please ping 

Re: [DISCUSS] Apache Kafka 3.8.0 release

[Josep Prat]

Thanks for the heads up Justine!

On Thu, Jun 20, 2024 at 5:54 PM Justine Olshan 
wrote:

> Sorry to derail this conversation, but just wanted to share we have a
> system test blocker with https://issues.apache.org/jira/browse/KAFKA-16990
> .
> Hopefully we can fix this in the next day or so.
>
> Justine
>
> On Mon, Jun 17, 2024 at 12:19 PM David Jacot 
> wrote:
>
> > I meant it from a time perspective, not from a branching point
> perspective.
> > Sorry for the confusion. As said in the other thread, doing it four
> months
> > after 3.9 is desirable for KIP-848 as I expect that we will need time to
> > stabilize everything after switching all the default configs once 3.9 is
> > cut.
> >
> > David
> >
> > Le lun. 17 juin 2024 à 19:33, Matthias J. Sax  a
> écrit :
> >
> > > Why would 4.0 be based on 3.8? My understanding is, that it will be
> > > based on 3.9.
> > >
> > > -Matthias
> > >
> > > On 6/14/24 11:22 PM, David Jacot wrote:
> > > > I agree that we should keep 4.0 time-based. My question is based on
> > which
> > > > release. If I understand you, you would like to keep it based on 3.8.
> > > This
> > > > means that 4.0 would be released in October. It would be helpful to
> fix
> > > the
> > > > dates so we can plan accordingly. I will start a separate thread on
> > > Monday.
> > > >
> > > > David
> > > >
> > > > Le sam. 15 juin 2024 à 00:44, Colin McCabe  a
> > écrit
> > > :
> > > >
> > > >> +1. I think it would be good to keep 4.0 time-based. Most of the
> > > refactors
> > > >> we want to do are optional in some sense and can be descoped if time
> > > runs
> > > >> out. For example, we can drop support for JDK 8 without immediately
> > > >> refactoring everything that could benefit from the improvements in
> > > JDK9+.
> > > >>
> > > >> best,
> > > >> Colin
> > > >>
> > > >>
> > > >> On Fri, Jun 14, 2024, at 15:37, Matthias J. Sax wrote:
> > > >>> That's my understanding, and I would advocate strongly to keep the
> > 4.0
> > > >>> release schedule as planed originally.
> > > >>>
> > > >>> The 3.9 one should really be an additional "out of schedule"
> release
> > > not
> > > >>> impacting any other releases.
> > > >>>
> > > >>>
> > > >>> -Matthias
> > > >>>
> > > >>> On 6/14/24 1:29 PM, David Jacot wrote:
> > >  The plan sounds good to me. I suppose that we will follow our
> > regular
> > >  cadence for 4.0 and release it four months after 3.9 (in
> November?).
> > > Is
> > >  this correct?
> > > 
> > >  Best,
> > >  David
> > > 
> > >  Le ven. 14 juin 2024 à 21:57, José Armando García Sancio
> > >   a écrit :
> > > 
> > > > +1 on the proposed release plan for 3.8.
> > > >
> > > > Thanks!
> > > >
> > > > On Fri, Jun 14, 2024 at 3:33 PM Ismael Juma 
> > > wrote:
> > > >>
> > > >> +1 to the plan we converged on in this thread.
> > > >>
> > > >> Ismael
> > > >>
> > > >> On Fri, Jun 14, 2024 at 10:46 AM Josep Prat
> > > >>  > > >>
> > > >> wrote:
> > > >>
> > > >>> Hi all,
> > > >>>
> > > >>> Thanks Colin, yes go ahead.
> > > >>>
> > > >>> As we are now past code freeze I would like to ask everyone
> > > involved
> > > > in a
> > > >>> KIP that is not yet complete, to verify if what landed on the
> 3.8
> > > > branch
> > > >>> needs to be reverted or if it can stay. Additionally, I'll be
> > > pinging
> > > > KIPs
> > > >>> and Jira reporters asking for their status as some Jiras seem
> to
> > > have
> > > > all
> > > >>> related GitHub PRs merged but their status is still Open or In
> > > > Progress.
> > > >>> I'll be checking all the open blockers and check if they are
> > > really a
> > > >>> blocker or can be pushed.
> > > >>>
> > > >>>
> > > >>> Regarding timeline, I'll attempt to generate the first RC on
> > > >> Wednesday
> > > > or
> > > >>> Thursday, so please revert any changes
> > > <
> >
> https://www.google.com/maps/search/,+so+please+revert+any+changes+?entry=gmail=g
> > >you
> > > deem necessary by then. If
> > > > you
> > > >>> need more time, please ping me.
> > > >>>
> > > >>> Best,
> > > >>>
> > > >>> -
> > > >>> Josep Prat
> > > >>> Open Source Engineering Director, Aiven
> > > >>> josep.p...@aiven.io   |   +491715557497 | aiven.io
> > > >>> Aiven Deutschland GmbH
> > > >>> Alexanderufer 3-7, 10117 Berlin
> > > >>> Geschäftsführer: Oskari Saarenmaa & Hannu Valtonen
> > > >>> Amtsgericht Charlottenburg, HRB 209739 B
> > > >>>
> > > >>> On Fri, Jun 14, 2024, 19:25 Colin McCabe 
> > > wrote:
> > > >>>
> > >  Hi all,
> > > 
> > >  We have had many delays with releases this year. We should try
> > to
> > > >> get
> > > >>> back
> > >  on schedule.
> > > 
> > >  I agree with the idea that was proposed a few times in this
> > thread
> > > >> of
> > >  drawing a line under 

Re: [DISCUSS] Apache Kafka 3.8.0 release

[Justine Olshan]

Sorry to derail this conversation, but just wanted to share we have a
system test blocker with https://issues.apache.org/jira/browse/KAFKA-16990.
Hopefully we can fix this in the next day or so.

Justine

On Mon, Jun 17, 2024 at 12:19 PM David Jacot  wrote:

> I meant it from a time perspective, not from a branching point perspective.
> Sorry for the confusion. As said in the other thread, doing it four months
> after 3.9 is desirable for KIP-848 as I expect that we will need time to
> stabilize everything after switching all the default configs once 3.9 is
> cut.
>
> David
>
> Le lun. 17 juin 2024 à 19:33, Matthias J. Sax  a écrit :
>
> > Why would 4.0 be based on 3.8? My understanding is, that it will be
> > based on 3.9.
> >
> > -Matthias
> >
> > On 6/14/24 11:22 PM, David Jacot wrote:
> > > I agree that we should keep 4.0 time-based. My question is based on
> which
> > > release. If I understand you, you would like to keep it based on 3.8.
> > This
> > > means that 4.0 would be released in October. It would be helpful to fix
> > the
> > > dates so we can plan accordingly. I will start a separate thread on
> > Monday.
> > >
> > > David
> > >
> > > Le sam. 15 juin 2024 à 00:44, Colin McCabe  a
> écrit
> > :
> > >
> > >> +1. I think it would be good to keep 4.0 time-based. Most of the
> > refactors
> > >> we want to do are optional in some sense and can be descoped if time
> > runs
> > >> out. For example, we can drop support for JDK 8 without immediately
> > >> refactoring everything that could benefit from the improvements in
> > JDK9+.
> > >>
> > >> best,
> > >> Colin
> > >>
> > >>
> > >> On Fri, Jun 14, 2024, at 15:37, Matthias J. Sax wrote:
> > >>> That's my understanding, and I would advocate strongly to keep the
> 4.0
> > >>> release schedule as planed originally.
> > >>>
> > >>> The 3.9 one should really be an additional "out of schedule" release
> > not
> > >>> impacting any other releases.
> > >>>
> > >>>
> > >>> -Matthias
> > >>>
> > >>> On 6/14/24 1:29 PM, David Jacot wrote:
> >  The plan sounds good to me. I suppose that we will follow our
> regular
> >  cadence for 4.0 and release it four months after 3.9 (in November?).
> > Is
> >  this correct?
> > 
> >  Best,
> >  David
> > 
> >  Le ven. 14 juin 2024 à 21:57, José Armando García Sancio
> >   a écrit :
> > 
> > > +1 on the proposed release plan for 3.8.
> > >
> > > Thanks!
> > >
> > > On Fri, Jun 14, 2024 at 3:33 PM Ismael Juma 
> > wrote:
> > >>
> > >> +1 to the plan we converged on in this thread.
> > >>
> > >> Ismael
> > >>
> > >> On Fri, Jun 14, 2024 at 10:46 AM Josep Prat
> > >>  > >>
> > >> wrote:
> > >>
> > >>> Hi all,
> > >>>
> > >>> Thanks Colin, yes go ahead.
> > >>>
> > >>> As we are now past code freeze I would like to ask everyone
> > involved
> > > in a
> > >>> KIP that is not yet complete, to verify if what landed on the 3.8
> > > branch
> > >>> needs to be reverted or if it can stay. Additionally, I'll be
> > pinging
> > > KIPs
> > >>> and Jira reporters asking for their status as some Jiras seem to
> > have
> > > all
> > >>> related GitHub PRs merged but their status is still Open or In
> > > Progress.
> > >>> I'll be checking all the open blockers and check if they are
> > really a
> > >>> blocker or can be pushed.
> > >>>
> > >>>
> > >>> Regarding timeline, I'll attempt to generate the first RC on
> > >> Wednesday
> > > or
> > >>> Thursday, so please revert any changes
> > <
> https://www.google.com/maps/search/,+so+please+revert+any+changes+?entry=gmail=g
> >you
> > deem necessary by then. If
> > > you
> > >>> need more time, please ping me.
> > >>>
> > >>> Best,
> > >>>
> > >>> -
> > >>> Josep Prat
> > >>> Open Source Engineering Director, Aiven
> > >>> josep.p...@aiven.io   |   +491715557497 | aiven.io
> > >>> Aiven Deutschland GmbH
> > >>> Alexanderufer 3-7, 10117 Berlin
> > >>> Geschäftsführer: Oskari Saarenmaa & Hannu Valtonen
> > >>> Amtsgericht Charlottenburg, HRB 209739 B
> > >>>
> > >>> On Fri, Jun 14, 2024, 19:25 Colin McCabe 
> > wrote:
> > >>>
> >  Hi all,
> > 
> >  We have had many delays with releases this year. We should try
> to
> > >> get
> > >>> back
> >  on schedule.
> > 
> >  I agree with the idea that was proposed a few times in this
> thread
> > >> of
> >  drawing a line under 3.8 now, and doing a short 3.9 release. I
> > > posted a
> > >>> 3.9
> >  release plan here:
> > 
> > >> https://cwiki.apache.org/confluence/display/KAFKA/Release+Plan+3.9.0
> > 
> >  I think we could start doing RCs for 3.8.0 as early as next
> week.
> > > There
> >  are a few things that need to be reverted first (anything
> related
> > to
> >  

Re: [DISCUSS] Apache Kafka 3.8.0 release

[David Jacot]

I meant it from a time perspective, not from a branching point perspective.
Sorry for the confusion. As said in the other thread, doing it four months
after 3.9 is desirable for KIP-848 as I expect that we will need time to
stabilize everything after switching all the default configs once 3.9 is
cut.

David

Le lun. 17 juin 2024 à 19:33, Matthias J. Sax  a écrit :

> Why would 4.0 be based on 3.8? My understanding is, that it will be
> based on 3.9.
>
> -Matthias
>
> On 6/14/24 11:22 PM, David Jacot wrote:
> > I agree that we should keep 4.0 time-based. My question is based on which
> > release. If I understand you, you would like to keep it based on 3.8.
> This
> > means that 4.0 would be released in October. It would be helpful to fix
> the
> > dates so we can plan accordingly. I will start a separate thread on
> Monday.
> >
> > David
> >
> > Le sam. 15 juin 2024 à 00:44, Colin McCabe  a écrit
> :
> >
> >> +1. I think it would be good to keep 4.0 time-based. Most of the
> refactors
> >> we want to do are optional in some sense and can be descoped if time
> runs
> >> out. For example, we can drop support for JDK 8 without immediately
> >> refactoring everything that could benefit from the improvements in
> JDK9+.
> >>
> >> best,
> >> Colin
> >>
> >>
> >> On Fri, Jun 14, 2024, at 15:37, Matthias J. Sax wrote:
> >>> That's my understanding, and I would advocate strongly to keep the 4.0
> >>> release schedule as planed originally.
> >>>
> >>> The 3.9 one should really be an additional "out of schedule" release
> not
> >>> impacting any other releases.
> >>>
> >>>
> >>> -Matthias
> >>>
> >>> On 6/14/24 1:29 PM, David Jacot wrote:
>  The plan sounds good to me. I suppose that we will follow our regular
>  cadence for 4.0 and release it four months after 3.9 (in November?).
> Is
>  this correct?
> 
>  Best,
>  David
> 
>  Le ven. 14 juin 2024 à 21:57, José Armando García Sancio
>   a écrit :
> 
> > +1 on the proposed release plan for 3.8.
> >
> > Thanks!
> >
> > On Fri, Jun 14, 2024 at 3:33 PM Ismael Juma 
> wrote:
> >>
> >> +1 to the plan we converged on in this thread.
> >>
> >> Ismael
> >>
> >> On Fri, Jun 14, 2024 at 10:46 AM Josep Prat
> >>  >>
> >> wrote:
> >>
> >>> Hi all,
> >>>
> >>> Thanks Colin, yes go ahead.
> >>>
> >>> As we are now past code freeze I would like to ask everyone
> involved
> > in a
> >>> KIP that is not yet complete, to verify if what landed on the 3.8
> > branch
> >>> needs to be reverted or if it can stay. Additionally, I'll be
> pinging
> > KIPs
> >>> and Jira reporters asking for their status as some Jiras seem to
> have
> > all
> >>> related GitHub PRs merged but their status is still Open or In
> > Progress.
> >>> I'll be checking all the open blockers and check if they are
> really a
> >>> blocker or can be pushed.
> >>>
> >>>
> >>> Regarding timeline, I'll attempt to generate the first RC on
> >> Wednesday
> > or
> >>> Thursday, so please revert any changes
> you
> deem necessary by then. If
> > you
> >>> need more time, please ping me.
> >>>
> >>> Best,
> >>>
> >>> -
> >>> Josep Prat
> >>> Open Source Engineering Director, Aiven
> >>> josep.p...@aiven.io   |   +491715557497 | aiven.io
> >>> Aiven Deutschland GmbH
> >>> Alexanderufer 3-7, 10117 Berlin
> >>> Geschäftsführer: Oskari Saarenmaa & Hannu Valtonen
> >>> Amtsgericht Charlottenburg, HRB 209739 B
> >>>
> >>> On Fri, Jun 14, 2024, 19:25 Colin McCabe 
> wrote:
> >>>
>  Hi all,
> 
>  We have had many delays with releases this year. We should try to
> >> get
> >>> back
>  on schedule.
> 
>  I agree with the idea that was proposed a few times in this thread
> >> of
>  drawing a line under 3.8 now, and doing a short 3.9 release. I
> > posted a
> >>> 3.9
>  release plan here:
> 
> >> https://cwiki.apache.org/confluence/display/KAFKA/Release+Plan+3.9.0
> 
>  I think we could start doing RCs for 3.8.0 as early as next week.
> > There
>  are a few things that need to be reverted first (anything related
> to
>  KIP-853 or KIP-966).
> 
>  Josep, if you agree, I will update KIP-1012 to reflect that these
> > things
>  are landing in 3.9 rather than 3.8. And we can start doing all the
> > normal
>  release stuff. The main blocker JIRA I'm aware of is KAFKA-16946,
> > which
> >>> is
>  a very simple fix.
> 
>  best,
>  Colin
> 
> 
>  On Fri, Jun 14, 2024, at 03:48, Satish Duggana wrote:
> > +1 on going with 3.8 release with the existing plan and targeting
> > the
> 

Re: [DISCUSS] Apache Kafka 3.8.0 release

[Matthias J. Sax]

Why would 4.0 be based on 3.8? My understanding is, that it will be 
based on 3.9.


-Matthias

On 6/14/24 11:22 PM, David Jacot wrote:

I agree that we should keep 4.0 time-based. My question is based on which
release. If I understand you, you would like to keep it based on 3.8. This
means that 4.0 would be released in October. It would be helpful to fix the
dates so we can plan accordingly. I will start a separate thread on Monday.

David

Le sam. 15 juin 2024 à 00:44, Colin McCabe  a écrit :


+1. I think it would be good to keep 4.0 time-based. Most of the refactors
we want to do are optional in some sense and can be descoped if time runs
out. For example, we can drop support for JDK 8 without immediately
refactoring everything that could benefit from the improvements in JDK9+.

best,
Colin


On Fri, Jun 14, 2024, at 15:37, Matthias J. Sax wrote:

That's my understanding, and I would advocate strongly to keep the 4.0
release schedule as planed originally.

The 3.9 one should really be an additional "out of schedule" release not
impacting any other releases.


-Matthias

On 6/14/24 1:29 PM, David Jacot wrote:

The plan sounds good to me. I suppose that we will follow our regular
cadence for 4.0 and release it four months after 3.9 (in November?). Is
this correct?

Best,
David

Le ven. 14 juin 2024 à 21:57, José Armando García Sancio
 a écrit :


+1 on the proposed release plan for 3.8.

Thanks!

On Fri, Jun 14, 2024 at 3:33 PM Ismael Juma  wrote:


+1 to the plan we converged on in this thread.

Ismael

On Fri, Jun 14, 2024 at 10:46 AM Josep Prat



wrote:


Hi all,

Thanks Colin, yes go ahead.

As we are now past code freeze I would like to ask everyone involved

in a

KIP that is not yet complete, to verify if what landed on the 3.8

branch

needs to be reverted or if it can stay. Additionally, I'll be pinging

KIPs

and Jira reporters asking for their status as some Jiras seem to have

all

related GitHub PRs merged but their status is still Open or In

Progress.

I'll be checking all the open blockers and check if they are really a
blocker or can be pushed.


Regarding timeline, I'll attempt to generate the first RC on

Wednesday

or

Thursday, so please revert any changes you deem necessary by then. If

you

need more time, please ping me.

Best,

-
Josep Prat
Open Source Engineering Director, Aiven
josep.p...@aiven.io   |   +491715557497 | aiven.io
Aiven Deutschland GmbH
Alexanderufer 3-7, 10117 Berlin
Geschäftsführer: Oskari Saarenmaa & Hannu Valtonen
Amtsgericht Charlottenburg, HRB 209739 B

On Fri, Jun 14, 2024, 19:25 Colin McCabe  wrote:


Hi all,

We have had many delays with releases this year. We should try to

get

back

on schedule.

I agree with the idea that was proposed a few times in this thread

of

drawing a line under 3.8 now, and doing a short 3.9 release. I

posted a

3.9

release plan here:


https://cwiki.apache.org/confluence/display/KAFKA/Release+Plan+3.9.0


I think we could start doing RCs for 3.8.0 as early as next week.

There

are a few things that need to be reverted first (anything related to
KIP-853 or KIP-966).

Josep, if you agree, I will update KIP-1012 to reflect that these

things

are landing in 3.9 rather than 3.8. And we can start doing all the

normal

release stuff. The main blocker JIRA I'm aware of is KAFKA-16946,

which

is

a very simple fix.

best,
Colin


On Fri, Jun 14, 2024, at 03:48, Satish Duggana wrote:

+1 on going with 3.8 release with the existing plan and targeting

the

required features in 3.9 timelines. 4.0 will be targeted in the

usual

cycle(4 months) after 3.9 is released.


On Fri, 14 Jun 2024 at 15:19, Edoardo Comar 


wrote:


Josep,
past the deadline sorry but I can't see reasons not to cherry-pick

this

https://github.com/apache/kafka/pull/16326

On Wed, 12 Jun 2024 at 17:14, Josep Prat



wrote:


Hi Edoardo,

Correct, you can still cherry-pick this one.

I'll send an email tomorrow morning (CEST) asking maintainers to

stop

cherry picking commits unless we discuss it beforehand.

Best,

On Wed, Jun 12, 2024 at 6:09 PM Edoardo Comar <

edoardli...@gmail.com>

wrote:



Hi Josep, I understand I am still in time to cherry-pick on

3.8.0

https://github.com/apache/kafka/pull/16229

right?
thanks

On Wed, 12 Jun 2024 at 11:34, Ivan Yurchenko 

wrote:


Hi,

I'll try to do all the fixes and changes for KIP-899 [1]

sooner

today,

but please proceed with the release if I don't manage.


Ivan

[1] https://github.com/apache/kafka/pull/13277

On Wed, Jun 12, 2024, at 12:54, Josep Prat wrote:

Hi Luke,
I think Jose, also mentioned that it won't be ready for

v3.8.0

(but he

can

confirm this). My question now would be, given that it

seems

we

would

need

a v3.9.0, do you think it's important to include
https://github.com/apache/kafka/pull/16284 in v3.8.0?

Best,

On Wed, Jun 12, 2024 at 11:40 AM Luke Chen <

show...@gmail.com


wrote:



Hi Josep

For KIP-966, I think Calvin had mentioned he won't

complete

in

Re: [DISCUSS] Apache Kafka 3.8.0 release

[David Jacot]

I agree that we should keep 4.0 time-based. My question is based on which
release. If I understand you, you would like to keep it based on 3.8. This
means that 4.0 would be released in October. It would be helpful to fix the
dates so we can plan accordingly. I will start a separate thread on Monday.

David

Le sam. 15 juin 2024 à 00:44, Colin McCabe  a écrit :

> +1. I think it would be good to keep 4.0 time-based. Most of the refactors
> we want to do are optional in some sense and can be descoped if time runs
> out. For example, we can drop support for JDK 8 without immediately
> refactoring everything that could benefit from the improvements in JDK9+.
>
> best,
> Colin
>
>
> On Fri, Jun 14, 2024, at 15:37, Matthias J. Sax wrote:
> > That's my understanding, and I would advocate strongly to keep the 4.0
> > release schedule as planed originally.
> >
> > The 3.9 one should really be an additional "out of schedule" release not
> > impacting any other releases.
> >
> >
> > -Matthias
> >
> > On 6/14/24 1:29 PM, David Jacot wrote:
> >> The plan sounds good to me. I suppose that we will follow our regular
> >> cadence for 4.0 and release it four months after 3.9 (in November?). Is
> >> this correct?
> >>
> >> Best,
> >> David
> >>
> >> Le ven. 14 juin 2024 à 21:57, José Armando García Sancio
> >>  a écrit :
> >>
> >>> +1 on the proposed release plan for 3.8.
> >>>
> >>> Thanks!
> >>>
> >>> On Fri, Jun 14, 2024 at 3:33 PM Ismael Juma  wrote:
> 
>  +1 to the plan we converged on in this thread.
> 
>  Ismael
> 
>  On Fri, Jun 14, 2024 at 10:46 AM Josep Prat
>  
>  wrote:
> 
> > Hi all,
> >
> > Thanks Colin, yes go ahead.
> >
> > As we are now past code freeze I would like to ask everyone involved
> >>> in a
> > KIP that is not yet complete, to verify if what landed on the 3.8
> >>> branch
> > needs to be reverted or if it can stay. Additionally, I'll be pinging
> >>> KIPs
> > and Jira reporters asking for their status as some Jiras seem to have
> >>> all
> > related GitHub PRs merged but their status is still Open or In
> >>> Progress.
> > I'll be checking all the open blockers and check if they are really a
> > blocker or can be pushed.
> >
> >
> > Regarding timeline, I'll attempt to generate the first RC on
> Wednesday
> >>> or
> > Thursday, so please revert any changes you deem necessary by then. If
> >>> you
> > need more time, please ping me.
> >
> > Best,
> >
> > -
> > Josep Prat
> > Open Source Engineering Director, Aiven
> > josep.p...@aiven.io   |   +491715557497 | aiven.io
> > Aiven Deutschland GmbH
> > Alexanderufer 3-7, 10117 Berlin
> > Geschäftsführer: Oskari Saarenmaa & Hannu Valtonen
> > Amtsgericht Charlottenburg, HRB 209739 B
> >
> > On Fri, Jun 14, 2024, 19:25 Colin McCabe  wrote:
> >
> >> Hi all,
> >>
> >> We have had many delays with releases this year. We should try to
> get
> > back
> >> on schedule.
> >>
> >> I agree with the idea that was proposed a few times in this thread
> of
> >> drawing a line under 3.8 now, and doing a short 3.9 release. I
> >>> posted a
> > 3.9
> >> release plan here:
> >>
> https://cwiki.apache.org/confluence/display/KAFKA/Release+Plan+3.9.0
> >>
> >> I think we could start doing RCs for 3.8.0 as early as next week.
> >>> There
> >> are a few things that need to be reverted first (anything related to
> >> KIP-853 or KIP-966).
> >>
> >> Josep, if you agree, I will update KIP-1012 to reflect that these
> >>> things
> >> are landing in 3.9 rather than 3.8. And we can start doing all the
> >>> normal
> >> release stuff. The main blocker JIRA I'm aware of is KAFKA-16946,
> >>> which
> > is
> >> a very simple fix.
> >>
> >> best,
> >> Colin
> >>
> >>
> >> On Fri, Jun 14, 2024, at 03:48, Satish Duggana wrote:
> >>> +1 on going with 3.8 release with the existing plan and targeting
> >>> the
> >>> required features in 3.9 timelines. 4.0 will be targeted in the
> >>> usual
> >>> cycle(4 months) after 3.9 is released.
> >>>
> >>>
> >>> On Fri, 14 Jun 2024 at 15:19, Edoardo Comar  
> >> wrote:
> 
>  Josep,
>  past the deadline sorry but I can't see reasons not to cherry-pick
> > this
>  https://github.com/apache/kafka/pull/16326
> 
>  On Wed, 12 Jun 2024 at 17:14, Josep Prat
> >>>  >>
> >> wrote:
> >
> > Hi Edoardo,
> >
> > Correct, you can still cherry-pick this one.
> >
> > I'll send an email tomorrow morning (CEST) asking maintainers to
> > stop
> > cherry picking commits unless we discuss it beforehand.
> >
> > Best,
> >
> > On Wed, Jun 12, 2024 at 6:09 PM Edoardo Comar <
> > edoardli...@gmail.com>
> >> 

Re: [DISCUSS] Apache Kafka 3.8.0 release

[Colin McCabe]

+1. I think it would be good to keep 4.0 time-based. Most of the refactors we 
want to do are optional in some sense and can be descoped if time runs out. For 
example, we can drop support for JDK 8 without immediately refactoring 
everything that could benefit from the improvements in JDK9+.

best,
Colin


On Fri, Jun 14, 2024, at 15:37, Matthias J. Sax wrote:
> That's my understanding, and I would advocate strongly to keep the 4.0 
> release schedule as planed originally.
>
> The 3.9 one should really be an additional "out of schedule" release not 
> impacting any other releases.
>
>
> -Matthias
>
> On 6/14/24 1:29 PM, David Jacot wrote:
>> The plan sounds good to me. I suppose that we will follow our regular
>> cadence for 4.0 and release it four months after 3.9 (in November?). Is
>> this correct?
>> 
>> Best,
>> David
>> 
>> Le ven. 14 juin 2024 à 21:57, José Armando García Sancio
>>  a écrit :
>> 
>>> +1 on the proposed release plan for 3.8.
>>>
>>> Thanks!
>>>
>>> On Fri, Jun 14, 2024 at 3:33 PM Ismael Juma  wrote:

 +1 to the plan we converged on in this thread.

 Ismael

 On Fri, Jun 14, 2024 at 10:46 AM Josep Prat >>>
 wrote:

> Hi all,
>
> Thanks Colin, yes go ahead.
>
> As we are now past code freeze I would like to ask everyone involved
>>> in a
> KIP that is not yet complete, to verify if what landed on the 3.8
>>> branch
> needs to be reverted or if it can stay. Additionally, I'll be pinging
>>> KIPs
> and Jira reporters asking for their status as some Jiras seem to have
>>> all
> related GitHub PRs merged but their status is still Open or In
>>> Progress.
> I'll be checking all the open blockers and check if they are really a
> blocker or can be pushed.
>
>
> Regarding timeline, I'll attempt to generate the first RC on Wednesday
>>> or
> Thursday, so please revert any changes you deem necessary by then. If
>>> you
> need more time, please ping me.
>
> Best,
>
> -
> Josep Prat
> Open Source Engineering Director, Aiven
> josep.p...@aiven.io   |   +491715557497 | aiven.io
> Aiven Deutschland GmbH
> Alexanderufer 3-7, 10117 Berlin
> Geschäftsführer: Oskari Saarenmaa & Hannu Valtonen
> Amtsgericht Charlottenburg, HRB 209739 B
>
> On Fri, Jun 14, 2024, 19:25 Colin McCabe  wrote:
>
>> Hi all,
>>
>> We have had many delays with releases this year. We should try to get
> back
>> on schedule.
>>
>> I agree with the idea that was proposed a few times in this thread of
>> drawing a line under 3.8 now, and doing a short 3.9 release. I
>>> posted a
> 3.9
>> release plan here:
>> https://cwiki.apache.org/confluence/display/KAFKA/Release+Plan+3.9.0
>>
>> I think we could start doing RCs for 3.8.0 as early as next week.
>>> There
>> are a few things that need to be reverted first (anything related to
>> KIP-853 or KIP-966).
>>
>> Josep, if you agree, I will update KIP-1012 to reflect that these
>>> things
>> are landing in 3.9 rather than 3.8. And we can start doing all the
>>> normal
>> release stuff. The main blocker JIRA I'm aware of is KAFKA-16946,
>>> which
> is
>> a very simple fix.
>>
>> best,
>> Colin
>>
>>
>> On Fri, Jun 14, 2024, at 03:48, Satish Duggana wrote:
>>> +1 on going with 3.8 release with the existing plan and targeting
>>> the
>>> required features in 3.9 timelines. 4.0 will be targeted in the
>>> usual
>>> cycle(4 months) after 3.9 is released.
>>>
>>>
>>> On Fri, 14 Jun 2024 at 15:19, Edoardo Comar >>>
>> wrote:

 Josep,
 past the deadline sorry but I can't see reasons not to cherry-pick
> this
 https://github.com/apache/kafka/pull/16326

 On Wed, 12 Jun 2024 at 17:14, Josep Prat
>>> >
>> wrote:
>
> Hi Edoardo,
>
> Correct, you can still cherry-pick this one.
>
> I'll send an email tomorrow morning (CEST) asking maintainers to
> stop
> cherry picking commits unless we discuss it beforehand.
>
> Best,
>
> On Wed, Jun 12, 2024 at 6:09 PM Edoardo Comar <
> edoardli...@gmail.com>
>> wrote:
>
>> Hi Josep, I understand I am still in time to cherry-pick on
>>> 3.8.0
>> https://github.com/apache/kafka/pull/16229
>>
>> right?
>> thanks
>>
>> On Wed, 12 Jun 2024 at 11:34, Ivan Yurchenko 
>> wrote:
>>>
>>> Hi,
>>>
>>> I'll try to do all the fixes and changes for KIP-899 [1]
>>> sooner
>> today,
>> but please proceed with the release if I don't manage.
>>>
>>> Ivan
>>>
>>> [1] https://github.com/apache/kafka/pull/13277
>>>
>>> On Wed, Jun 12, 2024, at 12:54, Josep Prat wrote:

Re: [DISCUSS] Apache Kafka 3.8.0 release

[Matthias J. Sax]

That's my understanding, and I would advocate strongly to keep the 4.0 
release schedule as planed originally.


The 3.9 one should really be an additional "out of schedule" release not 
impacting any other releases.



-Matthias

On 6/14/24 1:29 PM, David Jacot wrote:

The plan sounds good to me. I suppose that we will follow our regular
cadence for 4.0 and release it four months after 3.9 (in November?). Is
this correct?

Best,
David

Le ven. 14 juin 2024 à 21:57, José Armando García Sancio
 a écrit :


+1 on the proposed release plan for 3.8.

Thanks!

On Fri, Jun 14, 2024 at 3:33 PM Ismael Juma  wrote:


+1 to the plan we converged on in this thread.

Ismael

On Fri, Jun 14, 2024 at 10:46 AM Josep Prat 
Hi all,

Thanks Colin, yes go ahead.

As we are now past code freeze I would like to ask everyone involved

in a

KIP that is not yet complete, to verify if what landed on the 3.8

branch

needs to be reverted or if it can stay. Additionally, I'll be pinging

KIPs

and Jira reporters asking for their status as some Jiras seem to have

all

related GitHub PRs merged but their status is still Open or In

Progress.

I'll be checking all the open blockers and check if they are really a
blocker or can be pushed.


Regarding timeline, I'll attempt to generate the first RC on Wednesday

or

Thursday, so please revert any changes you deem necessary by then. If

you

need more time, please ping me.

Best,

-
Josep Prat
Open Source Engineering Director, Aiven
josep.p...@aiven.io   |   +491715557497 | aiven.io
Aiven Deutschland GmbH
Alexanderufer 3-7, 10117 Berlin
Geschäftsführer: Oskari Saarenmaa & Hannu Valtonen
Amtsgericht Charlottenburg, HRB 209739 B

On Fri, Jun 14, 2024, 19:25 Colin McCabe  wrote:


Hi all,

We have had many delays with releases this year. We should try to get

back

on schedule.

I agree with the idea that was proposed a few times in this thread of
drawing a line under 3.8 now, and doing a short 3.9 release. I

posted a

3.9

release plan here:
https://cwiki.apache.org/confluence/display/KAFKA/Release+Plan+3.9.0

I think we could start doing RCs for 3.8.0 as early as next week.

There

are a few things that need to be reverted first (anything related to
KIP-853 or KIP-966).

Josep, if you agree, I will update KIP-1012 to reflect that these

things

are landing in 3.9 rather than 3.8. And we can start doing all the

normal

release stuff. The main blocker JIRA I'm aware of is KAFKA-16946,

which

is

a very simple fix.

best,
Colin


On Fri, Jun 14, 2024, at 03:48, Satish Duggana wrote:

+1 on going with 3.8 release with the existing plan and targeting

the

required features in 3.9 timelines. 4.0 will be targeted in the

usual

cycle(4 months) after 3.9 is released.


On Fri, 14 Jun 2024 at 15:19, Edoardo Comar 


wrote:


Josep,
past the deadline sorry but I can't see reasons not to cherry-pick

this

https://github.com/apache/kafka/pull/16326

On Wed, 12 Jun 2024 at 17:14, Josep Prat



wrote:


Hi Edoardo,

Correct, you can still cherry-pick this one.

I'll send an email tomorrow morning (CEST) asking maintainers to

stop

cherry picking commits unless we discuss it beforehand.

Best,

On Wed, Jun 12, 2024 at 6:09 PM Edoardo Comar <

edoardli...@gmail.com>

wrote:



Hi Josep, I understand I am still in time to cherry-pick on

3.8.0

https://github.com/apache/kafka/pull/16229

right?
thanks

On Wed, 12 Jun 2024 at 11:34, Ivan Yurchenko 

wrote:


Hi,

I'll try to do all the fixes and changes for KIP-899 [1]

sooner

today,

but please proceed with the release if I don't manage.


Ivan

[1] https://github.com/apache/kafka/pull/13277

On Wed, Jun 12, 2024, at 12:54, Josep Prat wrote:

Hi Luke,
I think Jose, also mentioned that it won't be ready for

v3.8.0

(but he

can

confirm this). My question now would be, given that it

seems

we

would

need

a v3.9.0, do you think it's important to include
https://github.com/apache/kafka/pull/16284 in v3.8.0?

Best,

On Wed, Jun 12, 2024 at 11:40 AM Luke Chen <

show...@gmail.com


wrote:



Hi Josep

For KIP-966, I think Calvin had mentioned he won't

complete

in

v3.8.0.



https://lists.apache.org/thread/fsnr8wy5fznzfso7jgk90skgyo277fmw


For unclean leader election, all we need is this PR:
https://github.com/apache/kafka/pull/16284
For this PR, I think it needs one more week to be

completed.


Thanks.
Luke

On Wed, Jun 12, 2024 at 4:51 PM Josep Prat



wrote:


Hi all,

We are now really close to the planned code freeze

deadline

(today

EOD).

According to KIP-1012 [1] we agreed to stay in the 3.x

branch

until we

achieve feature parity regarding Zookeeper and KRaft.

The

two main

KIPs

identified that would achieve this are: KIP-853 [2]

and

KIP-966

[3].

At the moment of writing this email both KIPs are not

completed. My

question to the people driving both KIPs would be, how

much

more

time do

you think it's needed to bring these KIPs to

completion?


- If the time needed would be short, we could still

Re: [DISCUSS] Apache Kafka 3.8.0 release

[David Jacot]

The plan sounds good to me. I suppose that we will follow our regular
cadence for 4.0 and release it four months after 3.9 (in November?). Is
this correct?

Best,
David

Le ven. 14 juin 2024 à 21:57, José Armando García Sancio
 a écrit :

> +1 on the proposed release plan for 3.8.
>
> Thanks!
>
> On Fri, Jun 14, 2024 at 3:33 PM Ismael Juma  wrote:
> >
> > +1 to the plan we converged on in this thread.
> >
> > Ismael
> >
> > On Fri, Jun 14, 2024 at 10:46 AM Josep Prat  >
> > wrote:
> >
> > > Hi all,
> > >
> > > Thanks Colin, yes go ahead.
> > >
> > > As we are now past code freeze I would like to ask everyone involved
> in a
> > > KIP that is not yet complete, to verify if what landed on the 3.8
> branch
> > > needs to be reverted or if it can stay. Additionally, I'll be pinging
> KIPs
> > > and Jira reporters asking for their status as some Jiras seem to have
> all
> > > related GitHub PRs merged but their status is still Open or In
> Progress.
> > > I'll be checking all the open blockers and check if they are really a
> > > blocker or can be pushed.
> > >
> > >
> > > Regarding timeline, I'll attempt to generate the first RC on Wednesday
> or
> > > Thursday, so please revert any changes you deem necessary by then. If
> you
> > > need more time, please ping me.
> > >
> > > Best,
> > >
> > > -
> > > Josep Prat
> > > Open Source Engineering Director, Aiven
> > > josep.p...@aiven.io   |   +491715557497 | aiven.io
> > > Aiven Deutschland GmbH
> > > Alexanderufer 3-7, 10117 Berlin
> > > Geschäftsführer: Oskari Saarenmaa & Hannu Valtonen
> > > Amtsgericht Charlottenburg, HRB 209739 B
> > >
> > > On Fri, Jun 14, 2024, 19:25 Colin McCabe  wrote:
> > >
> > > > Hi all,
> > > >
> > > > We have had many delays with releases this year. We should try to get
> > > back
> > > > on schedule.
> > > >
> > > > I agree with the idea that was proposed a few times in this thread of
> > > > drawing a line under 3.8 now, and doing a short 3.9 release. I
> posted a
> > > 3.9
> > > > release plan here:
> > > > https://cwiki.apache.org/confluence/display/KAFKA/Release+Plan+3.9.0
> > > >
> > > > I think we could start doing RCs for 3.8.0 as early as next week.
> There
> > > > are a few things that need to be reverted first (anything related to
> > > > KIP-853 or KIP-966).
> > > >
> > > > Josep, if you agree, I will update KIP-1012 to reflect that these
> things
> > > > are landing in 3.9 rather than 3.8. And we can start doing all the
> normal
> > > > release stuff. The main blocker JIRA I'm aware of is KAFKA-16946,
> which
> > > is
> > > > a very simple fix.
> > > >
> > > > best,
> > > > Colin
> > > >
> > > >
> > > > On Fri, Jun 14, 2024, at 03:48, Satish Duggana wrote:
> > > > > +1 on going with 3.8 release with the existing plan and targeting
> the
> > > > > required features in 3.9 timelines. 4.0 will be targeted in the
> usual
> > > > > cycle(4 months) after 3.9 is released.
> > > > >
> > > > >
> > > > > On Fri, 14 Jun 2024 at 15:19, Edoardo Comar  >
> > > > wrote:
> > > > >>
> > > > >> Josep,
> > > > >> past the deadline sorry but I can't see reasons not to cherry-pick
> > > this
> > > > >> https://github.com/apache/kafka/pull/16326
> > > > >>
> > > > >> On Wed, 12 Jun 2024 at 17:14, Josep Prat
>  > > >
> > > > wrote:
> > > > >> >
> > > > >> > Hi Edoardo,
> > > > >> >
> > > > >> > Correct, you can still cherry-pick this one.
> > > > >> >
> > > > >> > I'll send an email tomorrow morning (CEST) asking maintainers to
> > > stop
> > > > >> > cherry picking commits unless we discuss it beforehand.
> > > > >> >
> > > > >> > Best,
> > > > >> >
> > > > >> > On Wed, Jun 12, 2024 at 6:09 PM Edoardo Comar <
> > > edoardli...@gmail.com>
> > > > wrote:
> > > > >> >
> > > > >> > > Hi Josep, I understand I am still in time to cherry-pick on
> 3.8.0
> > > > >> > > https://github.com/apache/kafka/pull/16229
> > > > >> > >
> > > > >> > > right?
> > > > >> > > thanks
> > > > >> > >
> > > > >> > > On Wed, 12 Jun 2024 at 11:34, Ivan Yurchenko 
> > > > wrote:
> > > > >> > > >
> > > > >> > > > Hi,
> > > > >> > > >
> > > > >> > > > I'll try to do all the fixes and changes for KIP-899 [1]
> sooner
> > > > today,
> > > > >> > > but please proceed with the release if I don't manage.
> > > > >> > > >
> > > > >> > > > Ivan
> > > > >> > > >
> > > > >> > > > [1] https://github.com/apache/kafka/pull/13277
> > > > >> > > >
> > > > >> > > > On Wed, Jun 12, 2024, at 12:54, Josep Prat wrote:
> > > > >> > > > > Hi Luke,
> > > > >> > > > > I think Jose, also mentioned that it won't be ready for
> v3.8.0
> > > > (but he
> > > > >> > > can
> > > > >> > > > > confirm this). My question now would be, given that it
> seems
> > > we
> > > > would
> > > > >> > > need
> > > > >> > > > > a v3.9.0, do you think it's important to include
> > > > >> > > > > https://github.com/apache/kafka/pull/16284 in v3.8.0?
> > > > >> > > > >
> > > > >> > > > > Best,
> > > > >> > > > >
> > > > >> > > > > On Wed, Jun 12, 2024 at 11:40 AM Luke Chen <
> show...@gmail.com
> > > >

Re: [DISCUSS] Apache Kafka 3.8.0 release

[José Armando García Sancio]

+1 on the proposed release plan for 3.8.

Thanks!

On Fri, Jun 14, 2024 at 3:33 PM Ismael Juma  wrote:
>
> +1 to the plan we converged on in this thread.
>
> Ismael
>
> On Fri, Jun 14, 2024 at 10:46 AM Josep Prat 
> wrote:
>
> > Hi all,
> >
> > Thanks Colin, yes go ahead.
> >
> > As we are now past code freeze I would like to ask everyone involved in a
> > KIP that is not yet complete, to verify if what landed on the 3.8 branch
> > needs to be reverted or if it can stay. Additionally, I'll be pinging KIPs
> > and Jira reporters asking for their status as some Jiras seem to have all
> > related GitHub PRs merged but their status is still Open or In Progress.
> > I'll be checking all the open blockers and check if they are really a
> > blocker or can be pushed.
> >
> >
> > Regarding timeline, I'll attempt to generate the first RC on Wednesday or
> > Thursday, so please revert any changes you deem necessary by then. If you
> > need more time, please ping me.
> >
> > Best,
> >
> > -
> > Josep Prat
> > Open Source Engineering Director, Aiven
> > josep.p...@aiven.io   |   +491715557497 | aiven.io
> > Aiven Deutschland GmbH
> > Alexanderufer 3-7, 10117 Berlin
> > Geschäftsführer: Oskari Saarenmaa & Hannu Valtonen
> > Amtsgericht Charlottenburg, HRB 209739 B
> >
> > On Fri, Jun 14, 2024, 19:25 Colin McCabe  wrote:
> >
> > > Hi all,
> > >
> > > We have had many delays with releases this year. We should try to get
> > back
> > > on schedule.
> > >
> > > I agree with the idea that was proposed a few times in this thread of
> > > drawing a line under 3.8 now, and doing a short 3.9 release. I posted a
> > 3.9
> > > release plan here:
> > > https://cwiki.apache.org/confluence/display/KAFKA/Release+Plan+3.9.0
> > >
> > > I think we could start doing RCs for 3.8.0 as early as next week. There
> > > are a few things that need to be reverted first (anything related to
> > > KIP-853 or KIP-966).
> > >
> > > Josep, if you agree, I will update KIP-1012 to reflect that these things
> > > are landing in 3.9 rather than 3.8. And we can start doing all the normal
> > > release stuff. The main blocker JIRA I'm aware of is KAFKA-16946, which
> > is
> > > a very simple fix.
> > >
> > > best,
> > > Colin
> > >
> > >
> > > On Fri, Jun 14, 2024, at 03:48, Satish Duggana wrote:
> > > > +1 on going with 3.8 release with the existing plan and targeting the
> > > > required features in 3.9 timelines. 4.0 will be targeted in the usual
> > > > cycle(4 months) after 3.9 is released.
> > > >
> > > >
> > > > On Fri, 14 Jun 2024 at 15:19, Edoardo Comar 
> > > wrote:
> > > >>
> > > >> Josep,
> > > >> past the deadline sorry but I can't see reasons not to cherry-pick
> > this
> > > >> https://github.com/apache/kafka/pull/16326
> > > >>
> > > >> On Wed, 12 Jun 2024 at 17:14, Josep Prat  > >
> > > wrote:
> > > >> >
> > > >> > Hi Edoardo,
> > > >> >
> > > >> > Correct, you can still cherry-pick this one.
> > > >> >
> > > >> > I'll send an email tomorrow morning (CEST) asking maintainers to
> > stop
> > > >> > cherry picking commits unless we discuss it beforehand.
> > > >> >
> > > >> > Best,
> > > >> >
> > > >> > On Wed, Jun 12, 2024 at 6:09 PM Edoardo Comar <
> > edoardli...@gmail.com>
> > > wrote:
> > > >> >
> > > >> > > Hi Josep, I understand I am still in time to cherry-pick on 3.8.0
> > > >> > > https://github.com/apache/kafka/pull/16229
> > > >> > >
> > > >> > > right?
> > > >> > > thanks
> > > >> > >
> > > >> > > On Wed, 12 Jun 2024 at 11:34, Ivan Yurchenko 
> > > wrote:
> > > >> > > >
> > > >> > > > Hi,
> > > >> > > >
> > > >> > > > I'll try to do all the fixes and changes for KIP-899 [1] sooner
> > > today,
> > > >> > > but please proceed with the release if I don't manage.
> > > >> > > >
> > > >> > > > Ivan
> > > >> > > >
> > > >> > > > [1] https://github.com/apache/kafka/pull/13277
> > > >> > > >
> > > >> > > > On Wed, Jun 12, 2024, at 12:54, Josep Prat wrote:
> > > >> > > > > Hi Luke,
> > > >> > > > > I think Jose, also mentioned that it won't be ready for v3.8.0
> > > (but he
> > > >> > > can
> > > >> > > > > confirm this). My question now would be, given that it seems
> > we
> > > would
> > > >> > > need
> > > >> > > > > a v3.9.0, do you think it's important to include
> > > >> > > > > https://github.com/apache/kafka/pull/16284 in v3.8.0?
> > > >> > > > >
> > > >> > > > > Best,
> > > >> > > > >
> > > >> > > > > On Wed, Jun 12, 2024 at 11:40 AM Luke Chen  > >
> > > wrote:
> > > >> > > > >
> > > >> > > > > > Hi Josep
> > > >> > > > > >
> > > >> > > > > > For KIP-966, I think Calvin had mentioned he won't complete
> > in
> > > >> > > v3.8.0.
> > > >> > > > > >
> > > https://lists.apache.org/thread/fsnr8wy5fznzfso7jgk90skgyo277fmw
> > > >> > > > > >
> > > >> > > > > > For unclean leader election, all we need is this PR:
> > > >> > > > > > https://github.com/apache/kafka/pull/16284
> > > >> > > > > > For this PR, I think it needs one more week to be completed.
> > > >> > > > > >
> > > >> > > > > > Thanks.
> > > >> > > > > > 

Re: [DISCUSS] Apache Kafka 3.8.0 release

[Ismael Juma]

+1 to the plan we converged on in this thread.

Ismael

On Fri, Jun 14, 2024 at 10:46 AM Josep Prat 
wrote:

> Hi all,
>
> Thanks Colin, yes go ahead.
>
> As we are now past code freeze I would like to ask everyone involved in a
> KIP that is not yet complete, to verify if what landed on the 3.8 branch
> needs to be reverted or if it can stay. Additionally, I'll be pinging KIPs
> and Jira reporters asking for their status as some Jiras seem to have all
> related GitHub PRs merged but their status is still Open or In Progress.
> I'll be checking all the open blockers and check if they are really a
> blocker or can be pushed.
>
>
> Regarding timeline, I'll attempt to generate the first RC on Wednesday or
> Thursday, so please revert any changes you deem necessary by then. If you
> need more time, please ping me.
>
> Best,
>
> -
> Josep Prat
> Open Source Engineering Director, Aiven
> josep.p...@aiven.io   |   +491715557497 | aiven.io
> Aiven Deutschland GmbH
> Alexanderufer 3-7, 10117 Berlin
> Geschäftsführer: Oskari Saarenmaa & Hannu Valtonen
> Amtsgericht Charlottenburg, HRB 209739 B
>
> On Fri, Jun 14, 2024, 19:25 Colin McCabe  wrote:
>
> > Hi all,
> >
> > We have had many delays with releases this year. We should try to get
> back
> > on schedule.
> >
> > I agree with the idea that was proposed a few times in this thread of
> > drawing a line under 3.8 now, and doing a short 3.9 release. I posted a
> 3.9
> > release plan here:
> > https://cwiki.apache.org/confluence/display/KAFKA/Release+Plan+3.9.0
> >
> > I think we could start doing RCs for 3.8.0 as early as next week. There
> > are a few things that need to be reverted first (anything related to
> > KIP-853 or KIP-966).
> >
> > Josep, if you agree, I will update KIP-1012 to reflect that these things
> > are landing in 3.9 rather than 3.8. And we can start doing all the normal
> > release stuff. The main blocker JIRA I'm aware of is KAFKA-16946, which
> is
> > a very simple fix.
> >
> > best,
> > Colin
> >
> >
> > On Fri, Jun 14, 2024, at 03:48, Satish Duggana wrote:
> > > +1 on going with 3.8 release with the existing plan and targeting the
> > > required features in 3.9 timelines. 4.0 will be targeted in the usual
> > > cycle(4 months) after 3.9 is released.
> > >
> > >
> > > On Fri, 14 Jun 2024 at 15:19, Edoardo Comar 
> > wrote:
> > >>
> > >> Josep,
> > >> past the deadline sorry but I can't see reasons not to cherry-pick
> this
> > >> https://github.com/apache/kafka/pull/16326
> > >>
> > >> On Wed, 12 Jun 2024 at 17:14, Josep Prat  >
> > wrote:
> > >> >
> > >> > Hi Edoardo,
> > >> >
> > >> > Correct, you can still cherry-pick this one.
> > >> >
> > >> > I'll send an email tomorrow morning (CEST) asking maintainers to
> stop
> > >> > cherry picking commits unless we discuss it beforehand.
> > >> >
> > >> > Best,
> > >> >
> > >> > On Wed, Jun 12, 2024 at 6:09 PM Edoardo Comar <
> edoardli...@gmail.com>
> > wrote:
> > >> >
> > >> > > Hi Josep, I understand I am still in time to cherry-pick on 3.8.0
> > >> > > https://github.com/apache/kafka/pull/16229
> > >> > >
> > >> > > right?
> > >> > > thanks
> > >> > >
> > >> > > On Wed, 12 Jun 2024 at 11:34, Ivan Yurchenko 
> > wrote:
> > >> > > >
> > >> > > > Hi,
> > >> > > >
> > >> > > > I'll try to do all the fixes and changes for KIP-899 [1] sooner
> > today,
> > >> > > but please proceed with the release if I don't manage.
> > >> > > >
> > >> > > > Ivan
> > >> > > >
> > >> > > > [1] https://github.com/apache/kafka/pull/13277
> > >> > > >
> > >> > > > On Wed, Jun 12, 2024, at 12:54, Josep Prat wrote:
> > >> > > > > Hi Luke,
> > >> > > > > I think Jose, also mentioned that it won't be ready for v3.8.0
> > (but he
> > >> > > can
> > >> > > > > confirm this). My question now would be, given that it seems
> we
> > would
> > >> > > need
> > >> > > > > a v3.9.0, do you think it's important to include
> > >> > > > > https://github.com/apache/kafka/pull/16284 in v3.8.0?
> > >> > > > >
> > >> > > > > Best,
> > >> > > > >
> > >> > > > > On Wed, Jun 12, 2024 at 11:40 AM Luke Chen  >
> > wrote:
> > >> > > > >
> > >> > > > > > Hi Josep
> > >> > > > > >
> > >> > > > > > For KIP-966, I think Calvin had mentioned he won't complete
> in
> > >> > > v3.8.0.
> > >> > > > > >
> > https://lists.apache.org/thread/fsnr8wy5fznzfso7jgk90skgyo277fmw
> > >> > > > > >
> > >> > > > > > For unclean leader election, all we need is this PR:
> > >> > > > > > https://github.com/apache/kafka/pull/16284
> > >> > > > > > For this PR, I think it needs one more week to be completed.
> > >> > > > > >
> > >> > > > > > Thanks.
> > >> > > > > > Luke
> > >> > > > > >
> > >> > > > > > On Wed, Jun 12, 2024 at 4:51 PM Josep Prat
> > >> > > 
> > >> > > > > > wrote:
> > >> > > > > >
> > >> > > > > > > Hi all,
> > >> > > > > > >
> > >> > > > > > > We are now really close to the planned code freeze
> deadline
> > (today
> > >> > > EOD).
> > >> > > > > > > According to KIP-1012 [1] we agreed to stay in the 3.x
> > branch
> > >> > > until we

Re: [DISCUSS] Apache Kafka 3.8.0 release

[Josep Prat]

Hi all,

Thanks Colin, yes go ahead.

As we are now past code freeze I would like to ask everyone involved in a
KIP that is not yet complete, to verify if what landed on the 3.8 branch
needs to be reverted or if it can stay. Additionally, I'll be pinging KIPs
and Jira reporters asking for their status as some Jiras seem to have all
related GitHub PRs merged but their status is still Open or In Progress.
I'll be checking all the open blockers and check if they are really a
blocker or can be pushed.


Regarding timeline, I'll attempt to generate the first RC on Wednesday or
Thursday, so please revert any changes you deem necessary by then. If you
need more time, please ping me.

Best,

-
Josep Prat
Open Source Engineering Director, Aiven
josep.p...@aiven.io   |   +491715557497 | aiven.io
Aiven Deutschland GmbH
Alexanderufer 3-7, 10117 Berlin
Geschäftsführer: Oskari Saarenmaa & Hannu Valtonen
Amtsgericht Charlottenburg, HRB 209739 B

On Fri, Jun 14, 2024, 19:25 Colin McCabe  wrote:

> Hi all,
>
> We have had many delays with releases this year. We should try to get back
> on schedule.
>
> I agree with the idea that was proposed a few times in this thread of
> drawing a line under 3.8 now, and doing a short 3.9 release. I posted a 3.9
> release plan here:
> https://cwiki.apache.org/confluence/display/KAFKA/Release+Plan+3.9.0
>
> I think we could start doing RCs for 3.8.0 as early as next week. There
> are a few things that need to be reverted first (anything related to
> KIP-853 or KIP-966).
>
> Josep, if you agree, I will update KIP-1012 to reflect that these things
> are landing in 3.9 rather than 3.8. And we can start doing all the normal
> release stuff. The main blocker JIRA I'm aware of is KAFKA-16946, which is
> a very simple fix.
>
> best,
> Colin
>
>
> On Fri, Jun 14, 2024, at 03:48, Satish Duggana wrote:
> > +1 on going with 3.8 release with the existing plan and targeting the
> > required features in 3.9 timelines. 4.0 will be targeted in the usual
> > cycle(4 months) after 3.9 is released.
> >
> >
> > On Fri, 14 Jun 2024 at 15:19, Edoardo Comar 
> wrote:
> >>
> >> Josep,
> >> past the deadline sorry but I can't see reasons not to cherry-pick this
> >> https://github.com/apache/kafka/pull/16326
> >>
> >> On Wed, 12 Jun 2024 at 17:14, Josep Prat 
> wrote:
> >> >
> >> > Hi Edoardo,
> >> >
> >> > Correct, you can still cherry-pick this one.
> >> >
> >> > I'll send an email tomorrow morning (CEST) asking maintainers to stop
> >> > cherry picking commits unless we discuss it beforehand.
> >> >
> >> > Best,
> >> >
> >> > On Wed, Jun 12, 2024 at 6:09 PM Edoardo Comar 
> wrote:
> >> >
> >> > > Hi Josep, I understand I am still in time to cherry-pick on 3.8.0
> >> > > https://github.com/apache/kafka/pull/16229
> >> > >
> >> > > right?
> >> > > thanks
> >> > >
> >> > > On Wed, 12 Jun 2024 at 11:34, Ivan Yurchenko 
> wrote:
> >> > > >
> >> > > > Hi,
> >> > > >
> >> > > > I'll try to do all the fixes and changes for KIP-899 [1] sooner
> today,
> >> > > but please proceed with the release if I don't manage.
> >> > > >
> >> > > > Ivan
> >> > > >
> >> > > > [1] https://github.com/apache/kafka/pull/13277
> >> > > >
> >> > > > On Wed, Jun 12, 2024, at 12:54, Josep Prat wrote:
> >> > > > > Hi Luke,
> >> > > > > I think Jose, also mentioned that it won't be ready for v3.8.0
> (but he
> >> > > can
> >> > > > > confirm this). My question now would be, given that it seems we
> would
> >> > > need
> >> > > > > a v3.9.0, do you think it's important to include
> >> > > > > https://github.com/apache/kafka/pull/16284 in v3.8.0?
> >> > > > >
> >> > > > > Best,
> >> > > > >
> >> > > > > On Wed, Jun 12, 2024 at 11:40 AM Luke Chen 
> wrote:
> >> > > > >
> >> > > > > > Hi Josep
> >> > > > > >
> >> > > > > > For KIP-966, I think Calvin had mentioned he won't complete in
> >> > > v3.8.0.
> >> > > > > >
> https://lists.apache.org/thread/fsnr8wy5fznzfso7jgk90skgyo277fmw
> >> > > > > >
> >> > > > > > For unclean leader election, all we need is this PR:
> >> > > > > > https://github.com/apache/kafka/pull/16284
> >> > > > > > For this PR, I think it needs one more week to be completed.
> >> > > > > >
> >> > > > > > Thanks.
> >> > > > > > Luke
> >> > > > > >
> >> > > > > > On Wed, Jun 12, 2024 at 4:51 PM Josep Prat
> >> > > 
> >> > > > > > wrote:
> >> > > > > >
> >> > > > > > > Hi all,
> >> > > > > > >
> >> > > > > > > We are now really close to the planned code freeze deadline
> (today
> >> > > EOD).
> >> > > > > > > According to KIP-1012 [1] we agreed to stay in the 3.x
> branch
> >> > > until we
> >> > > > > > > achieve feature parity regarding Zookeeper and KRaft. The
> two main
> >> > > KIPs
> >> > > > > > > identified that would achieve this are: KIP-853 [2] and
> KIP-966
> >> > > [3].
> >> > > > > > > At the moment of writing this email both KIPs are not
> completed. My
> >> > > > > > > question to the people driving both KIPs would be, how much
> more
> >> > > time do
> >> > > > > > > you think it's needed to 

Re: [DISCUSS] Apache Kafka 3.8.0 release

[Colin McCabe]

Hi all,

We have had many delays with releases this year. We should try to get back on 
schedule.

I agree with the idea that was proposed a few times in this thread of drawing a 
line under 3.8 now, and doing a short 3.9 release. I posted a 3.9 release plan 
here: https://cwiki.apache.org/confluence/display/KAFKA/Release+Plan+3.9.0

I think we could start doing RCs for 3.8.0 as early as next week. There are a 
few things that need to be reverted first (anything related to KIP-853 or 
KIP-966).

Josep, if you agree, I will update KIP-1012 to reflect that these things are 
landing in 3.9 rather than 3.8. And we can start doing all the normal release 
stuff. The main blocker JIRA I'm aware of is KAFKA-16946, which is a very 
simple fix.

best,
Colin


On Fri, Jun 14, 2024, at 03:48, Satish Duggana wrote:
> +1 on going with 3.8 release with the existing plan and targeting the
> required features in 3.9 timelines. 4.0 will be targeted in the usual
> cycle(4 months) after 3.9 is released.
>
>
> On Fri, 14 Jun 2024 at 15:19, Edoardo Comar  wrote:
>>
>> Josep,
>> past the deadline sorry but I can't see reasons not to cherry-pick this
>> https://github.com/apache/kafka/pull/16326
>>
>> On Wed, 12 Jun 2024 at 17:14, Josep Prat  wrote:
>> >
>> > Hi Edoardo,
>> >
>> > Correct, you can still cherry-pick this one.
>> >
>> > I'll send an email tomorrow morning (CEST) asking maintainers to stop
>> > cherry picking commits unless we discuss it beforehand.
>> >
>> > Best,
>> >
>> > On Wed, Jun 12, 2024 at 6:09 PM Edoardo Comar  
>> > wrote:
>> >
>> > > Hi Josep, I understand I am still in time to cherry-pick on 3.8.0
>> > > https://github.com/apache/kafka/pull/16229
>> > >
>> > > right?
>> > > thanks
>> > >
>> > > On Wed, 12 Jun 2024 at 11:34, Ivan Yurchenko  wrote:
>> > > >
>> > > > Hi,
>> > > >
>> > > > I'll try to do all the fixes and changes for KIP-899 [1] sooner today,
>> > > but please proceed with the release if I don't manage.
>> > > >
>> > > > Ivan
>> > > >
>> > > > [1] https://github.com/apache/kafka/pull/13277
>> > > >
>> > > > On Wed, Jun 12, 2024, at 12:54, Josep Prat wrote:
>> > > > > Hi Luke,
>> > > > > I think Jose, also mentioned that it won't be ready for v3.8.0 (but 
>> > > > > he
>> > > can
>> > > > > confirm this). My question now would be, given that it seems we would
>> > > need
>> > > > > a v3.9.0, do you think it's important to include
>> > > > > https://github.com/apache/kafka/pull/16284 in v3.8.0?
>> > > > >
>> > > > > Best,
>> > > > >
>> > > > > On Wed, Jun 12, 2024 at 11:40 AM Luke Chen  wrote:
>> > > > >
>> > > > > > Hi Josep
>> > > > > >
>> > > > > > For KIP-966, I think Calvin had mentioned he won't complete in
>> > > v3.8.0.
>> > > > > > https://lists.apache.org/thread/fsnr8wy5fznzfso7jgk90skgyo277fmw
>> > > > > >
>> > > > > > For unclean leader election, all we need is this PR:
>> > > > > > https://github.com/apache/kafka/pull/16284
>> > > > > > For this PR, I think it needs one more week to be completed.
>> > > > > >
>> > > > > > Thanks.
>> > > > > > Luke
>> > > > > >
>> > > > > > On Wed, Jun 12, 2024 at 4:51 PM Josep Prat
>> > > 
>> > > > > > wrote:
>> > > > > >
>> > > > > > > Hi all,
>> > > > > > >
>> > > > > > > We are now really close to the planned code freeze deadline 
>> > > > > > > (today
>> > > EOD).
>> > > > > > > According to KIP-1012 [1] we agreed to stay in the 3.x branch
>> > > until we
>> > > > > > > achieve feature parity regarding Zookeeper and KRaft. The two 
>> > > > > > > main
>> > > KIPs
>> > > > > > > identified that would achieve this are: KIP-853 [2] and KIP-966
>> > > [3].
>> > > > > > > At the moment of writing this email both KIPs are not completed. 
>> > > > > > > My
>> > > > > > > question to the people driving both KIPs would be, how much more
>> > > time do
>> > > > > > > you think it's needed to bring these KIPs to completion?
>> > > > > > >
>> > > > > > > - If the time needed would be short, we could still include these
>> > > 2 KIPs
>> > > > > > in
>> > > > > > > the release.
>> > > > > > > - However, if the time needed would be on the scale of weeks, we
>> > > should
>> > > > > > > continue with the release plan for 3.8 and after start working on
>> > > the 3.9
>> > > > > > > release.
>> > > > > > >
>> > > > > > > What are your thoughts?
>> > > > > > >
>> > > > > > >
>> > > > > > > [1]:
>> > > > > > >
>> > > > > > >
>> > > > > >
>> > > https://cwiki.apache.org/confluence/display/KAFKA/KIP-1012%3A+The+need+for+a+Kafka+3.8.x+release
>> > > > > > > [2]:
>> > > > > > >
>> > > > > > >
>> > > > > >
>> > > https://cwiki.apache.org/confluence/display/KAFKA/KIP-853%3A+KRaft+Controller+Membership+Changes
>> > > > > > > [3]:
>> > > > > > >
>> > > > > > >
>> > > > > >
>> > > https://cwiki.apache.org/confluence/display/KAFKA/KIP-966%3A+Eligible+Leader+Replicas
>> > > > > > >
>> > > > > > > On Wed, Jun 12, 2024 at 10:40 AM Josep Prat 
>> > > wrote:
>> > > > > > >
>> > > > > > > > Hi Rajini,
>> > > > > > > > Yes, we could backport this one to the 3.8 branch. Would 

Re: [DISCUSS] Apache Kafka 3.8.0 release

[Satish Duggana]

+1 on going with 3.8 release with the existing plan and targeting the
required features in 3.9 timelines. 4.0 will be targeted in the usual
cycle(4 months) after 3.9 is released.


On Fri, 14 Jun 2024 at 15:19, Edoardo Comar  wrote:
>
> Josep,
> past the deadline sorry but I can't see reasons not to cherry-pick this
> https://github.com/apache/kafka/pull/16326
>
> On Wed, 12 Jun 2024 at 17:14, Josep Prat  wrote:
> >
> > Hi Edoardo,
> >
> > Correct, you can still cherry-pick this one.
> >
> > I'll send an email tomorrow morning (CEST) asking maintainers to stop
> > cherry picking commits unless we discuss it beforehand.
> >
> > Best,
> >
> > On Wed, Jun 12, 2024 at 6:09 PM Edoardo Comar  wrote:
> >
> > > Hi Josep, I understand I am still in time to cherry-pick on 3.8.0
> > > https://github.com/apache/kafka/pull/16229
> > >
> > > right?
> > > thanks
> > >
> > > On Wed, 12 Jun 2024 at 11:34, Ivan Yurchenko  wrote:
> > > >
> > > > Hi,
> > > >
> > > > I'll try to do all the fixes and changes for KIP-899 [1] sooner today,
> > > but please proceed with the release if I don't manage.
> > > >
> > > > Ivan
> > > >
> > > > [1] https://github.com/apache/kafka/pull/13277
> > > >
> > > > On Wed, Jun 12, 2024, at 12:54, Josep Prat wrote:
> > > > > Hi Luke,
> > > > > I think Jose, also mentioned that it won't be ready for v3.8.0 (but he
> > > can
> > > > > confirm this). My question now would be, given that it seems we would
> > > need
> > > > > a v3.9.0, do you think it's important to include
> > > > > https://github.com/apache/kafka/pull/16284 in v3.8.0?
> > > > >
> > > > > Best,
> > > > >
> > > > > On Wed, Jun 12, 2024 at 11:40 AM Luke Chen  wrote:
> > > > >
> > > > > > Hi Josep
> > > > > >
> > > > > > For KIP-966, I think Calvin had mentioned he won't complete in
> > > v3.8.0.
> > > > > > https://lists.apache.org/thread/fsnr8wy5fznzfso7jgk90skgyo277fmw
> > > > > >
> > > > > > For unclean leader election, all we need is this PR:
> > > > > > https://github.com/apache/kafka/pull/16284
> > > > > > For this PR, I think it needs one more week to be completed.
> > > > > >
> > > > > > Thanks.
> > > > > > Luke
> > > > > >
> > > > > > On Wed, Jun 12, 2024 at 4:51 PM Josep Prat
> > > 
> > > > > > wrote:
> > > > > >
> > > > > > > Hi all,
> > > > > > >
> > > > > > > We are now really close to the planned code freeze deadline (today
> > > EOD).
> > > > > > > According to KIP-1012 [1] we agreed to stay in the 3.x branch
> > > until we
> > > > > > > achieve feature parity regarding Zookeeper and KRaft. The two main
> > > KIPs
> > > > > > > identified that would achieve this are: KIP-853 [2] and KIP-966
> > > [3].
> > > > > > > At the moment of writing this email both KIPs are not completed. 
> > > > > > > My
> > > > > > > question to the people driving both KIPs would be, how much more
> > > time do
> > > > > > > you think it's needed to bring these KIPs to completion?
> > > > > > >
> > > > > > > - If the time needed would be short, we could still include these
> > > 2 KIPs
> > > > > > in
> > > > > > > the release.
> > > > > > > - However, if the time needed would be on the scale of weeks, we
> > > should
> > > > > > > continue with the release plan for 3.8 and after start working on
> > > the 3.9
> > > > > > > release.
> > > > > > >
> > > > > > > What are your thoughts?
> > > > > > >
> > > > > > >
> > > > > > > [1]:
> > > > > > >
> > > > > > >
> > > > > >
> > > https://cwiki.apache.org/confluence/display/KAFKA/KIP-1012%3A+The+need+for+a+Kafka+3.8.x+release
> > > > > > > [2]:
> > > > > > >
> > > > > > >
> > > > > >
> > > https://cwiki.apache.org/confluence/display/KAFKA/KIP-853%3A+KRaft+Controller+Membership+Changes
> > > > > > > [3]:
> > > > > > >
> > > > > > >
> > > > > >
> > > https://cwiki.apache.org/confluence/display/KAFKA/KIP-966%3A+Eligible+Leader+Replicas
> > > > > > >
> > > > > > > On Wed, Jun 12, 2024 at 10:40 AM Josep Prat 
> > > wrote:
> > > > > > >
> > > > > > > > Hi Rajini,
> > > > > > > > Yes, we could backport this one to the 3.8 branch. Would you be
> > > able to
> > > > > > > do
> > > > > > > > this once you merge this PR?
> > > > > > > >
> > > > > > > > Thanks
> > > > > > > >
> > > > > > > > On Tue, Jun 11, 2024 at 10:53 PM Rajini Sivaram <
> > > > > > rajinisiva...@gmail.com
> > > > > > > >
> > > > > > > > wrote:
> > > > > > > >
> > > > > > > >> Hi Josep,
> > > > > > > >>
> > > > > > > >> The PR https://github.com/apache/kafka/pull/13277 for KIP-899
> > > looks
> > > > > > > ready
> > > > > > > >> to be merged (waiting for the PR build).The PR changes several
> > > files,
> > > > > > > but
> > > > > > > >> is relatively straightforward and not risky. Also the changes
> > > are
> > > > > > under
> > > > > > > a
> > > > > > > >> config that is not enabled by default. Since the KIP was
> > > approved
> > > > > > before
> > > > > > > >> KIP freeze, will it be ok to include in 3.8.0?
> > > > > > > >>
> > > > > > > >> Thank you,
> > > > > > > >>
> > > > > > > >> Rajini
> > > > > > > >>
> > > > > > > >>
> > > > > > > 

Re: [DISCUSS] Apache Kafka 3.8.0 release

[Edoardo Comar]

Josep,
past the deadline sorry but I can't see reasons not to cherry-pick this
https://github.com/apache/kafka/pull/16326

On Wed, 12 Jun 2024 at 17:14, Josep Prat  wrote:
>
> Hi Edoardo,
>
> Correct, you can still cherry-pick this one.
>
> I'll send an email tomorrow morning (CEST) asking maintainers to stop
> cherry picking commits unless we discuss it beforehand.
>
> Best,
>
> On Wed, Jun 12, 2024 at 6:09 PM Edoardo Comar  wrote:
>
> > Hi Josep, I understand I am still in time to cherry-pick on 3.8.0
> > https://github.com/apache/kafka/pull/16229
> >
> > right?
> > thanks
> >
> > On Wed, 12 Jun 2024 at 11:34, Ivan Yurchenko  wrote:
> > >
> > > Hi,
> > >
> > > I'll try to do all the fixes and changes for KIP-899 [1] sooner today,
> > but please proceed with the release if I don't manage.
> > >
> > > Ivan
> > >
> > > [1] https://github.com/apache/kafka/pull/13277
> > >
> > > On Wed, Jun 12, 2024, at 12:54, Josep Prat wrote:
> > > > Hi Luke,
> > > > I think Jose, also mentioned that it won't be ready for v3.8.0 (but he
> > can
> > > > confirm this). My question now would be, given that it seems we would
> > need
> > > > a v3.9.0, do you think it's important to include
> > > > https://github.com/apache/kafka/pull/16284 in v3.8.0?
> > > >
> > > > Best,
> > > >
> > > > On Wed, Jun 12, 2024 at 11:40 AM Luke Chen  wrote:
> > > >
> > > > > Hi Josep
> > > > >
> > > > > For KIP-966, I think Calvin had mentioned he won't complete in
> > v3.8.0.
> > > > > https://lists.apache.org/thread/fsnr8wy5fznzfso7jgk90skgyo277fmw
> > > > >
> > > > > For unclean leader election, all we need is this PR:
> > > > > https://github.com/apache/kafka/pull/16284
> > > > > For this PR, I think it needs one more week to be completed.
> > > > >
> > > > > Thanks.
> > > > > Luke
> > > > >
> > > > > On Wed, Jun 12, 2024 at 4:51 PM Josep Prat
> > 
> > > > > wrote:
> > > > >
> > > > > > Hi all,
> > > > > >
> > > > > > We are now really close to the planned code freeze deadline (today
> > EOD).
> > > > > > According to KIP-1012 [1] we agreed to stay in the 3.x branch
> > until we
> > > > > > achieve feature parity regarding Zookeeper and KRaft. The two main
> > KIPs
> > > > > > identified that would achieve this are: KIP-853 [2] and KIP-966
> > [3].
> > > > > > At the moment of writing this email both KIPs are not completed. My
> > > > > > question to the people driving both KIPs would be, how much more
> > time do
> > > > > > you think it's needed to bring these KIPs to completion?
> > > > > >
> > > > > > - If the time needed would be short, we could still include these
> > 2 KIPs
> > > > > in
> > > > > > the release.
> > > > > > - However, if the time needed would be on the scale of weeks, we
> > should
> > > > > > continue with the release plan for 3.8 and after start working on
> > the 3.9
> > > > > > release.
> > > > > >
> > > > > > What are your thoughts?
> > > > > >
> > > > > >
> > > > > > [1]:
> > > > > >
> > > > > >
> > > > >
> > https://cwiki.apache.org/confluence/display/KAFKA/KIP-1012%3A+The+need+for+a+Kafka+3.8.x+release
> > > > > > [2]:
> > > > > >
> > > > > >
> > > > >
> > https://cwiki.apache.org/confluence/display/KAFKA/KIP-853%3A+KRaft+Controller+Membership+Changes
> > > > > > [3]:
> > > > > >
> > > > > >
> > > > >
> > https://cwiki.apache.org/confluence/display/KAFKA/KIP-966%3A+Eligible+Leader+Replicas
> > > > > >
> > > > > > On Wed, Jun 12, 2024 at 10:40 AM Josep Prat 
> > wrote:
> > > > > >
> > > > > > > Hi Rajini,
> > > > > > > Yes, we could backport this one to the 3.8 branch. Would you be
> > able to
> > > > > > do
> > > > > > > this once you merge this PR?
> > > > > > >
> > > > > > > Thanks
> > > > > > >
> > > > > > > On Tue, Jun 11, 2024 at 10:53 PM Rajini Sivaram <
> > > > > rajinisiva...@gmail.com
> > > > > > >
> > > > > > > wrote:
> > > > > > >
> > > > > > >> Hi Josep,
> > > > > > >>
> > > > > > >> The PR https://github.com/apache/kafka/pull/13277 for KIP-899
> > looks
> > > > > > ready
> > > > > > >> to be merged (waiting for the PR build).The PR changes several
> > files,
> > > > > > but
> > > > > > >> is relatively straightforward and not risky. Also the changes
> > are
> > > > > under
> > > > > > a
> > > > > > >> config that is not enabled by default. Since the KIP was
> > approved
> > > > > before
> > > > > > >> KIP freeze, will it be ok to include in 3.8.0?
> > > > > > >>
> > > > > > >> Thank you,
> > > > > > >>
> > > > > > >> Rajini
> > > > > > >>
> > > > > > >>
> > > > > > >> On Tue, Jun 11, 2024 at 9:35 AM Josep Prat
> > > > >  > > > > > >
> > > > > > >> wrote:
> > > > > > >>
> > > > > > >> > Hi all,
> > > > > > >> >
> > > > > > >> > I just want to remind everybody that the code freeze deadline
> > is
> > > > > > >> > approaching. June 12th EOD is the deadline.
> > > > > > >> >
> > > > > > >> > Please do not automatically backport any commit to the 3.8
> > branch
> > > > > > after
> > > > > > >> > June 12th EOD. Ping me if you think the commit should be
> > backported
> > > > > > >> (fixes
> > > > > > >> > 

Re: [DISCUSS] Apache Kafka 3.8.0 release

[Luke Chen]

I'm also +1 to have 3.8 release on time, and have a shorter release cycle
for v3.9.
But we have to explicitly define what "shorter release cycle" means.
I agree with Greg's suggestion:
cutting the 3.9 branch immediately after the Kraft KIPS are
feature-complete, or 4 months after the 3.8 release, whichever comes first.

Also, what does that mean to v4.0?
Release 4.0.0: 3 - 4 months after the 3.9 branch is created?

Thanks.
Luke



On Fri, Jun 14, 2024 at 4:32 AM Greg Harris 
wrote:

> Hi Mickael,
>
> I agree +1 to proceeding with the 3.8 release on-time.
>
> I'm fine with cutting the 3.9 branch immediately after the Kraft KIPS are
> feature-complete, or 4 months after the 3.8 release, whichever comes first.
>
> Thanks,
> Greg
>
> On Thu, Jun 13, 2024 at 1:29 PM Mickael Maison 
> wrote:
>
> > Hi,
> >
> > We follow a time based release process precisely to avoid this type of
> > issues.
> > Rushing to complete a feature and merging it just before the release
> > puts pressure on the contributors, and leaves little time to properly
> > test it. Especially on a complex feature like KIP-853.
> >
> > I'd be +1 on releasing 3.8 now and doing a 3.9 release to reach
> > feature parity. If we really want, as Sophie suggested, we could do a
> > shorter cycle for 3.9 before moving onto 4.0.
> >
> > Thanks,
> > Mickael
> >
> > On Thu, Jun 13, 2024 at 10:23 PM Christopher X Bogan
> >  wrote:
> > >
> > > is this where I ask
> > >  to join?
> > >
> > > On Thu, Jun 13, 2024 at 1:20 PM Greg Harris
>  > >
> > > wrote:
> > >
> > > > Hi Sophie and Justine,
> > > >
> > > > I share your concerns about delaying 3.8 in order to give the Kraft
> > KIPs
> > > > more time for implementation. I raised them in the discussion for
> > KIP-1012
> > > > [1]:
> > > >
> > > > > I think there is a
> > > > > risk that features that are on-time and eligible for a 3.8 release
> > > > > could be delayed by some KIPs which are given special treatment.
> > > >
> > > > This situation is exactly why Kafka has standardized on time based
> > releases
> > > > [2], and It is not exceptional for features to slip from releases in
> > order
> > > > to keep the releases on-time, it's a very intentional choice of
> > priorities.
> > > >
> > > > I don't think the situation we're in warrants parallel development,
> and
> > > > I'm uncomfortable with incurring the additional risk to users by
> doing
> > a
> > > > nonstandard release.
> > > > For example, two risks are that 3.9 never happens, or happens much
> > later
> > > > than expected (after 4.1, 4.2, etc). There is a remote chance of
> these
> > > > happening, but we should be prepared if these features get delayed
> > further.
> > > > Users could be left behind waiting for a 3.9 release without an
> upgrade
> > > > path for new features or security updates. I found this to be the
> most
> > > > compelling motivation for KIP-1012, and parallel development doesn't
> > > > address it.
> > > > If the 3.9 release comes out much later, users may be unsafe
> upgrading
> > from
> > > > 3.9 to some 4.x versions, and we would need special notices to
> explain
> > this
> > > > non-linearity in our versions.
> > > >
> > > > Thanks all,
> > > > Greg
> > > >
> > > > [1] https://lists.apache.org/thread/kvdp2gmq5gd9txkvxh5vk3z2n55b04s5
> > > > [2]
> > > >
> >
> https://cwiki.apache.org/confluence/display/KAFKA/Time+Based+Release+Plan
> > > >
> > > > On Thu, Jun 13, 2024 at 1:17 PM Josep Prat
>  > >
> > > > wrote:
> > > >
> > > > > Hi Justine,
> > > > >
> > > > > I know we discarded parallel branching, but it was under the scope
> of
> > > > 3.8.0
> > > > > and with the KIPs no yet approved.
> > > > > We could also not do a parallel release, but rather "quick" 3.9 and
> > then
> > > > > start with 4.0.
> > > > >
> > > > > Best
> > > > > -
> > > > > Josep Prat
> > > > > Open Source Engineering Director, Aiven
> > > > > josep.p...@aiven.io   |   +491715557497 | aiven.io
> > > > > Aiven Deutschland GmbH
> > > > > Alexanderufer 3-7, 10117 Berlin
> > > > > Geschäftsführer: Oskari Saarenmaa & Hannu Valtonen
> > > > > Amtsgericht Charlottenburg, HRB 209739 B
> > > > >
> > > > > On Thu, Jun 13, 2024, 22:08 Josep Prat 
> wrote:
> > > > >
> > > > > > Hi Sophie,
> > > > > >
> > > > > > I have a call tomorrow with José to clarify the estimates for
> > KIP-853.
> > > > > > I also wouldn't like to delay the release for a month or more.
> > > > > >
> > > > > > Regarding your proposal, I find it would be a good way forward,
> +1
> > from
> > > > > my
> > > > > > side.
> > > > > >
> > > > > >
> > > > > > I also find this release and what should include is a hot topic.
> > > > > > What do others think?
> > > > > >
> > > > > > Best,
> > > > > >
> > > > > > 
> > > > > > Josep Prat
> > > > > > Open Source Engineering Director, Aiven josep.p...@aiven.io   |
> > > > > > +491715557497 | aiven.io
> > > > > > Aiven Deutschland GmbH
> > > > > > Alexanderufer 3-7, 10117 Berlin
> > > > > > Geschäftsführer: Oskari 

Re: [DISCUSS] Apache Kafka 3.8.0 release

[Greg Harris]

Hi Mickael,

I agree +1 to proceeding with the 3.8 release on-time.

I'm fine with cutting the 3.9 branch immediately after the Kraft KIPS are
feature-complete, or 4 months after the 3.8 release, whichever comes first.

Thanks,
Greg

On Thu, Jun 13, 2024 at 1:29 PM Mickael Maison 
wrote:

> Hi,
>
> We follow a time based release process precisely to avoid this type of
> issues.
> Rushing to complete a feature and merging it just before the release
> puts pressure on the contributors, and leaves little time to properly
> test it. Especially on a complex feature like KIP-853.
>
> I'd be +1 on releasing 3.8 now and doing a 3.9 release to reach
> feature parity. If we really want, as Sophie suggested, we could do a
> shorter cycle for 3.9 before moving onto 4.0.
>
> Thanks,
> Mickael
>
> On Thu, Jun 13, 2024 at 10:23 PM Christopher X Bogan
>  wrote:
> >
> > is this where I ask
> >  to join?
> >
> > On Thu, Jun 13, 2024 at 1:20 PM Greg Harris  >
> > wrote:
> >
> > > Hi Sophie and Justine,
> > >
> > > I share your concerns about delaying 3.8 in order to give the Kraft
> KIPs
> > > more time for implementation. I raised them in the discussion for
> KIP-1012
> > > [1]:
> > >
> > > > I think there is a
> > > > risk that features that are on-time and eligible for a 3.8 release
> > > > could be delayed by some KIPs which are given special treatment.
> > >
> > > This situation is exactly why Kafka has standardized on time based
> releases
> > > [2], and It is not exceptional for features to slip from releases in
> order
> > > to keep the releases on-time, it's a very intentional choice of
> priorities.
> > >
> > > I don't think the situation we're in warrants parallel development, and
> > > I'm uncomfortable with incurring the additional risk to users by doing
> a
> > > nonstandard release.
> > > For example, two risks are that 3.9 never happens, or happens much
> later
> > > than expected (after 4.1, 4.2, etc). There is a remote chance of these
> > > happening, but we should be prepared if these features get delayed
> further.
> > > Users could be left behind waiting for a 3.9 release without an upgrade
> > > path for new features or security updates. I found this to be the most
> > > compelling motivation for KIP-1012, and parallel development doesn't
> > > address it.
> > > If the 3.9 release comes out much later, users may be unsafe upgrading
> from
> > > 3.9 to some 4.x versions, and we would need special notices to explain
> this
> > > non-linearity in our versions.
> > >
> > > Thanks all,
> > > Greg
> > >
> > > [1] https://lists.apache.org/thread/kvdp2gmq5gd9txkvxh5vk3z2n55b04s5
> > > [2]
> > >
> https://cwiki.apache.org/confluence/display/KAFKA/Time+Based+Release+Plan
> > >
> > > On Thu, Jun 13, 2024 at 1:17 PM Josep Prat  >
> > > wrote:
> > >
> > > > Hi Justine,
> > > >
> > > > I know we discarded parallel branching, but it was under the scope of
> > > 3.8.0
> > > > and with the KIPs no yet approved.
> > > > We could also not do a parallel release, but rather "quick" 3.9 and
> then
> > > > start with 4.0.
> > > >
> > > > Best
> > > > -
> > > > Josep Prat
> > > > Open Source Engineering Director, Aiven
> > > > josep.p...@aiven.io   |   +491715557497 | aiven.io
> > > > Aiven Deutschland GmbH
> > > > Alexanderufer 3-7, 10117 Berlin
> > > > Geschäftsführer: Oskari Saarenmaa & Hannu Valtonen
> > > > Amtsgericht Charlottenburg, HRB 209739 B
> > > >
> > > > On Thu, Jun 13, 2024, 22:08 Josep Prat  wrote:
> > > >
> > > > > Hi Sophie,
> > > > >
> > > > > I have a call tomorrow with José to clarify the estimates for
> KIP-853.
> > > > > I also wouldn't like to delay the release for a month or more.
> > > > >
> > > > > Regarding your proposal, I find it would be a good way forward, +1
> from
> > > > my
> > > > > side.
> > > > >
> > > > >
> > > > > I also find this release and what should include is a hot topic.
> > > > > What do others think?
> > > > >
> > > > > Best,
> > > > >
> > > > > 
> > > > > Josep Prat
> > > > > Open Source Engineering Director, Aiven josep.p...@aiven.io   |
> > > > > +491715557497 | aiven.io
> > > > > Aiven Deutschland GmbH
> > > > > Alexanderufer 3-7, 10117 Berlin
> > > > > Geschäftsführer: Oskari Saarenmaa & Hannu Valtonen
> > > > > Amtsgericht Charlottenburg, HRB 209739 B
> > > > >
> > > > > On Thu, Jun 13, 2024, 21:23 Sophie Blee-Goldman <
> sop...@responsive.dev
> > > >
> > > > > wrote:
> > > > >
> > > > >> Hey all -- was just wondering where we currently stand Re:
> delaying 3.
> > > > for
> > > > >> the KRaft KIPs vs doing a 3.9 release
> > > > >>
> > > > >> I know we don't want to have to wait for a whole release cycle to
> ship
> > > > >> these KRaft features, but delaying 3.8 up to month is also rather
> > > > >> difficult
> > > > >> to swallow. I just wanted to throw an unusual idea out there and
> see
> > > if
> > > > >> this might be a possible compromise, or is out of the question:
> > > > >>
> > > > >> What if we proceed with the 3.8 release as-is, 

Re: [DISCUSS] Apache Kafka 3.8.0 release

[Mickael Maison]

Hi,

We follow a time based release process precisely to avoid this type of issues.
Rushing to complete a feature and merging it just before the release
puts pressure on the contributors, and leaves little time to properly
test it. Especially on a complex feature like KIP-853.

I'd be +1 on releasing 3.8 now and doing a 3.9 release to reach
feature parity. If we really want, as Sophie suggested, we could do a
shorter cycle for 3.9 before moving onto 4.0.

Thanks,
Mickael

On Thu, Jun 13, 2024 at 10:23 PM Christopher X Bogan
 wrote:
>
> is this where I ask
>  to join?
>
> On Thu, Jun 13, 2024 at 1:20 PM Greg Harris 
> wrote:
>
> > Hi Sophie and Justine,
> >
> > I share your concerns about delaying 3.8 in order to give the Kraft KIPs
> > more time for implementation. I raised them in the discussion for KIP-1012
> > [1]:
> >
> > > I think there is a
> > > risk that features that are on-time and eligible for a 3.8 release
> > > could be delayed by some KIPs which are given special treatment.
> >
> > This situation is exactly why Kafka has standardized on time based releases
> > [2], and It is not exceptional for features to slip from releases in order
> > to keep the releases on-time, it's a very intentional choice of priorities.
> >
> > I don't think the situation we're in warrants parallel development, and
> > I'm uncomfortable with incurring the additional risk to users by doing a
> > nonstandard release.
> > For example, two risks are that 3.9 never happens, or happens much later
> > than expected (after 4.1, 4.2, etc). There is a remote chance of these
> > happening, but we should be prepared if these features get delayed further.
> > Users could be left behind waiting for a 3.9 release without an upgrade
> > path for new features or security updates. I found this to be the most
> > compelling motivation for KIP-1012, and parallel development doesn't
> > address it.
> > If the 3.9 release comes out much later, users may be unsafe upgrading from
> > 3.9 to some 4.x versions, and we would need special notices to explain this
> > non-linearity in our versions.
> >
> > Thanks all,
> > Greg
> >
> > [1] https://lists.apache.org/thread/kvdp2gmq5gd9txkvxh5vk3z2n55b04s5
> > [2]
> > https://cwiki.apache.org/confluence/display/KAFKA/Time+Based+Release+Plan
> >
> > On Thu, Jun 13, 2024 at 1:17 PM Josep Prat 
> > wrote:
> >
> > > Hi Justine,
> > >
> > > I know we discarded parallel branching, but it was under the scope of
> > 3.8.0
> > > and with the KIPs no yet approved.
> > > We could also not do a parallel release, but rather "quick" 3.9 and then
> > > start with 4.0.
> > >
> > > Best
> > > -
> > > Josep Prat
> > > Open Source Engineering Director, Aiven
> > > josep.p...@aiven.io   |   +491715557497 | aiven.io
> > > Aiven Deutschland GmbH
> > > Alexanderufer 3-7, 10117 Berlin
> > > Geschäftsführer: Oskari Saarenmaa & Hannu Valtonen
> > > Amtsgericht Charlottenburg, HRB 209739 B
> > >
> > > On Thu, Jun 13, 2024, 22:08 Josep Prat  wrote:
> > >
> > > > Hi Sophie,
> > > >
> > > > I have a call tomorrow with José to clarify the estimates for KIP-853.
> > > > I also wouldn't like to delay the release for a month or more.
> > > >
> > > > Regarding your proposal, I find it would be a good way forward, +1 from
> > > my
> > > > side.
> > > >
> > > >
> > > > I also find this release and what should include is a hot topic.
> > > > What do others think?
> > > >
> > > > Best,
> > > >
> > > > 
> > > > Josep Prat
> > > > Open Source Engineering Director, Aiven josep.p...@aiven.io   |
> > > > +491715557497 | aiven.io
> > > > Aiven Deutschland GmbH
> > > > Alexanderufer 3-7, 10117 Berlin
> > > > Geschäftsführer: Oskari Saarenmaa & Hannu Valtonen
> > > > Amtsgericht Charlottenburg, HRB 209739 B
> > > >
> > > > On Thu, Jun 13, 2024, 21:23 Sophie Blee-Goldman  > >
> > > > wrote:
> > > >
> > > >> Hey all -- was just wondering where we currently stand Re: delaying 3.
> > > for
> > > >> the KRaft KIPs vs doing a 3.9 release
> > > >>
> > > >> I know we don't want to have to wait for a whole release cycle to ship
> > > >> these KRaft features, but delaying 3.8 up to month is also rather
> > > >> difficult
> > > >> to swallow. I just wanted to throw an unusual idea out there and see
> > if
> > > >> this might be a possible compromise, or is out of the question:
> > > >>
> > > >> What if we proceed with the 3.8 release as-is, without these KIPs, but
> > > >> rather than doing 3.9 in another 3 months we continue on with the plan
> > > to
> > > >> ship 4.0 in the fall and simply do a very small 3.9 release just for
> > the
> > > >> KRaft KIPs once they are finished?
> > > >>
> > > >> I know this breaks our usual release cycle and may be confusing to
> > some
> > > >> users, but many of us are waiting on things being shipped in 3.8 and
> > > >> delaying it by another month (perhaps more) feels unfair. At the same
> > > >> time,
> > > >> I understand the need to ship these KRaft KIPs before 4.0 and that
> > there

Re: [DISCUSS] Apache Kafka 3.8.0 release

[Christopher X Bogan]

is this where I ask
 to join?

On Thu, Jun 13, 2024 at 1:20 PM Greg Harris 
wrote:

> Hi Sophie and Justine,
>
> I share your concerns about delaying 3.8 in order to give the Kraft KIPs
> more time for implementation. I raised them in the discussion for KIP-1012
> [1]:
>
> > I think there is a
> > risk that features that are on-time and eligible for a 3.8 release
> > could be delayed by some KIPs which are given special treatment.
>
> This situation is exactly why Kafka has standardized on time based releases
> [2], and It is not exceptional for features to slip from releases in order
> to keep the releases on-time, it's a very intentional choice of priorities.
>
> I don't think the situation we're in warrants parallel development, and
> I'm uncomfortable with incurring the additional risk to users by doing a
> nonstandard release.
> For example, two risks are that 3.9 never happens, or happens much later
> than expected (after 4.1, 4.2, etc). There is a remote chance of these
> happening, but we should be prepared if these features get delayed further.
> Users could be left behind waiting for a 3.9 release without an upgrade
> path for new features or security updates. I found this to be the most
> compelling motivation for KIP-1012, and parallel development doesn't
> address it.
> If the 3.9 release comes out much later, users may be unsafe upgrading from
> 3.9 to some 4.x versions, and we would need special notices to explain this
> non-linearity in our versions.
>
> Thanks all,
> Greg
>
> [1] https://lists.apache.org/thread/kvdp2gmq5gd9txkvxh5vk3z2n55b04s5
> [2]
> https://cwiki.apache.org/confluence/display/KAFKA/Time+Based+Release+Plan
>
> On Thu, Jun 13, 2024 at 1:17 PM Josep Prat 
> wrote:
>
> > Hi Justine,
> >
> > I know we discarded parallel branching, but it was under the scope of
> 3.8.0
> > and with the KIPs no yet approved.
> > We could also not do a parallel release, but rather "quick" 3.9 and then
> > start with 4.0.
> >
> > Best
> > -
> > Josep Prat
> > Open Source Engineering Director, Aiven
> > josep.p...@aiven.io   |   +491715557497 | aiven.io
> > Aiven Deutschland GmbH
> > Alexanderufer 3-7, 10117 Berlin
> > Geschäftsführer: Oskari Saarenmaa & Hannu Valtonen
> > Amtsgericht Charlottenburg, HRB 209739 B
> >
> > On Thu, Jun 13, 2024, 22:08 Josep Prat  wrote:
> >
> > > Hi Sophie,
> > >
> > > I have a call tomorrow with José to clarify the estimates for KIP-853.
> > > I also wouldn't like to delay the release for a month or more.
> > >
> > > Regarding your proposal, I find it would be a good way forward, +1 from
> > my
> > > side.
> > >
> > >
> > > I also find this release and what should include is a hot topic.
> > > What do others think?
> > >
> > > Best,
> > >
> > > 
> > > Josep Prat
> > > Open Source Engineering Director, Aiven josep.p...@aiven.io   |
> > > +491715557497 | aiven.io
> > > Aiven Deutschland GmbH
> > > Alexanderufer 3-7, 10117 Berlin
> > > Geschäftsführer: Oskari Saarenmaa & Hannu Valtonen
> > > Amtsgericht Charlottenburg, HRB 209739 B
> > >
> > > On Thu, Jun 13, 2024, 21:23 Sophie Blee-Goldman  >
> > > wrote:
> > >
> > >> Hey all -- was just wondering where we currently stand Re: delaying 3.
> > for
> > >> the KRaft KIPs vs doing a 3.9 release
> > >>
> > >> I know we don't want to have to wait for a whole release cycle to ship
> > >> these KRaft features, but delaying 3.8 up to month is also rather
> > >> difficult
> > >> to swallow. I just wanted to throw an unusual idea out there and see
> if
> > >> this might be a possible compromise, or is out of the question:
> > >>
> > >> What if we proceed with the 3.8 release as-is, without these KIPs, but
> > >> rather than doing 3.9 in another 3 months we continue on with the plan
> > to
> > >> ship 4.0 in the fall and simply do a very small 3.9 release just for
> the
> > >> KRaft KIPs once they are finished?
> > >>
> > >> I know this breaks our usual release cycle and may be confusing to
> some
> > >> users, but many of us are waiting on things being shipped in 3.8 and
> > >> delaying it by another month (perhaps more) feels unfair. At the same
> > >> time,
> > >> I understand the need to ship these KRaft KIPs before 4.0 and that
> there
> > >> are others who would consider it unfair if the KRaft KIPs were delayed
> > >> until the next release cycle. So it seems like an easy win-win to make
> > >> everyone happy by shipping 3.8 now and shipping the KRaft KIPs
> whenever
> > >> they are ready. This also removes the pressure on these KIPs to rush
> > >> everything in or cut scope, and would give them some breathing room to
> > >> take
> > >> the time they need.
> > >>
> > >> Thoughts?
> > >>
> > >> On Wed, Jun 12, 2024 at 11:44 PM Josep Prat
>  > >
> > >> wrote:
> > >>
> > >> > Hi all,
> > >> >
> > >> > We are now past the code freeze for the 3.8.0 release. If you think
> a
> > >> > commit should be backported to the 3.8 branch, please ping me in the
> > PR
> > >> > (@jlprat).
> > >> >
> > >> > 

Re: [DISCUSS] Apache Kafka 3.8.0 release

[Greg Harris]

Hi Sophie and Justine,

I share your concerns about delaying 3.8 in order to give the Kraft KIPs
more time for implementation. I raised them in the discussion for KIP-1012
[1]:

> I think there is a
> risk that features that are on-time and eligible for a 3.8 release
> could be delayed by some KIPs which are given special treatment.

This situation is exactly why Kafka has standardized on time based releases
[2], and It is not exceptional for features to slip from releases in order
to keep the releases on-time, it's a very intentional choice of priorities.

I don't think the situation we're in warrants parallel development, and
I'm uncomfortable with incurring the additional risk to users by doing a
nonstandard release.
For example, two risks are that 3.9 never happens, or happens much later
than expected (after 4.1, 4.2, etc). There is a remote chance of these
happening, but we should be prepared if these features get delayed further.
Users could be left behind waiting for a 3.9 release without an upgrade
path for new features or security updates. I found this to be the most
compelling motivation for KIP-1012, and parallel development doesn't
address it.
If the 3.9 release comes out much later, users may be unsafe upgrading from
3.9 to some 4.x versions, and we would need special notices to explain this
non-linearity in our versions.

Thanks all,
Greg

[1] https://lists.apache.org/thread/kvdp2gmq5gd9txkvxh5vk3z2n55b04s5
[2]
https://cwiki.apache.org/confluence/display/KAFKA/Time+Based+Release+Plan

On Thu, Jun 13, 2024 at 1:17 PM Josep Prat 
wrote:

> Hi Justine,
>
> I know we discarded parallel branching, but it was under the scope of 3.8.0
> and with the KIPs no yet approved.
> We could also not do a parallel release, but rather "quick" 3.9 and then
> start with 4.0.
>
> Best
> -
> Josep Prat
> Open Source Engineering Director, Aiven
> josep.p...@aiven.io   |   +491715557497 | aiven.io
> Aiven Deutschland GmbH
> Alexanderufer 3-7, 10117 Berlin
> Geschäftsführer: Oskari Saarenmaa & Hannu Valtonen
> Amtsgericht Charlottenburg, HRB 209739 B
>
> On Thu, Jun 13, 2024, 22:08 Josep Prat  wrote:
>
> > Hi Sophie,
> >
> > I have a call tomorrow with José to clarify the estimates for KIP-853.
> > I also wouldn't like to delay the release for a month or more.
> >
> > Regarding your proposal, I find it would be a good way forward, +1 from
> my
> > side.
> >
> >
> > I also find this release and what should include is a hot topic.
> > What do others think?
> >
> > Best,
> >
> > 
> > Josep Prat
> > Open Source Engineering Director, Aiven josep.p...@aiven.io   |
> > +491715557497 | aiven.io
> > Aiven Deutschland GmbH
> > Alexanderufer 3-7, 10117 Berlin
> > Geschäftsführer: Oskari Saarenmaa & Hannu Valtonen
> > Amtsgericht Charlottenburg, HRB 209739 B
> >
> > On Thu, Jun 13, 2024, 21:23 Sophie Blee-Goldman 
> > wrote:
> >
> >> Hey all -- was just wondering where we currently stand Re: delaying 3.
> for
> >> the KRaft KIPs vs doing a 3.9 release
> >>
> >> I know we don't want to have to wait for a whole release cycle to ship
> >> these KRaft features, but delaying 3.8 up to month is also rather
> >> difficult
> >> to swallow. I just wanted to throw an unusual idea out there and see if
> >> this might be a possible compromise, or is out of the question:
> >>
> >> What if we proceed with the 3.8 release as-is, without these KIPs, but
> >> rather than doing 3.9 in another 3 months we continue on with the plan
> to
> >> ship 4.0 in the fall and simply do a very small 3.9 release just for the
> >> KRaft KIPs once they are finished?
> >>
> >> I know this breaks our usual release cycle and may be confusing to some
> >> users, but many of us are waiting on things being shipped in 3.8 and
> >> delaying it by another month (perhaps more) feels unfair. At the same
> >> time,
> >> I understand the need to ship these KRaft KIPs before 4.0 and that there
> >> are others who would consider it unfair if the KRaft KIPs were delayed
> >> until the next release cycle. So it seems like an easy win-win to make
> >> everyone happy by shipping 3.8 now and shipping the KRaft KIPs whenever
> >> they are ready. This also removes the pressure on these KIPs to rush
> >> everything in or cut scope, and would give them some breathing room to
> >> take
> >> the time they need.
> >>
> >> Thoughts?
> >>
> >> On Wed, Jun 12, 2024 at 11:44 PM Josep Prat  >
> >> wrote:
> >>
> >> > Hi all,
> >> >
> >> > We are now past the code freeze for the 3.8.0 release. If you think a
> >> > commit should be backported to the 3.8 branch, please ping me in the
> PR
> >> > (@jlprat).
> >> >
> >> > Thanks!
> >> >
> >> > On Wed, Jun 12, 2024 at 7:22 PM José Armando García Sancio
> >> >  wrote:
> >> >
> >> > > Hi Josep,
> >> > >
> >> > > See my comment below.
> >> > >
> >> > > On Wed, Jun 12, 2024 at 1:17 PM Josep Prat
> >> 
> >> > > wrote:
> >> > > > How long do you think it will take to bring KIP-853 to completion?
> >> > >
> >> > > We are 

Re: [DISCUSS] Apache Kafka 3.8.0 release

[Josep Prat]

Hi Justine,

I know we discarded parallel branching, but it was under the scope of 3.8.0
and with the KIPs no yet approved.
We could also not do a parallel release, but rather "quick" 3.9 and then
start with 4.0.

Best
-
Josep Prat
Open Source Engineering Director, Aiven
josep.p...@aiven.io   |   +491715557497 | aiven.io
Aiven Deutschland GmbH
Alexanderufer 3-7, 10117 Berlin
Geschäftsführer: Oskari Saarenmaa & Hannu Valtonen
Amtsgericht Charlottenburg, HRB 209739 B

On Thu, Jun 13, 2024, 22:08 Josep Prat  wrote:

> Hi Sophie,
>
> I have a call tomorrow with José to clarify the estimates for KIP-853.
> I also wouldn't like to delay the release for a month or more.
>
> Regarding your proposal, I find it would be a good way forward, +1 from my
> side.
>
>
> I also find this release and what should include is a hot topic.
> What do others think?
>
> Best,
>
> 
> Josep Prat
> Open Source Engineering Director, Aiven josep.p...@aiven.io   |
> +491715557497 | aiven.io
> Aiven Deutschland GmbH
> Alexanderufer 3-7, 10117 Berlin
> Geschäftsführer: Oskari Saarenmaa & Hannu Valtonen
> Amtsgericht Charlottenburg, HRB 209739 B
>
> On Thu, Jun 13, 2024, 21:23 Sophie Blee-Goldman 
> wrote:
>
>> Hey all -- was just wondering where we currently stand Re: delaying 3. for
>> the KRaft KIPs vs doing a 3.9 release
>>
>> I know we don't want to have to wait for a whole release cycle to ship
>> these KRaft features, but delaying 3.8 up to month is also rather
>> difficult
>> to swallow. I just wanted to throw an unusual idea out there and see if
>> this might be a possible compromise, or is out of the question:
>>
>> What if we proceed with the 3.8 release as-is, without these KIPs, but
>> rather than doing 3.9 in another 3 months we continue on with the plan to
>> ship 4.0 in the fall and simply do a very small 3.9 release just for the
>> KRaft KIPs once they are finished?
>>
>> I know this breaks our usual release cycle and may be confusing to some
>> users, but many of us are waiting on things being shipped in 3.8 and
>> delaying it by another month (perhaps more) feels unfair. At the same
>> time,
>> I understand the need to ship these KRaft KIPs before 4.0 and that there
>> are others who would consider it unfair if the KRaft KIPs were delayed
>> until the next release cycle. So it seems like an easy win-win to make
>> everyone happy by shipping 3.8 now and shipping the KRaft KIPs whenever
>> they are ready. This also removes the pressure on these KIPs to rush
>> everything in or cut scope, and would give them some breathing room to
>> take
>> the time they need.
>>
>> Thoughts?
>>
>> On Wed, Jun 12, 2024 at 11:44 PM Josep Prat 
>> wrote:
>>
>> > Hi all,
>> >
>> > We are now past the code freeze for the 3.8.0 release. If you think a
>> > commit should be backported to the 3.8 branch, please ping me in the PR
>> > (@jlprat).
>> >
>> > Thanks!
>> >
>> > On Wed, Jun 12, 2024 at 7:22 PM José Armando García Sancio
>> >  wrote:
>> >
>> > > Hi Josep,
>> > >
>> > > See my comment below.
>> > >
>> > > On Wed, Jun 12, 2024 at 1:17 PM Josep Prat
>> 
>> > > wrote:
>> > > > How long do you think it will take to bring KIP-853 to completion?
>> > >
>> > > We are still missing a few issues/jiras that need to get implemented
>> > > for the feature to be usable. I would say a few more weeks. May be
>> > > early July or mid July.
>> > >
>> > > Thanks,
>> > > --
>> > > -José
>> > >
>> >
>> >
>> > --
>> > [image: Aiven] 
>> >
>> > *Josep Prat*
>> > Open Source Engineering Director, *Aiven*
>> > josep.p...@aiven.io   |   +491715557497
>> > aiven.io    |   <
>> https://www.facebook.com/aivencloud
>> > >
>> >      <
>> > https://twitter.com/aiven_io>
>> > *Aiven Deutschland GmbH*
>> > Alexanderufer 3-7, 10117 Berlin
>> > Geschäftsführer: Oskari Saarenmaa & Hannu Valtonen
>> > Amtsgericht Charlottenburg, HRB 209739 B
>> >
>>
>

Re: [DISCUSS] Apache Kafka 3.8.0 release

[Josep Prat]

Hi Sophie,

I have a call tomorrow with José to clarify the estimates for KIP-853.
I also wouldn't like to delay the release for a month or more.

Regarding your proposal, I find it would be a good way forward, +1 from my
side.


I also find this release and what should include is a hot topic.
What do others think?

Best,


Josep Prat
Open Source Engineering Director, Aiven josep.p...@aiven.io   |
+491715557497 | aiven.io
Aiven Deutschland GmbH
Alexanderufer 3-7, 10117 Berlin
Geschäftsführer: Oskari Saarenmaa & Hannu Valtonen
Amtsgericht Charlottenburg, HRB 209739 B

On Thu, Jun 13, 2024, 21:23 Sophie Blee-Goldman 
wrote:

> Hey all -- was just wondering where we currently stand Re: delaying 3. for
> the KRaft KIPs vs doing a 3.9 release
>
> I know we don't want to have to wait for a whole release cycle to ship
> these KRaft features, but delaying 3.8 up to month is also rather difficult
> to swallow. I just wanted to throw an unusual idea out there and see if
> this might be a possible compromise, or is out of the question:
>
> What if we proceed with the 3.8 release as-is, without these KIPs, but
> rather than doing 3.9 in another 3 months we continue on with the plan to
> ship 4.0 in the fall and simply do a very small 3.9 release just for the
> KRaft KIPs once they are finished?
>
> I know this breaks our usual release cycle and may be confusing to some
> users, but many of us are waiting on things being shipped in 3.8 and
> delaying it by another month (perhaps more) feels unfair. At the same time,
> I understand the need to ship these KRaft KIPs before 4.0 and that there
> are others who would consider it unfair if the KRaft KIPs were delayed
> until the next release cycle. So it seems like an easy win-win to make
> everyone happy by shipping 3.8 now and shipping the KRaft KIPs whenever
> they are ready. This also removes the pressure on these KIPs to rush
> everything in or cut scope, and would give them some breathing room to take
> the time they need.
>
> Thoughts?
>
> On Wed, Jun 12, 2024 at 11:44 PM Josep Prat 
> wrote:
>
> > Hi all,
> >
> > We are now past the code freeze for the 3.8.0 release. If you think a
> > commit should be backported to the 3.8 branch, please ping me in the PR
> > (@jlprat).
> >
> > Thanks!
> >
> > On Wed, Jun 12, 2024 at 7:22 PM José Armando García Sancio
> >  wrote:
> >
> > > Hi Josep,
> > >
> > > See my comment below.
> > >
> > > On Wed, Jun 12, 2024 at 1:17 PM Josep Prat  >
> > > wrote:
> > > > How long do you think it will take to bring KIP-853 to completion?
> > >
> > > We are still missing a few issues/jiras that need to get implemented
> > > for the feature to be usable. I would say a few more weeks. May be
> > > early July or mid July.
> > >
> > > Thanks,
> > > --
> > > -José
> > >
> >
> >
> > --
> > [image: Aiven] 
> >
> > *Josep Prat*
> > Open Source Engineering Director, *Aiven*
> > josep.p...@aiven.io   |   +491715557497
> > aiven.io    |   <
> https://www.facebook.com/aivencloud
> > >
> >      <
> > https://twitter.com/aiven_io>
> > *Aiven Deutschland GmbH*
> > Alexanderufer 3-7, 10117 Berlin
> > Geschäftsführer: Oskari Saarenmaa & Hannu Valtonen
> > Amtsgericht Charlottenburg, HRB 209739 B
> >
>

Re: [DISCUSS] Apache Kafka 3.8.0 release

[Justine Olshan]

Hey Sophie,

Thanks for bringing this up, since I was also lacking clarity here.

One thing to note is that such a proposal (parallel development) was
discussed as part of KIP-1012 and it was rejected
https://cwiki.apache.org/confluence/display/KAFKA/KIP-1012%3A+The+need+for+a+Kafka+3.8.x+release

I do understand the concern of delaying the release though so it would be
good to hear from others as well.

Justine

On Thu, Jun 13, 2024 at 12:23 PM Sophie Blee-Goldman 
wrote:

> Hey all -- was just wondering where we currently stand Re: delaying 3. for
> the KRaft KIPs vs doing a 3.9 release
>
> I know we don't want to have to wait for a whole release cycle to ship
> these KRaft features, but delaying 3.8 up to month is also rather difficult
> to swallow. I just wanted to throw an unusual idea out there and see if
> this might be a possible compromise, or is out of the question:
>
> What if we proceed with the 3.8 release as-is, without these KIPs, but
> rather than doing 3.9 in another 3 months we continue on with the plan to
> ship 4.0 in the fall and simply do a very small 3.9 release just for the
> KRaft KIPs once they are finished?
>
> I know this breaks our usual release cycle and may be confusing to some
> users, but many of us are waiting on things being shipped in 3.8 and
> delaying it by another month (perhaps more) feels unfair. At the same time,
> I understand the need to ship these KRaft KIPs before 4.0 and that there
> are others who would consider it unfair if the KRaft KIPs were delayed
> until the next release cycle. So it seems like an easy win-win to make
> everyone happy by shipping 3.8 now and shipping the KRaft KIPs whenever
> they are ready. This also removes the pressure on these KIPs to rush
> everything in or cut scope, and would give them some breathing room to take
> the time they need.
>
> Thoughts?
>
> On Wed, Jun 12, 2024 at 11:44 PM Josep Prat 
> wrote:
>
> > Hi all,
> >
> > We are now past the code freeze for the 3.8.0 release. If you think a
> > commit should be backported to the 3.8 branch, please ping me in the PR
> > (@jlprat).
> >
> > Thanks!
> >
> > On Wed, Jun 12, 2024 at 7:22 PM José Armando García Sancio
> >  wrote:
> >
> > > Hi Josep,
> > >
> > > See my comment below.
> > >
> > > On Wed, Jun 12, 2024 at 1:17 PM Josep Prat  >
> > > wrote:
> > > > How long do you think it will take to bring KIP-853 to completion?
> > >
> > > We are still missing a few issues/jiras that need to get implemented
> > > for the feature to be usable. I would say a few more weeks. May be
> > > early July or mid July.
> > >
> > > Thanks,
> > > --
> > > -José
> > >
> >
> >
> > --
> > [image: Aiven] 
> >
> > *Josep Prat*
> > Open Source Engineering Director, *Aiven*
> > josep.p...@aiven.io   |   +491715557497
> > aiven.io    |   <
> https://www.facebook.com/aivencloud
> > >
> >      <
> > https://twitter.com/aiven_io>
> > *Aiven Deutschland GmbH*
> > Alexanderufer 3-7, 10117 Berlin
> > Geschäftsführer: Oskari Saarenmaa & Hannu Valtonen
> > Amtsgericht Charlottenburg, HRB 209739 B
> >
>

Re: [DISCUSS] Apache Kafka 3.8.0 release

[Sophie Blee-Goldman]

Hey all -- was just wondering where we currently stand Re: delaying 3. for
the KRaft KIPs vs doing a 3.9 release

I know we don't want to have to wait for a whole release cycle to ship
these KRaft features, but delaying 3.8 up to month is also rather difficult
to swallow. I just wanted to throw an unusual idea out there and see if
this might be a possible compromise, or is out of the question:

What if we proceed with the 3.8 release as-is, without these KIPs, but
rather than doing 3.9 in another 3 months we continue on with the plan to
ship 4.0 in the fall and simply do a very small 3.9 release just for the
KRaft KIPs once they are finished?

I know this breaks our usual release cycle and may be confusing to some
users, but many of us are waiting on things being shipped in 3.8 and
delaying it by another month (perhaps more) feels unfair. At the same time,
I understand the need to ship these KRaft KIPs before 4.0 and that there
are others who would consider it unfair if the KRaft KIPs were delayed
until the next release cycle. So it seems like an easy win-win to make
everyone happy by shipping 3.8 now and shipping the KRaft KIPs whenever
they are ready. This also removes the pressure on these KIPs to rush
everything in or cut scope, and would give them some breathing room to take
the time they need.

Thoughts?

On Wed, Jun 12, 2024 at 11:44 PM Josep Prat 
wrote:

> Hi all,
>
> We are now past the code freeze for the 3.8.0 release. If you think a
> commit should be backported to the 3.8 branch, please ping me in the PR
> (@jlprat).
>
> Thanks!
>
> On Wed, Jun 12, 2024 at 7:22 PM José Armando García Sancio
>  wrote:
>
> > Hi Josep,
> >
> > See my comment below.
> >
> > On Wed, Jun 12, 2024 at 1:17 PM Josep Prat 
> > wrote:
> > > How long do you think it will take to bring KIP-853 to completion?
> >
> > We are still missing a few issues/jiras that need to get implemented
> > for the feature to be usable. I would say a few more weeks. May be
> > early July or mid July.
> >
> > Thanks,
> > --
> > -José
> >
>
>
> --
> [image: Aiven] 
>
> *Josep Prat*
> Open Source Engineering Director, *Aiven*
> josep.p...@aiven.io   |   +491715557497
> aiven.io    |    >
>      <
> https://twitter.com/aiven_io>
> *Aiven Deutschland GmbH*
> Alexanderufer 3-7, 10117 Berlin
> Geschäftsführer: Oskari Saarenmaa & Hannu Valtonen
> Amtsgericht Charlottenburg, HRB 209739 B
>

Re: [DISCUSS] Apache Kafka 3.8.0 release

[Josep Prat]

Hi all,

We are now past the code freeze for the 3.8.0 release. If you think a
commit should be backported to the 3.8 branch, please ping me in the PR
(@jlprat).

Thanks!

On Wed, Jun 12, 2024 at 7:22 PM José Armando García Sancio
 wrote:

> Hi Josep,
>
> See my comment below.
>
> On Wed, Jun 12, 2024 at 1:17 PM Josep Prat 
> wrote:
> > How long do you think it will take to bring KIP-853 to completion?
>
> We are still missing a few issues/jiras that need to get implemented
> for the feature to be usable. I would say a few more weeks. May be
> early July or mid July.
>
> Thanks,
> --
> -José
>


-- 
[image: Aiven] 

*Josep Prat*
Open Source Engineering Director, *Aiven*
josep.p...@aiven.io   |   +491715557497
aiven.io    |   
     
*Aiven Deutschland GmbH*
Alexanderufer 3-7, 10117 Berlin
Geschäftsführer: Oskari Saarenmaa & Hannu Valtonen
Amtsgericht Charlottenburg, HRB 209739 B

Re: [DISCUSS] Apache Kafka 3.8.0 release

[José Armando García Sancio]

Hi Josep,

See my comment below.

On Wed, Jun 12, 2024 at 1:17 PM Josep Prat  wrote:
> How long do you think it will take to bring KIP-853 to completion?

We are still missing a few issues/jiras that need to get implemented
for the feature to be usable. I would say a few more weeks. May be
early July or mid July.

Thanks,
-- 
-José

Re: [DISCUSS] Apache Kafka 3.8.0 release

[Josep Prat]

Hi Colin,

How long do you think it will take to bring KIP-853 to completion?

Best,

On Wed, Jun 12, 2024 at 6:42 PM Colin McCabe  wrote:

> Hi Josep,
>
> KIP-966 is not needed for feature parity with ZK. Indeed, KIP-966 will not
> be implemented in ZK at all (and never was).
>
> There is a PR related to honoring dynamic configs for
> unclean.leader.election which we did agree to do for 3.8. It's under review
> and we hope to get it in soon.
>
> We still plan on having KIP-853 in 3.8. In fact, it will be the main
> feature of that release.
>
> best,
> Colin
>
> On Wed, Jun 12, 2024, at 01:50, Josep Prat wrote:
> > Hi all,
> >
> > We are now really close to the planned code freeze deadline (today EOD).
> > According to KIP-1012 [1] we agreed to stay in the 3.x branch until we
> > achieve feature parity regarding Zookeeper and KRaft. The two main KIPs
> > identified that would achieve this are: KIP-853 [2] and KIP-966 [3].
> > At the moment of writing this email both KIPs are not completed. My
> > question to the people driving both KIPs would be, how much more time do
> > you think it's needed to bring these KIPs to completion?
> >
> > - If the time needed would be short, we could still include these 2 KIPs
> in
> > the release.
> > - However, if the time needed would be on the scale of weeks, we should
> > continue with the release plan for 3.8 and after start working on the 3.9
> > release.
> >
> > What are your thoughts?
> >
> >
> > [1]:
> >
> https://cwiki.apache.org/confluence/display/KAFKA/KIP-1012%3A+The+need+for+a+Kafka+3.8.x+release
> > [2]:
> >
> https://cwiki.apache.org/confluence/display/KAFKA/KIP-853%3A+KRaft+Controller+Membership+Changes
> > [3]:
> >
> https://cwiki.apache.org/confluence/display/KAFKA/KIP-966%3A+Eligible+Leader+Replicas
> >
> > On Wed, Jun 12, 2024 at 10:40 AM Josep Prat  wrote:
> >
> >> Hi Rajini,
> >> Yes, we could backport this one to the 3.8 branch. Would you be able to
> do
> >> this once you merge this PR?
> >>
> >> Thanks
> >>
> >> On Tue, Jun 11, 2024 at 10:53 PM Rajini Sivaram <
> rajinisiva...@gmail.com>
> >> wrote:
> >>
> >>> Hi Josep,
> >>>
> >>> The PR https://github.com/apache/kafka/pull/13277 for KIP-899 looks
> ready
> >>> to be merged (waiting for the PR build).The PR changes several files,
> but
> >>> is relatively straightforward and not risky. Also the changes are
> under a
> >>> config that is not enabled by default. Since the KIP was approved
> before
> >>> KIP freeze, will it be ok to include in 3.8.0?
> >>>
> >>> Thank you,
> >>>
> >>> Rajini
> >>>
> >>>
> >>> On Tue, Jun 11, 2024 at 9:35 AM Josep Prat  >
> >>> wrote:
> >>>
> >>> > Hi all,
> >>> >
> >>> > I just want to remind everybody that the code freeze deadline is
> >>> > approaching. June 12th EOD is the deadline.
> >>> >
> >>> > Please do not automatically backport any commit to the 3.8 branch
> after
> >>> > June 12th EOD. Ping me if you think the commit should be backported
> >>> (fixes
> >>> > failures in the branch or critical bug fixes).
> >>> >
> >>> > Thanks all!
> >>> >
> >>> > On Sat, Jun 1, 2024 at 8:43 PM José Armando García Sancio
> >>> >  wrote:
> >>> >
> >>> > > Hi Josep,
> >>> > >
> >>> > > See my comments below.
> >>> > >
> >>> > > On Wed, May 29, 2024 at 10:52 AM Josep Prat
> >>>  >>> > >
> >>> > > wrote:
> >>> > > > So I would propose to leave the deadlines as they are and
> manually
> >>> > cherry
> >>> > > > pick the commits related to KIP-853 and KIP-966.
> >>> > >
> >>> > > Your proposal sounds good to me. I suspect that will be doing
> feature
> >>> > > development for KIP-853 past the feature freeze and code freeze
> date.
> >>> > > Maybe feature development will be finished around the end of June.
> >>> > >
> >>> > > I'll make sure to cherry pick commits for KIP-853 to the 3.8 branch
> >>> > > once we have one.
> >>> > >
> >>> > > Thanks,
> >>> > > --
> >>> > > -José
> >>> > >
> >>> >
> >>> >
> >>> > --
> >>> > [image: Aiven] 
> >>> >
> >>> > *Josep Prat*
> >>> > Open Source Engineering Director, *Aiven*
> >>> > josep.p...@aiven.io   |   +491715557497
> >>> > aiven.io    |   <
> >>> https://www.facebook.com/aivencloud
> >>> > >
> >>> >      <
> >>> > https://twitter.com/aiven_io>
> >>> > *Aiven Deutschland GmbH*
> >>> > Alexanderufer 3-7, 10117 Berlin
> >>> > Geschäftsführer: Oskari Saarenmaa & Hannu Valtonen
> >>> > Amtsgericht Charlottenburg, HRB 209739 B
> >>> >
> >>>
> >>
> >>
> >> --
> >> [image: Aiven] 
> >>
> >> *Josep Prat*
> >> Open Source Engineering Director, *Aiven*
> >> josep.p...@aiven.io   |   +491715557497
> >> aiven.io    |
> >> 
> >>    <
> https://twitter.com/aiven_io>
> >> *Aiven Deutschland GmbH*
> >> Alexanderufer 3-7, 10117 Berlin
> >> Geschäftsführer: Oskari Saarenmaa & Hannu Valtonen
> >> Amtsgericht Charlottenburg, HRB 209739 B
> >>
> >
> >

Re: [DISCUSS] Apache Kafka 3.8.0 release

[Colin McCabe]

Hi Josep,

KIP-966 is not needed for feature parity with ZK. Indeed, KIP-966 will not be 
implemented in ZK at all (and never was).

There is a PR related to honoring dynamic configs for unclean.leader.election 
which we did agree to do for 3.8. It's under review and we hope to get it in 
soon.

We still plan on having KIP-853 in 3.8. In fact, it will be the main feature of 
that release.

best,
Colin

On Wed, Jun 12, 2024, at 01:50, Josep Prat wrote:
> Hi all,
>
> We are now really close to the planned code freeze deadline (today EOD).
> According to KIP-1012 [1] we agreed to stay in the 3.x branch until we
> achieve feature parity regarding Zookeeper and KRaft. The two main KIPs
> identified that would achieve this are: KIP-853 [2] and KIP-966 [3].
> At the moment of writing this email both KIPs are not completed. My
> question to the people driving both KIPs would be, how much more time do
> you think it's needed to bring these KIPs to completion?
>
> - If the time needed would be short, we could still include these 2 KIPs in
> the release.
> - However, if the time needed would be on the scale of weeks, we should
> continue with the release plan for 3.8 and after start working on the 3.9
> release.
>
> What are your thoughts?
>
>
> [1]:
> https://cwiki.apache.org/confluence/display/KAFKA/KIP-1012%3A+The+need+for+a+Kafka+3.8.x+release
> [2]:
> https://cwiki.apache.org/confluence/display/KAFKA/KIP-853%3A+KRaft+Controller+Membership+Changes
> [3]:
> https://cwiki.apache.org/confluence/display/KAFKA/KIP-966%3A+Eligible+Leader+Replicas
>
> On Wed, Jun 12, 2024 at 10:40 AM Josep Prat  wrote:
>
>> Hi Rajini,
>> Yes, we could backport this one to the 3.8 branch. Would you be able to do
>> this once you merge this PR?
>>
>> Thanks
>>
>> On Tue, Jun 11, 2024 at 10:53 PM Rajini Sivaram 
>> wrote:
>>
>>> Hi Josep,
>>>
>>> The PR https://github.com/apache/kafka/pull/13277 for KIP-899 looks ready
>>> to be merged (waiting for the PR build).The PR changes several files, but
>>> is relatively straightforward and not risky. Also the changes are under a
>>> config that is not enabled by default. Since the KIP was approved before
>>> KIP freeze, will it be ok to include in 3.8.0?
>>>
>>> Thank you,
>>>
>>> Rajini
>>>
>>>
>>> On Tue, Jun 11, 2024 at 9:35 AM Josep Prat 
>>> wrote:
>>>
>>> > Hi all,
>>> >
>>> > I just want to remind everybody that the code freeze deadline is
>>> > approaching. June 12th EOD is the deadline.
>>> >
>>> > Please do not automatically backport any commit to the 3.8 branch after
>>> > June 12th EOD. Ping me if you think the commit should be backported
>>> (fixes
>>> > failures in the branch or critical bug fixes).
>>> >
>>> > Thanks all!
>>> >
>>> > On Sat, Jun 1, 2024 at 8:43 PM José Armando García Sancio
>>> >  wrote:
>>> >
>>> > > Hi Josep,
>>> > >
>>> > > See my comments below.
>>> > >
>>> > > On Wed, May 29, 2024 at 10:52 AM Josep Prat
>>> >> > >
>>> > > wrote:
>>> > > > So I would propose to leave the deadlines as they are and manually
>>> > cherry
>>> > > > pick the commits related to KIP-853 and KIP-966.
>>> > >
>>> > > Your proposal sounds good to me. I suspect that will be doing feature
>>> > > development for KIP-853 past the feature freeze and code freeze date.
>>> > > Maybe feature development will be finished around the end of June.
>>> > >
>>> > > I'll make sure to cherry pick commits for KIP-853 to the 3.8 branch
>>> > > once we have one.
>>> > >
>>> > > Thanks,
>>> > > --
>>> > > -José
>>> > >
>>> >
>>> >
>>> > --
>>> > [image: Aiven] 
>>> >
>>> > *Josep Prat*
>>> > Open Source Engineering Director, *Aiven*
>>> > josep.p...@aiven.io   |   +491715557497
>>> > aiven.io    |   <
>>> https://www.facebook.com/aivencloud
>>> > >
>>> >      <
>>> > https://twitter.com/aiven_io>
>>> > *Aiven Deutschland GmbH*
>>> > Alexanderufer 3-7, 10117 Berlin
>>> > Geschäftsführer: Oskari Saarenmaa & Hannu Valtonen
>>> > Amtsgericht Charlottenburg, HRB 209739 B
>>> >
>>>
>>
>>
>> --
>> [image: Aiven] 
>>
>> *Josep Prat*
>> Open Source Engineering Director, *Aiven*
>> josep.p...@aiven.io   |   +491715557497
>> aiven.io    |
>> 
>>    
>> *Aiven Deutschland GmbH*
>> Alexanderufer 3-7, 10117 Berlin
>> Geschäftsführer: Oskari Saarenmaa & Hannu Valtonen
>> Amtsgericht Charlottenburg, HRB 209739 B
>>
>
>
> -- 
> [image: Aiven] 
>
> *Josep Prat*
> Open Source Engineering Director, *Aiven*
> josep.p...@aiven.io   |   +491715557497
> aiven.io    |   
>      
> *Aiven Deutschland GmbH*
> Alexanderufer 3-7, 10117 Berlin
> Geschäftsführer: Oskari Saarenmaa & Hannu Valtonen
> Amtsgericht Charlottenburg, HRB 209739 B

Re: [DISCUSS] Apache Kafka 3.8.0 release

[Justine Olshan]

I'm just going to echo what Luke said.

KIP-966 is definitely delayed to the next release and we only need the
unclean leadership election PR he shared.

Thanks,
Justine

On Wed, Jun 12, 2024 at 9:33 AM Calvin Liu 
wrote:

> Hi Josep
> Due to the limit of the review resources, KIP-966 may have to be delayed to
> the next release.
> Thanks.
>
> On Wed, Jun 12, 2024 at 2:05 AM Rajini Sivaram 
> wrote:
>
> > >
> > > Yes, we could backport this one to the 3.8 branch. Would you be able to
> > do
> > > this once you merge this PR?
> >
> >
> > Thanks Josep! There were some unit test failures in last night's PR
> build,
> > so I have commented on the PR for Ivan to fix. If he fixes it today,
> then I
> > can merge to trunk and then cherry-pick to 3.8 today.
> >
> > Regards,
> >
> > Rajini
> >
> >
> > On Wed, Jun 12, 2024 at 9:51 AM Josep Prat 
> > wrote:
> >
> > > Hi all,
> > >
> > > We are now really close to the planned code freeze deadline (today
> EOD).
> > > According to KIP-1012 [1] we agreed to stay in the 3.x branch until we
> > > achieve feature parity regarding Zookeeper and KRaft. The two main KIPs
> > > identified that would achieve this are: KIP-853 [2] and KIP-966 [3].
> > > At the moment of writing this email both KIPs are not completed. My
> > > question to the people driving both KIPs would be, how much more time
> do
> > > you think it's needed to bring these KIPs to completion?
> > >
> > > - If the time needed would be short, we could still include these 2
> KIPs
> > in
> > > the release.
> > > - However, if the time needed would be on the scale of weeks, we should
> > > continue with the release plan for 3.8 and after start working on the
> 3.9
> > > release.
> > >
> > > What are your thoughts?
> > >
> > >
> > > [1]:
> > >
> > >
> >
> https://cwiki.apache.org/confluence/display/KAFKA/KIP-1012%3A+The+need+for+a+Kafka+3.8.x+release
> > > [2]:
> > >
> > >
> >
> https://cwiki.apache.org/confluence/display/KAFKA/KIP-853%3A+KRaft+Controller+Membership+Changes
> > > [3]:
> > >
> > >
> >
> https://cwiki.apache.org/confluence/display/KAFKA/KIP-966%3A+Eligible+Leader+Replicas
> > >
> > > On Wed, Jun 12, 2024 at 10:40 AM Josep Prat 
> wrote:
> > >
> > > > Hi Rajini,
> > > > Yes, we could backport this one to the 3.8 branch. Would you be able
> to
> > > do
> > > > this once you merge this PR?
> > > >
> > > > Thanks
> > > >
> > > > On Tue, Jun 11, 2024 at 10:53 PM Rajini Sivaram <
> > rajinisiva...@gmail.com
> > > >
> > > > wrote:
> > > >
> > > >> Hi Josep,
> > > >>
> > > >> The PR https://github.com/apache/kafka/pull/13277 for KIP-899 looks
> > > ready
> > > >> to be merged (waiting for the PR build).The PR changes several
> files,
> > > but
> > > >> is relatively straightforward and not risky. Also the changes are
> > under
> > > a
> > > >> config that is not enabled by default. Since the KIP was approved
> > before
> > > >> KIP freeze, will it be ok to include in 3.8.0?
> > > >>
> > > >> Thank you,
> > > >>
> > > >> Rajini
> > > >>
> > > >>
> > > >> On Tue, Jun 11, 2024 at 9:35 AM Josep Prat
> >  > > >
> > > >> wrote:
> > > >>
> > > >> > Hi all,
> > > >> >
> > > >> > I just want to remind everybody that the code freeze deadline is
> > > >> > approaching. June 12th EOD is the deadline.
> > > >> >
> > > >> > Please do not automatically backport any commit to the 3.8 branch
> > > after
> > > >> > June 12th EOD. Ping me if you think the commit should be
> backported
> > > >> (fixes
> > > >> > failures in the branch or critical bug fixes).
> > > >> >
> > > >> > Thanks all!
> > > >> >
> > > >> > On Sat, Jun 1, 2024 at 8:43 PM José Armando García Sancio
> > > >> >  wrote:
> > > >> >
> > > >> > > Hi Josep,
> > > >> > >
> > > >> > > See my comments below.
> > > >> > >
> > > >> > > On Wed, May 29, 2024 at 10:52 AM Josep Prat
> > > >>  > > >> > >
> > > >> > > wrote:
> > > >> > > > So I would propose to leave the deadlines as they are and
> > manually
> > > >> > cherry
> > > >> > > > pick the commits related to KIP-853 and KIP-966.
> > > >> > >
> > > >> > > Your proposal sounds good to me. I suspect that will be doing
> > > feature
> > > >> > > development for KIP-853 past the feature freeze and code freeze
> > > date.
> > > >> > > Maybe feature development will be finished around the end of
> June.
> > > >> > >
> > > >> > > I'll make sure to cherry pick commits for KIP-853 to the 3.8
> > branch
> > > >> > > once we have one.
> > > >> > >
> > > >> > > Thanks,
> > > >> > > --
> > > >> > > -José
> > > >> > >
> > > >> >
> > > >> >
> > > >> > --
> > > >> > [image: Aiven] 
> > > >> >
> > > >> > *Josep Prat*
> > > >> > Open Source Engineering Director, *Aiven*
> > > >> > josep.p...@aiven.io   |   +491715557497
> > > >> > aiven.io    |   <
> > > >> https://www.facebook.com/aivencloud
> > > >> > >
> > > >> >      <
> > > >> > https://twitter.com/aiven_io>
> > > >> > *Aiven Deutschland GmbH*
> > > >> > Alexanderufer 3-7, 10117 Berlin
> > > 

Re: [DISCUSS] Apache Kafka 3.8.0 release

[Calvin Liu]

Hi Josep
Due to the limit of the review resources, KIP-966 may have to be delayed to
the next release.
Thanks.

On Wed, Jun 12, 2024 at 2:05 AM Rajini Sivaram 
wrote:

> >
> > Yes, we could backport this one to the 3.8 branch. Would you be able to
> do
> > this once you merge this PR?
>
>
> Thanks Josep! There were some unit test failures in last night's PR build,
> so I have commented on the PR for Ivan to fix. If he fixes it today, then I
> can merge to trunk and then cherry-pick to 3.8 today.
>
> Regards,
>
> Rajini
>
>
> On Wed, Jun 12, 2024 at 9:51 AM Josep Prat 
> wrote:
>
> > Hi all,
> >
> > We are now really close to the planned code freeze deadline (today EOD).
> > According to KIP-1012 [1] we agreed to stay in the 3.x branch until we
> > achieve feature parity regarding Zookeeper and KRaft. The two main KIPs
> > identified that would achieve this are: KIP-853 [2] and KIP-966 [3].
> > At the moment of writing this email both KIPs are not completed. My
> > question to the people driving both KIPs would be, how much more time do
> > you think it's needed to bring these KIPs to completion?
> >
> > - If the time needed would be short, we could still include these 2 KIPs
> in
> > the release.
> > - However, if the time needed would be on the scale of weeks, we should
> > continue with the release plan for 3.8 and after start working on the 3.9
> > release.
> >
> > What are your thoughts?
> >
> >
> > [1]:
> >
> >
> https://cwiki.apache.org/confluence/display/KAFKA/KIP-1012%3A+The+need+for+a+Kafka+3.8.x+release
> > [2]:
> >
> >
> https://cwiki.apache.org/confluence/display/KAFKA/KIP-853%3A+KRaft+Controller+Membership+Changes
> > [3]:
> >
> >
> https://cwiki.apache.org/confluence/display/KAFKA/KIP-966%3A+Eligible+Leader+Replicas
> >
> > On Wed, Jun 12, 2024 at 10:40 AM Josep Prat  wrote:
> >
> > > Hi Rajini,
> > > Yes, we could backport this one to the 3.8 branch. Would you be able to
> > do
> > > this once you merge this PR?
> > >
> > > Thanks
> > >
> > > On Tue, Jun 11, 2024 at 10:53 PM Rajini Sivaram <
> rajinisiva...@gmail.com
> > >
> > > wrote:
> > >
> > >> Hi Josep,
> > >>
> > >> The PR https://github.com/apache/kafka/pull/13277 for KIP-899 looks
> > ready
> > >> to be merged (waiting for the PR build).The PR changes several files,
> > but
> > >> is relatively straightforward and not risky. Also the changes are
> under
> > a
> > >> config that is not enabled by default. Since the KIP was approved
> before
> > >> KIP freeze, will it be ok to include in 3.8.0?
> > >>
> > >> Thank you,
> > >>
> > >> Rajini
> > >>
> > >>
> > >> On Tue, Jun 11, 2024 at 9:35 AM Josep Prat
>  > >
> > >> wrote:
> > >>
> > >> > Hi all,
> > >> >
> > >> > I just want to remind everybody that the code freeze deadline is
> > >> > approaching. June 12th EOD is the deadline.
> > >> >
> > >> > Please do not automatically backport any commit to the 3.8 branch
> > after
> > >> > June 12th EOD. Ping me if you think the commit should be backported
> > >> (fixes
> > >> > failures in the branch or critical bug fixes).
> > >> >
> > >> > Thanks all!
> > >> >
> > >> > On Sat, Jun 1, 2024 at 8:43 PM José Armando García Sancio
> > >> >  wrote:
> > >> >
> > >> > > Hi Josep,
> > >> > >
> > >> > > See my comments below.
> > >> > >
> > >> > > On Wed, May 29, 2024 at 10:52 AM Josep Prat
> > >>  > >> > >
> > >> > > wrote:
> > >> > > > So I would propose to leave the deadlines as they are and
> manually
> > >> > cherry
> > >> > > > pick the commits related to KIP-853 and KIP-966.
> > >> > >
> > >> > > Your proposal sounds good to me. I suspect that will be doing
> > feature
> > >> > > development for KIP-853 past the feature freeze and code freeze
> > date.
> > >> > > Maybe feature development will be finished around the end of June.
> > >> > >
> > >> > > I'll make sure to cherry pick commits for KIP-853 to the 3.8
> branch
> > >> > > once we have one.
> > >> > >
> > >> > > Thanks,
> > >> > > --
> > >> > > -José
> > >> > >
> > >> >
> > >> >
> > >> > --
> > >> > [image: Aiven] 
> > >> >
> > >> > *Josep Prat*
> > >> > Open Source Engineering Director, *Aiven*
> > >> > josep.p...@aiven.io   |   +491715557497
> > >> > aiven.io    |   <
> > >> https://www.facebook.com/aivencloud
> > >> > >
> > >> >      <
> > >> > https://twitter.com/aiven_io>
> > >> > *Aiven Deutschland GmbH*
> > >> > Alexanderufer 3-7, 10117 Berlin
> > >> > Geschäftsführer: Oskari Saarenmaa & Hannu Valtonen
> > >> > Amtsgericht Charlottenburg, HRB 209739 B
> > >> >
> > >>
> > >
> > >
> > > --
> > > [image: Aiven] 
> > >
> > > *Josep Prat*
> > > Open Source Engineering Director, *Aiven*
> > > josep.p...@aiven.io   |   +491715557497
> > > aiven.io    |
> > > 
> > >    <
> > https://twitter.com/aiven_io>
> > > *Aiven Deutschland GmbH*
> > > Alexanderufer 3-7, 10117 Berlin
> > > 

Re: [DISCUSS] Apache Kafka 3.8.0 release

[Josep Prat]

Hi Edoardo,

Correct, you can still cherry-pick this one.

I'll send an email tomorrow morning (CEST) asking maintainers to stop
cherry picking commits unless we discuss it beforehand.

Best,

On Wed, Jun 12, 2024 at 6:09 PM Edoardo Comar  wrote:

> Hi Josep, I understand I am still in time to cherry-pick on 3.8.0
> https://github.com/apache/kafka/pull/16229
>
> right?
> thanks
>
> On Wed, 12 Jun 2024 at 11:34, Ivan Yurchenko  wrote:
> >
> > Hi,
> >
> > I'll try to do all the fixes and changes for KIP-899 [1] sooner today,
> but please proceed with the release if I don't manage.
> >
> > Ivan
> >
> > [1] https://github.com/apache/kafka/pull/13277
> >
> > On Wed, Jun 12, 2024, at 12:54, Josep Prat wrote:
> > > Hi Luke,
> > > I think Jose, also mentioned that it won't be ready for v3.8.0 (but he
> can
> > > confirm this). My question now would be, given that it seems we would
> need
> > > a v3.9.0, do you think it's important to include
> > > https://github.com/apache/kafka/pull/16284 in v3.8.0?
> > >
> > > Best,
> > >
> > > On Wed, Jun 12, 2024 at 11:40 AM Luke Chen  wrote:
> > >
> > > > Hi Josep
> > > >
> > > > For KIP-966, I think Calvin had mentioned he won't complete in
> v3.8.0.
> > > > https://lists.apache.org/thread/fsnr8wy5fznzfso7jgk90skgyo277fmw
> > > >
> > > > For unclean leader election, all we need is this PR:
> > > > https://github.com/apache/kafka/pull/16284
> > > > For this PR, I think it needs one more week to be completed.
> > > >
> > > > Thanks.
> > > > Luke
> > > >
> > > > On Wed, Jun 12, 2024 at 4:51 PM Josep Prat
> 
> > > > wrote:
> > > >
> > > > > Hi all,
> > > > >
> > > > > We are now really close to the planned code freeze deadline (today
> EOD).
> > > > > According to KIP-1012 [1] we agreed to stay in the 3.x branch
> until we
> > > > > achieve feature parity regarding Zookeeper and KRaft. The two main
> KIPs
> > > > > identified that would achieve this are: KIP-853 [2] and KIP-966
> [3].
> > > > > At the moment of writing this email both KIPs are not completed. My
> > > > > question to the people driving both KIPs would be, how much more
> time do
> > > > > you think it's needed to bring these KIPs to completion?
> > > > >
> > > > > - If the time needed would be short, we could still include these
> 2 KIPs
> > > > in
> > > > > the release.
> > > > > - However, if the time needed would be on the scale of weeks, we
> should
> > > > > continue with the release plan for 3.8 and after start working on
> the 3.9
> > > > > release.
> > > > >
> > > > > What are your thoughts?
> > > > >
> > > > >
> > > > > [1]:
> > > > >
> > > > >
> > > >
> https://cwiki.apache.org/confluence/display/KAFKA/KIP-1012%3A+The+need+for+a+Kafka+3.8.x+release
> > > > > [2]:
> > > > >
> > > > >
> > > >
> https://cwiki.apache.org/confluence/display/KAFKA/KIP-853%3A+KRaft+Controller+Membership+Changes
> > > > > [3]:
> > > > >
> > > > >
> > > >
> https://cwiki.apache.org/confluence/display/KAFKA/KIP-966%3A+Eligible+Leader+Replicas
> > > > >
> > > > > On Wed, Jun 12, 2024 at 10:40 AM Josep Prat 
> wrote:
> > > > >
> > > > > > Hi Rajini,
> > > > > > Yes, we could backport this one to the 3.8 branch. Would you be
> able to
> > > > > do
> > > > > > this once you merge this PR?
> > > > > >
> > > > > > Thanks
> > > > > >
> > > > > > On Tue, Jun 11, 2024 at 10:53 PM Rajini Sivaram <
> > > > rajinisiva...@gmail.com
> > > > > >
> > > > > > wrote:
> > > > > >
> > > > > >> Hi Josep,
> > > > > >>
> > > > > >> The PR https://github.com/apache/kafka/pull/13277 for KIP-899
> looks
> > > > > ready
> > > > > >> to be merged (waiting for the PR build).The PR changes several
> files,
> > > > > but
> > > > > >> is relatively straightforward and not risky. Also the changes
> are
> > > > under
> > > > > a
> > > > > >> config that is not enabled by default. Since the KIP was
> approved
> > > > before
> > > > > >> KIP freeze, will it be ok to include in 3.8.0?
> > > > > >>
> > > > > >> Thank you,
> > > > > >>
> > > > > >> Rajini
> > > > > >>
> > > > > >>
> > > > > >> On Tue, Jun 11, 2024 at 9:35 AM Josep Prat
> > > >  > > > > >
> > > > > >> wrote:
> > > > > >>
> > > > > >> > Hi all,
> > > > > >> >
> > > > > >> > I just want to remind everybody that the code freeze deadline
> is
> > > > > >> > approaching. June 12th EOD is the deadline.
> > > > > >> >
> > > > > >> > Please do not automatically backport any commit to the 3.8
> branch
> > > > > after
> > > > > >> > June 12th EOD. Ping me if you think the commit should be
> backported
> > > > > >> (fixes
> > > > > >> > failures in the branch or critical bug fixes).
> > > > > >> >
> > > > > >> > Thanks all!
> > > > > >> >
> > > > > >> > On Sat, Jun 1, 2024 at 8:43 PM José Armando García Sancio
> > > > > >> >  wrote:
> > > > > >> >
> > > > > >> > > Hi Josep,
> > > > > >> > >
> > > > > >> > > See my comments below.
> > > > > >> > >
> > > > > >> > > On Wed, May 29, 2024 at 10:52 AM Josep Prat
> > > > > >>  > > > > >> > >
> > > > > >> > > wrote:
> > > > > >> > > > So I would propose to leave the 

Re: [DISCUSS] Apache Kafka 3.8.0 release

[Edoardo Comar]

Hi Josep, I understand I am still in time to cherry-pick on 3.8.0
https://github.com/apache/kafka/pull/16229

right?
thanks

On Wed, 12 Jun 2024 at 11:34, Ivan Yurchenko  wrote:
>
> Hi,
>
> I'll try to do all the fixes and changes for KIP-899 [1] sooner today, but 
> please proceed with the release if I don't manage.
>
> Ivan
>
> [1] https://github.com/apache/kafka/pull/13277
>
> On Wed, Jun 12, 2024, at 12:54, Josep Prat wrote:
> > Hi Luke,
> > I think Jose, also mentioned that it won't be ready for v3.8.0 (but he can
> > confirm this). My question now would be, given that it seems we would need
> > a v3.9.0, do you think it's important to include
> > https://github.com/apache/kafka/pull/16284 in v3.8.0?
> >
> > Best,
> >
> > On Wed, Jun 12, 2024 at 11:40 AM Luke Chen  wrote:
> >
> > > Hi Josep
> > >
> > > For KIP-966, I think Calvin had mentioned he won't complete in v3.8.0.
> > > https://lists.apache.org/thread/fsnr8wy5fznzfso7jgk90skgyo277fmw
> > >
> > > For unclean leader election, all we need is this PR:
> > > https://github.com/apache/kafka/pull/16284
> > > For this PR, I think it needs one more week to be completed.
> > >
> > > Thanks.
> > > Luke
> > >
> > > On Wed, Jun 12, 2024 at 4:51 PM Josep Prat 
> > > wrote:
> > >
> > > > Hi all,
> > > >
> > > > We are now really close to the planned code freeze deadline (today EOD).
> > > > According to KIP-1012 [1] we agreed to stay in the 3.x branch until we
> > > > achieve feature parity regarding Zookeeper and KRaft. The two main KIPs
> > > > identified that would achieve this are: KIP-853 [2] and KIP-966 [3].
> > > > At the moment of writing this email both KIPs are not completed. My
> > > > question to the people driving both KIPs would be, how much more time do
> > > > you think it's needed to bring these KIPs to completion?
> > > >
> > > > - If the time needed would be short, we could still include these 2 KIPs
> > > in
> > > > the release.
> > > > - However, if the time needed would be on the scale of weeks, we should
> > > > continue with the release plan for 3.8 and after start working on the 
> > > > 3.9
> > > > release.
> > > >
> > > > What are your thoughts?
> > > >
> > > >
> > > > [1]:
> > > >
> > > >
> > > https://cwiki.apache.org/confluence/display/KAFKA/KIP-1012%3A+The+need+for+a+Kafka+3.8.x+release
> > > > [2]:
> > > >
> > > >
> > > https://cwiki.apache.org/confluence/display/KAFKA/KIP-853%3A+KRaft+Controller+Membership+Changes
> > > > [3]:
> > > >
> > > >
> > > https://cwiki.apache.org/confluence/display/KAFKA/KIP-966%3A+Eligible+Leader+Replicas
> > > >
> > > > On Wed, Jun 12, 2024 at 10:40 AM Josep Prat  wrote:
> > > >
> > > > > Hi Rajini,
> > > > > Yes, we could backport this one to the 3.8 branch. Would you be able 
> > > > > to
> > > > do
> > > > > this once you merge this PR?
> > > > >
> > > > > Thanks
> > > > >
> > > > > On Tue, Jun 11, 2024 at 10:53 PM Rajini Sivaram <
> > > rajinisiva...@gmail.com
> > > > >
> > > > > wrote:
> > > > >
> > > > >> Hi Josep,
> > > > >>
> > > > >> The PR https://github.com/apache/kafka/pull/13277 for KIP-899 looks
> > > > ready
> > > > >> to be merged (waiting for the PR build).The PR changes several files,
> > > > but
> > > > >> is relatively straightforward and not risky. Also the changes are
> > > under
> > > > a
> > > > >> config that is not enabled by default. Since the KIP was approved
> > > before
> > > > >> KIP freeze, will it be ok to include in 3.8.0?
> > > > >>
> > > > >> Thank you,
> > > > >>
> > > > >> Rajini
> > > > >>
> > > > >>
> > > > >> On Tue, Jun 11, 2024 at 9:35 AM Josep Prat
> > >  > > > >
> > > > >> wrote:
> > > > >>
> > > > >> > Hi all,
> > > > >> >
> > > > >> > I just want to remind everybody that the code freeze deadline is
> > > > >> > approaching. June 12th EOD is the deadline.
> > > > >> >
> > > > >> > Please do not automatically backport any commit to the 3.8 branch
> > > > after
> > > > >> > June 12th EOD. Ping me if you think the commit should be backported
> > > > >> (fixes
> > > > >> > failures in the branch or critical bug fixes).
> > > > >> >
> > > > >> > Thanks all!
> > > > >> >
> > > > >> > On Sat, Jun 1, 2024 at 8:43 PM José Armando García Sancio
> > > > >> >  wrote:
> > > > >> >
> > > > >> > > Hi Josep,
> > > > >> > >
> > > > >> > > See my comments below.
> > > > >> > >
> > > > >> > > On Wed, May 29, 2024 at 10:52 AM Josep Prat
> > > > >>  > > > >> > >
> > > > >> > > wrote:
> > > > >> > > > So I would propose to leave the deadlines as they are and
> > > manually
> > > > >> > cherry
> > > > >> > > > pick the commits related to KIP-853 and KIP-966.
> > > > >> > >
> > > > >> > > Your proposal sounds good to me. I suspect that will be doing
> > > > feature
> > > > >> > > development for KIP-853 past the feature freeze and code freeze
> > > > date.
> > > > >> > > Maybe feature development will be finished around the end of 
> > > > >> > > June.
> > > > >> > >
> > > > >> > > I'll make sure to cherry pick commits for KIP-853 to the 3.8
> > > branch
> > > > >> > > once 

Re: [DISCUSS] Apache Kafka 3.8.0 release

[Ivan Yurchenko]

Hi,

I'll try to do all the fixes and changes for KIP-899 [1] sooner today, but 
please proceed with the release if I don't manage.

Ivan

[1] https://github.com/apache/kafka/pull/13277

On Wed, Jun 12, 2024, at 12:54, Josep Prat wrote:
> Hi Luke,
> I think Jose, also mentioned that it won't be ready for v3.8.0 (but he can
> confirm this). My question now would be, given that it seems we would need
> a v3.9.0, do you think it's important to include
> https://github.com/apache/kafka/pull/16284 in v3.8.0?
> 
> Best,
> 
> On Wed, Jun 12, 2024 at 11:40 AM Luke Chen  wrote:
> 
> > Hi Josep
> >
> > For KIP-966, I think Calvin had mentioned he won't complete in v3.8.0.
> > https://lists.apache.org/thread/fsnr8wy5fznzfso7jgk90skgyo277fmw
> >
> > For unclean leader election, all we need is this PR:
> > https://github.com/apache/kafka/pull/16284
> > For this PR, I think it needs one more week to be completed.
> >
> > Thanks.
> > Luke
> >
> > On Wed, Jun 12, 2024 at 4:51 PM Josep Prat 
> > wrote:
> >
> > > Hi all,
> > >
> > > We are now really close to the planned code freeze deadline (today EOD).
> > > According to KIP-1012 [1] we agreed to stay in the 3.x branch until we
> > > achieve feature parity regarding Zookeeper and KRaft. The two main KIPs
> > > identified that would achieve this are: KIP-853 [2] and KIP-966 [3].
> > > At the moment of writing this email both KIPs are not completed. My
> > > question to the people driving both KIPs would be, how much more time do
> > > you think it's needed to bring these KIPs to completion?
> > >
> > > - If the time needed would be short, we could still include these 2 KIPs
> > in
> > > the release.
> > > - However, if the time needed would be on the scale of weeks, we should
> > > continue with the release plan for 3.8 and after start working on the 3.9
> > > release.
> > >
> > > What are your thoughts?
> > >
> > >
> > > [1]:
> > >
> > >
> > https://cwiki.apache.org/confluence/display/KAFKA/KIP-1012%3A+The+need+for+a+Kafka+3.8.x+release
> > > [2]:
> > >
> > >
> > https://cwiki.apache.org/confluence/display/KAFKA/KIP-853%3A+KRaft+Controller+Membership+Changes
> > > [3]:
> > >
> > >
> > https://cwiki.apache.org/confluence/display/KAFKA/KIP-966%3A+Eligible+Leader+Replicas
> > >
> > > On Wed, Jun 12, 2024 at 10:40 AM Josep Prat  wrote:
> > >
> > > > Hi Rajini,
> > > > Yes, we could backport this one to the 3.8 branch. Would you be able to
> > > do
> > > > this once you merge this PR?
> > > >
> > > > Thanks
> > > >
> > > > On Tue, Jun 11, 2024 at 10:53 PM Rajini Sivaram <
> > rajinisiva...@gmail.com
> > > >
> > > > wrote:
> > > >
> > > >> Hi Josep,
> > > >>
> > > >> The PR https://github.com/apache/kafka/pull/13277 for KIP-899 looks
> > > ready
> > > >> to be merged (waiting for the PR build).The PR changes several files,
> > > but
> > > >> is relatively straightforward and not risky. Also the changes are
> > under
> > > a
> > > >> config that is not enabled by default. Since the KIP was approved
> > before
> > > >> KIP freeze, will it be ok to include in 3.8.0?
> > > >>
> > > >> Thank you,
> > > >>
> > > >> Rajini
> > > >>
> > > >>
> > > >> On Tue, Jun 11, 2024 at 9:35 AM Josep Prat
> >  > > >
> > > >> wrote:
> > > >>
> > > >> > Hi all,
> > > >> >
> > > >> > I just want to remind everybody that the code freeze deadline is
> > > >> > approaching. June 12th EOD is the deadline.
> > > >> >
> > > >> > Please do not automatically backport any commit to the 3.8 branch
> > > after
> > > >> > June 12th EOD. Ping me if you think the commit should be backported
> > > >> (fixes
> > > >> > failures in the branch or critical bug fixes).
> > > >> >
> > > >> > Thanks all!
> > > >> >
> > > >> > On Sat, Jun 1, 2024 at 8:43 PM José Armando García Sancio
> > > >> >  wrote:
> > > >> >
> > > >> > > Hi Josep,
> > > >> > >
> > > >> > > See my comments below.
> > > >> > >
> > > >> > > On Wed, May 29, 2024 at 10:52 AM Josep Prat
> > > >>  > > >> > >
> > > >> > > wrote:
> > > >> > > > So I would propose to leave the deadlines as they are and
> > manually
> > > >> > cherry
> > > >> > > > pick the commits related to KIP-853 and KIP-966.
> > > >> > >
> > > >> > > Your proposal sounds good to me. I suspect that will be doing
> > > feature
> > > >> > > development for KIP-853 past the feature freeze and code freeze
> > > date.
> > > >> > > Maybe feature development will be finished around the end of June.
> > > >> > >
> > > >> > > I'll make sure to cherry pick commits for KIP-853 to the 3.8
> > branch
> > > >> > > once we have one.
> > > >> > >
> > > >> > > Thanks,
> > > >> > > --
> > > >> > > -José
> > > >> > >
> > > >> >
> > > >> >
> > > >> > --
> > > >> > [image: Aiven] 
> > > >> >
> > > >> > *Josep Prat*
> > > >> > Open Source Engineering Director, *Aiven*
> > > >> > josep.p...@aiven.io   |   +491715557497
> > > >> > aiven.io    |   <
> > > >> https://www.facebook.com/aivencloud
> > > >> > >
> > > >> >      <
> > > >> 

Re: [DISCUSS] Apache Kafka 3.8.0 release

[Josep Prat]

Hi Luke,
I think Jose, also mentioned that it won't be ready for v3.8.0 (but he can
confirm this). My question now would be, given that it seems we would need
a v3.9.0, do you think it's important to include
https://github.com/apache/kafka/pull/16284 in v3.8.0?

Best,

On Wed, Jun 12, 2024 at 11:40 AM Luke Chen  wrote:

> Hi Josep
>
> For KIP-966, I think Calvin had mentioned he won't complete in v3.8.0.
> https://lists.apache.org/thread/fsnr8wy5fznzfso7jgk90skgyo277fmw
>
> For unclean leader election, all we need is this PR:
> https://github.com/apache/kafka/pull/16284
> For this PR, I think it needs one more week to be completed.
>
> Thanks.
> Luke
>
> On Wed, Jun 12, 2024 at 4:51 PM Josep Prat 
> wrote:
>
> > Hi all,
> >
> > We are now really close to the planned code freeze deadline (today EOD).
> > According to KIP-1012 [1] we agreed to stay in the 3.x branch until we
> > achieve feature parity regarding Zookeeper and KRaft. The two main KIPs
> > identified that would achieve this are: KIP-853 [2] and KIP-966 [3].
> > At the moment of writing this email both KIPs are not completed. My
> > question to the people driving both KIPs would be, how much more time do
> > you think it's needed to bring these KIPs to completion?
> >
> > - If the time needed would be short, we could still include these 2 KIPs
> in
> > the release.
> > - However, if the time needed would be on the scale of weeks, we should
> > continue with the release plan for 3.8 and after start working on the 3.9
> > release.
> >
> > What are your thoughts?
> >
> >
> > [1]:
> >
> >
> https://cwiki.apache.org/confluence/display/KAFKA/KIP-1012%3A+The+need+for+a+Kafka+3.8.x+release
> > [2]:
> >
> >
> https://cwiki.apache.org/confluence/display/KAFKA/KIP-853%3A+KRaft+Controller+Membership+Changes
> > [3]:
> >
> >
> https://cwiki.apache.org/confluence/display/KAFKA/KIP-966%3A+Eligible+Leader+Replicas
> >
> > On Wed, Jun 12, 2024 at 10:40 AM Josep Prat  wrote:
> >
> > > Hi Rajini,
> > > Yes, we could backport this one to the 3.8 branch. Would you be able to
> > do
> > > this once you merge this PR?
> > >
> > > Thanks
> > >
> > > On Tue, Jun 11, 2024 at 10:53 PM Rajini Sivaram <
> rajinisiva...@gmail.com
> > >
> > > wrote:
> > >
> > >> Hi Josep,
> > >>
> > >> The PR https://github.com/apache/kafka/pull/13277 for KIP-899 looks
> > ready
> > >> to be merged (waiting for the PR build).The PR changes several files,
> > but
> > >> is relatively straightforward and not risky. Also the changes are
> under
> > a
> > >> config that is not enabled by default. Since the KIP was approved
> before
> > >> KIP freeze, will it be ok to include in 3.8.0?
> > >>
> > >> Thank you,
> > >>
> > >> Rajini
> > >>
> > >>
> > >> On Tue, Jun 11, 2024 at 9:35 AM Josep Prat
>  > >
> > >> wrote:
> > >>
> > >> > Hi all,
> > >> >
> > >> > I just want to remind everybody that the code freeze deadline is
> > >> > approaching. June 12th EOD is the deadline.
> > >> >
> > >> > Please do not automatically backport any commit to the 3.8 branch
> > after
> > >> > June 12th EOD. Ping me if you think the commit should be backported
> > >> (fixes
> > >> > failures in the branch or critical bug fixes).
> > >> >
> > >> > Thanks all!
> > >> >
> > >> > On Sat, Jun 1, 2024 at 8:43 PM José Armando García Sancio
> > >> >  wrote:
> > >> >
> > >> > > Hi Josep,
> > >> > >
> > >> > > See my comments below.
> > >> > >
> > >> > > On Wed, May 29, 2024 at 10:52 AM Josep Prat
> > >>  > >> > >
> > >> > > wrote:
> > >> > > > So I would propose to leave the deadlines as they are and
> manually
> > >> > cherry
> > >> > > > pick the commits related to KIP-853 and KIP-966.
> > >> > >
> > >> > > Your proposal sounds good to me. I suspect that will be doing
> > feature
> > >> > > development for KIP-853 past the feature freeze and code freeze
> > date.
> > >> > > Maybe feature development will be finished around the end of June.
> > >> > >
> > >> > > I'll make sure to cherry pick commits for KIP-853 to the 3.8
> branch
> > >> > > once we have one.
> > >> > >
> > >> > > Thanks,
> > >> > > --
> > >> > > -José
> > >> > >
> > >> >
> > >> >
> > >> > --
> > >> > [image: Aiven] 
> > >> >
> > >> > *Josep Prat*
> > >> > Open Source Engineering Director, *Aiven*
> > >> > josep.p...@aiven.io   |   +491715557497
> > >> > aiven.io    |   <
> > >> https://www.facebook.com/aivencloud
> > >> > >
> > >> >      <
> > >> > https://twitter.com/aiven_io>
> > >> > *Aiven Deutschland GmbH*
> > >> > Alexanderufer 3-7, 10117 Berlin
> > >> > Geschäftsführer: Oskari Saarenmaa & Hannu Valtonen
> > >> > Amtsgericht Charlottenburg, HRB 209739 B
> > >> >
> > >>
> > >
> > >
> > > --
> > > [image: Aiven] 
> > >
> > > *Josep Prat*
> > > Open Source Engineering Director, *Aiven*
> > > josep.p...@aiven.io   |   +491715557497
> > > aiven.io    |
> > > 
> > > 

Re: [DISCUSS] Apache Kafka 3.8.0 release

[Luke Chen]

Hi Josep

For KIP-966, I think Calvin had mentioned he won't complete in v3.8.0.
https://lists.apache.org/thread/fsnr8wy5fznzfso7jgk90skgyo277fmw

For unclean leader election, all we need is this PR:
https://github.com/apache/kafka/pull/16284
For this PR, I think it needs one more week to be completed.

Thanks.
Luke

On Wed, Jun 12, 2024 at 4:51 PM Josep Prat 
wrote:

> Hi all,
>
> We are now really close to the planned code freeze deadline (today EOD).
> According to KIP-1012 [1] we agreed to stay in the 3.x branch until we
> achieve feature parity regarding Zookeeper and KRaft. The two main KIPs
> identified that would achieve this are: KIP-853 [2] and KIP-966 [3].
> At the moment of writing this email both KIPs are not completed. My
> question to the people driving both KIPs would be, how much more time do
> you think it's needed to bring these KIPs to completion?
>
> - If the time needed would be short, we could still include these 2 KIPs in
> the release.
> - However, if the time needed would be on the scale of weeks, we should
> continue with the release plan for 3.8 and after start working on the 3.9
> release.
>
> What are your thoughts?
>
>
> [1]:
>
> https://cwiki.apache.org/confluence/display/KAFKA/KIP-1012%3A+The+need+for+a+Kafka+3.8.x+release
> [2]:
>
> https://cwiki.apache.org/confluence/display/KAFKA/KIP-853%3A+KRaft+Controller+Membership+Changes
> [3]:
>
> https://cwiki.apache.org/confluence/display/KAFKA/KIP-966%3A+Eligible+Leader+Replicas
>
> On Wed, Jun 12, 2024 at 10:40 AM Josep Prat  wrote:
>
> > Hi Rajini,
> > Yes, we could backport this one to the 3.8 branch. Would you be able to
> do
> > this once you merge this PR?
> >
> > Thanks
> >
> > On Tue, Jun 11, 2024 at 10:53 PM Rajini Sivaram  >
> > wrote:
> >
> >> Hi Josep,
> >>
> >> The PR https://github.com/apache/kafka/pull/13277 for KIP-899 looks
> ready
> >> to be merged (waiting for the PR build).The PR changes several files,
> but
> >> is relatively straightforward and not risky. Also the changes are under
> a
> >> config that is not enabled by default. Since the KIP was approved before
> >> KIP freeze, will it be ok to include in 3.8.0?
> >>
> >> Thank you,
> >>
> >> Rajini
> >>
> >>
> >> On Tue, Jun 11, 2024 at 9:35 AM Josep Prat  >
> >> wrote:
> >>
> >> > Hi all,
> >> >
> >> > I just want to remind everybody that the code freeze deadline is
> >> > approaching. June 12th EOD is the deadline.
> >> >
> >> > Please do not automatically backport any commit to the 3.8 branch
> after
> >> > June 12th EOD. Ping me if you think the commit should be backported
> >> (fixes
> >> > failures in the branch or critical bug fixes).
> >> >
> >> > Thanks all!
> >> >
> >> > On Sat, Jun 1, 2024 at 8:43 PM José Armando García Sancio
> >> >  wrote:
> >> >
> >> > > Hi Josep,
> >> > >
> >> > > See my comments below.
> >> > >
> >> > > On Wed, May 29, 2024 at 10:52 AM Josep Prat
> >>  >> > >
> >> > > wrote:
> >> > > > So I would propose to leave the deadlines as they are and manually
> >> > cherry
> >> > > > pick the commits related to KIP-853 and KIP-966.
> >> > >
> >> > > Your proposal sounds good to me. I suspect that will be doing
> feature
> >> > > development for KIP-853 past the feature freeze and code freeze
> date.
> >> > > Maybe feature development will be finished around the end of June.
> >> > >
> >> > > I'll make sure to cherry pick commits for KIP-853 to the 3.8 branch
> >> > > once we have one.
> >> > >
> >> > > Thanks,
> >> > > --
> >> > > -José
> >> > >
> >> >
> >> >
> >> > --
> >> > [image: Aiven] 
> >> >
> >> > *Josep Prat*
> >> > Open Source Engineering Director, *Aiven*
> >> > josep.p...@aiven.io   |   +491715557497
> >> > aiven.io    |   <
> >> https://www.facebook.com/aivencloud
> >> > >
> >> >      <
> >> > https://twitter.com/aiven_io>
> >> > *Aiven Deutschland GmbH*
> >> > Alexanderufer 3-7, 10117 Berlin
> >> > Geschäftsführer: Oskari Saarenmaa & Hannu Valtonen
> >> > Amtsgericht Charlottenburg, HRB 209739 B
> >> >
> >>
> >
> >
> > --
> > [image: Aiven] 
> >
> > *Josep Prat*
> > Open Source Engineering Director, *Aiven*
> > josep.p...@aiven.io   |   +491715557497
> > aiven.io    |
> > 
> >    <
> https://twitter.com/aiven_io>
> > *Aiven Deutschland GmbH*
> > Alexanderufer 3-7, 10117 Berlin
> > Geschäftsführer: Oskari Saarenmaa & Hannu Valtonen
> > Amtsgericht Charlottenburg, HRB 209739 B
> >
>
>
> --
> [image: Aiven] 
>
> *Josep Prat*
> Open Source Engineering Director, *Aiven*
> josep.p...@aiven.io   |   +491715557497
> aiven.io    |    >
>      <
> https://twitter.com/aiven_io>
> *Aiven Deutschland GmbH*
> Alexanderufer 3-7, 10117 Berlin
> Geschäftsführer: Oskari Saarenmaa & Hannu Valtonen
> Amtsgericht 

Re: [DISCUSS] Apache Kafka 3.8.0 release

[Rajini Sivaram]

>
> Yes, we could backport this one to the 3.8 branch. Would you be able to do
> this once you merge this PR?


Thanks Josep! There were some unit test failures in last night's PR build,
so I have commented on the PR for Ivan to fix. If he fixes it today, then I
can merge to trunk and then cherry-pick to 3.8 today.

Regards,

Rajini


On Wed, Jun 12, 2024 at 9:51 AM Josep Prat 
wrote:

> Hi all,
>
> We are now really close to the planned code freeze deadline (today EOD).
> According to KIP-1012 [1] we agreed to stay in the 3.x branch until we
> achieve feature parity regarding Zookeeper and KRaft. The two main KIPs
> identified that would achieve this are: KIP-853 [2] and KIP-966 [3].
> At the moment of writing this email both KIPs are not completed. My
> question to the people driving both KIPs would be, how much more time do
> you think it's needed to bring these KIPs to completion?
>
> - If the time needed would be short, we could still include these 2 KIPs in
> the release.
> - However, if the time needed would be on the scale of weeks, we should
> continue with the release plan for 3.8 and after start working on the 3.9
> release.
>
> What are your thoughts?
>
>
> [1]:
>
> https://cwiki.apache.org/confluence/display/KAFKA/KIP-1012%3A+The+need+for+a+Kafka+3.8.x+release
> [2]:
>
> https://cwiki.apache.org/confluence/display/KAFKA/KIP-853%3A+KRaft+Controller+Membership+Changes
> [3]:
>
> https://cwiki.apache.org/confluence/display/KAFKA/KIP-966%3A+Eligible+Leader+Replicas
>
> On Wed, Jun 12, 2024 at 10:40 AM Josep Prat  wrote:
>
> > Hi Rajini,
> > Yes, we could backport this one to the 3.8 branch. Would you be able to
> do
> > this once you merge this PR?
> >
> > Thanks
> >
> > On Tue, Jun 11, 2024 at 10:53 PM Rajini Sivaram  >
> > wrote:
> >
> >> Hi Josep,
> >>
> >> The PR https://github.com/apache/kafka/pull/13277 for KIP-899 looks
> ready
> >> to be merged (waiting for the PR build).The PR changes several files,
> but
> >> is relatively straightforward and not risky. Also the changes are under
> a
> >> config that is not enabled by default. Since the KIP was approved before
> >> KIP freeze, will it be ok to include in 3.8.0?
> >>
> >> Thank you,
> >>
> >> Rajini
> >>
> >>
> >> On Tue, Jun 11, 2024 at 9:35 AM Josep Prat  >
> >> wrote:
> >>
> >> > Hi all,
> >> >
> >> > I just want to remind everybody that the code freeze deadline is
> >> > approaching. June 12th EOD is the deadline.
> >> >
> >> > Please do not automatically backport any commit to the 3.8 branch
> after
> >> > June 12th EOD. Ping me if you think the commit should be backported
> >> (fixes
> >> > failures in the branch or critical bug fixes).
> >> >
> >> > Thanks all!
> >> >
> >> > On Sat, Jun 1, 2024 at 8:43 PM José Armando García Sancio
> >> >  wrote:
> >> >
> >> > > Hi Josep,
> >> > >
> >> > > See my comments below.
> >> > >
> >> > > On Wed, May 29, 2024 at 10:52 AM Josep Prat
> >>  >> > >
> >> > > wrote:
> >> > > > So I would propose to leave the deadlines as they are and manually
> >> > cherry
> >> > > > pick the commits related to KIP-853 and KIP-966.
> >> > >
> >> > > Your proposal sounds good to me. I suspect that will be doing
> feature
> >> > > development for KIP-853 past the feature freeze and code freeze
> date.
> >> > > Maybe feature development will be finished around the end of June.
> >> > >
> >> > > I'll make sure to cherry pick commits for KIP-853 to the 3.8 branch
> >> > > once we have one.
> >> > >
> >> > > Thanks,
> >> > > --
> >> > > -José
> >> > >
> >> >
> >> >
> >> > --
> >> > [image: Aiven] 
> >> >
> >> > *Josep Prat*
> >> > Open Source Engineering Director, *Aiven*
> >> > josep.p...@aiven.io   |   +491715557497
> >> > aiven.io    |   <
> >> https://www.facebook.com/aivencloud
> >> > >
> >> >      <
> >> > https://twitter.com/aiven_io>
> >> > *Aiven Deutschland GmbH*
> >> > Alexanderufer 3-7, 10117 Berlin
> >> > Geschäftsführer: Oskari Saarenmaa & Hannu Valtonen
> >> > Amtsgericht Charlottenburg, HRB 209739 B
> >> >
> >>
> >
> >
> > --
> > [image: Aiven] 
> >
> > *Josep Prat*
> > Open Source Engineering Director, *Aiven*
> > josep.p...@aiven.io   |   +491715557497
> > aiven.io    |
> > 
> >    <
> https://twitter.com/aiven_io>
> > *Aiven Deutschland GmbH*
> > Alexanderufer 3-7, 10117 Berlin
> > Geschäftsführer: Oskari Saarenmaa & Hannu Valtonen
> > Amtsgericht Charlottenburg, HRB 209739 B
> >
>
>
> --
> [image: Aiven] 
>
> *Josep Prat*
> Open Source Engineering Director, *Aiven*
> josep.p...@aiven.io   |   +491715557497
> aiven.io    |    >
>      <
> https://twitter.com/aiven_io>
> *Aiven Deutschland GmbH*
> Alexanderufer 3-7, 10117 Berlin
> Geschäftsführer: Oskari Saarenmaa & Hannu 

Re: [DISCUSS] Apache Kafka 3.8.0 release

[Josep Prat]

Hi all,

We are now really close to the planned code freeze deadline (today EOD).
According to KIP-1012 [1] we agreed to stay in the 3.x branch until we
achieve feature parity regarding Zookeeper and KRaft. The two main KIPs
identified that would achieve this are: KIP-853 [2] and KIP-966 [3].
At the moment of writing this email both KIPs are not completed. My
question to the people driving both KIPs would be, how much more time do
you think it's needed to bring these KIPs to completion?

- If the time needed would be short, we could still include these 2 KIPs in
the release.
- However, if the time needed would be on the scale of weeks, we should
continue with the release plan for 3.8 and after start working on the 3.9
release.

What are your thoughts?


[1]:
https://cwiki.apache.org/confluence/display/KAFKA/KIP-1012%3A+The+need+for+a+Kafka+3.8.x+release
[2]:
https://cwiki.apache.org/confluence/display/KAFKA/KIP-853%3A+KRaft+Controller+Membership+Changes
[3]:
https://cwiki.apache.org/confluence/display/KAFKA/KIP-966%3A+Eligible+Leader+Replicas

On Wed, Jun 12, 2024 at 10:40 AM Josep Prat  wrote:

> Hi Rajini,
> Yes, we could backport this one to the 3.8 branch. Would you be able to do
> this once you merge this PR?
>
> Thanks
>
> On Tue, Jun 11, 2024 at 10:53 PM Rajini Sivaram 
> wrote:
>
>> Hi Josep,
>>
>> The PR https://github.com/apache/kafka/pull/13277 for KIP-899 looks ready
>> to be merged (waiting for the PR build).The PR changes several files, but
>> is relatively straightforward and not risky. Also the changes are under a
>> config that is not enabled by default. Since the KIP was approved before
>> KIP freeze, will it be ok to include in 3.8.0?
>>
>> Thank you,
>>
>> Rajini
>>
>>
>> On Tue, Jun 11, 2024 at 9:35 AM Josep Prat 
>> wrote:
>>
>> > Hi all,
>> >
>> > I just want to remind everybody that the code freeze deadline is
>> > approaching. June 12th EOD is the deadline.
>> >
>> > Please do not automatically backport any commit to the 3.8 branch after
>> > June 12th EOD. Ping me if you think the commit should be backported
>> (fixes
>> > failures in the branch or critical bug fixes).
>> >
>> > Thanks all!
>> >
>> > On Sat, Jun 1, 2024 at 8:43 PM José Armando García Sancio
>> >  wrote:
>> >
>> > > Hi Josep,
>> > >
>> > > See my comments below.
>> > >
>> > > On Wed, May 29, 2024 at 10:52 AM Josep Prat
>> > > >
>> > > wrote:
>> > > > So I would propose to leave the deadlines as they are and manually
>> > cherry
>> > > > pick the commits related to KIP-853 and KIP-966.
>> > >
>> > > Your proposal sounds good to me. I suspect that will be doing feature
>> > > development for KIP-853 past the feature freeze and code freeze date.
>> > > Maybe feature development will be finished around the end of June.
>> > >
>> > > I'll make sure to cherry pick commits for KIP-853 to the 3.8 branch
>> > > once we have one.
>> > >
>> > > Thanks,
>> > > --
>> > > -José
>> > >
>> >
>> >
>> > --
>> > [image: Aiven] 
>> >
>> > *Josep Prat*
>> > Open Source Engineering Director, *Aiven*
>> > josep.p...@aiven.io   |   +491715557497
>> > aiven.io    |   <
>> https://www.facebook.com/aivencloud
>> > >
>> >      <
>> > https://twitter.com/aiven_io>
>> > *Aiven Deutschland GmbH*
>> > Alexanderufer 3-7, 10117 Berlin
>> > Geschäftsführer: Oskari Saarenmaa & Hannu Valtonen
>> > Amtsgericht Charlottenburg, HRB 209739 B
>> >
>>
>
>
> --
> [image: Aiven] 
>
> *Josep Prat*
> Open Source Engineering Director, *Aiven*
> josep.p...@aiven.io   |   +491715557497
> aiven.io    |
> 
>    
> *Aiven Deutschland GmbH*
> Alexanderufer 3-7, 10117 Berlin
> Geschäftsführer: Oskari Saarenmaa & Hannu Valtonen
> Amtsgericht Charlottenburg, HRB 209739 B
>


-- 
[image: Aiven] 

*Josep Prat*
Open Source Engineering Director, *Aiven*
josep.p...@aiven.io   |   +491715557497
aiven.io    |   
     
*Aiven Deutschland GmbH*
Alexanderufer 3-7, 10117 Berlin
Geschäftsführer: Oskari Saarenmaa & Hannu Valtonen
Amtsgericht Charlottenburg, HRB 209739 B

Re: [DISCUSS] Apache Kafka 3.8.0 release

[Josep Prat]

Hi Rajini,
Yes, we could backport this one to the 3.8 branch. Would you be able to do
this once you merge this PR?

Thanks

On Tue, Jun 11, 2024 at 10:53 PM Rajini Sivaram 
wrote:

> Hi Josep,
>
> The PR https://github.com/apache/kafka/pull/13277 for KIP-899 looks ready
> to be merged (waiting for the PR build).The PR changes several files, but
> is relatively straightforward and not risky. Also the changes are under a
> config that is not enabled by default. Since the KIP was approved before
> KIP freeze, will it be ok to include in 3.8.0?
>
> Thank you,
>
> Rajini
>
>
> On Tue, Jun 11, 2024 at 9:35 AM Josep Prat 
> wrote:
>
> > Hi all,
> >
> > I just want to remind everybody that the code freeze deadline is
> > approaching. June 12th EOD is the deadline.
> >
> > Please do not automatically backport any commit to the 3.8 branch after
> > June 12th EOD. Ping me if you think the commit should be backported
> (fixes
> > failures in the branch or critical bug fixes).
> >
> > Thanks all!
> >
> > On Sat, Jun 1, 2024 at 8:43 PM José Armando García Sancio
> >  wrote:
> >
> > > Hi Josep,
> > >
> > > See my comments below.
> > >
> > > On Wed, May 29, 2024 at 10:52 AM Josep Prat
>  > >
> > > wrote:
> > > > So I would propose to leave the deadlines as they are and manually
> > cherry
> > > > pick the commits related to KIP-853 and KIP-966.
> > >
> > > Your proposal sounds good to me. I suspect that will be doing feature
> > > development for KIP-853 past the feature freeze and code freeze date.
> > > Maybe feature development will be finished around the end of June.
> > >
> > > I'll make sure to cherry pick commits for KIP-853 to the 3.8 branch
> > > once we have one.
> > >
> > > Thanks,
> > > --
> > > -José
> > >
> >
> >
> > --
> > [image: Aiven] 
> >
> > *Josep Prat*
> > Open Source Engineering Director, *Aiven*
> > josep.p...@aiven.io   |   +491715557497
> > aiven.io    |   <
> https://www.facebook.com/aivencloud
> > >
> >      <
> > https://twitter.com/aiven_io>
> > *Aiven Deutschland GmbH*
> > Alexanderufer 3-7, 10117 Berlin
> > Geschäftsführer: Oskari Saarenmaa & Hannu Valtonen
> > Amtsgericht Charlottenburg, HRB 209739 B
> >
>


-- 
[image: Aiven] 

*Josep Prat*
Open Source Engineering Director, *Aiven*
josep.p...@aiven.io   |   +491715557497
aiven.io    |   
     
*Aiven Deutschland GmbH*
Alexanderufer 3-7, 10117 Berlin
Geschäftsführer: Oskari Saarenmaa & Hannu Valtonen
Amtsgericht Charlottenburg, HRB 209739 B

Re: [DISCUSS] Apache Kafka 3.8.0 release

[Rajini Sivaram]

Hi Josep,

The PR https://github.com/apache/kafka/pull/13277 for KIP-899 looks ready
to be merged (waiting for the PR build).The PR changes several files, but
is relatively straightforward and not risky. Also the changes are under a
config that is not enabled by default. Since the KIP was approved before
KIP freeze, will it be ok to include in 3.8.0?

Thank you,

Rajini


On Tue, Jun 11, 2024 at 9:35 AM Josep Prat 
wrote:

> Hi all,
>
> I just want to remind everybody that the code freeze deadline is
> approaching. June 12th EOD is the deadline.
>
> Please do not automatically backport any commit to the 3.8 branch after
> June 12th EOD. Ping me if you think the commit should be backported (fixes
> failures in the branch or critical bug fixes).
>
> Thanks all!
>
> On Sat, Jun 1, 2024 at 8:43 PM José Armando García Sancio
>  wrote:
>
> > Hi Josep,
> >
> > See my comments below.
> >
> > On Wed, May 29, 2024 at 10:52 AM Josep Prat  >
> > wrote:
> > > So I would propose to leave the deadlines as they are and manually
> cherry
> > > pick the commits related to KIP-853 and KIP-966.
> >
> > Your proposal sounds good to me. I suspect that will be doing feature
> > development for KIP-853 past the feature freeze and code freeze date.
> > Maybe feature development will be finished around the end of June.
> >
> > I'll make sure to cherry pick commits for KIP-853 to the 3.8 branch
> > once we have one.
> >
> > Thanks,
> > --
> > -José
> >
>
>
> --
> [image: Aiven] 
>
> *Josep Prat*
> Open Source Engineering Director, *Aiven*
> josep.p...@aiven.io   |   +491715557497
> aiven.io    |    >
>      <
> https://twitter.com/aiven_io>
> *Aiven Deutschland GmbH*
> Alexanderufer 3-7, 10117 Berlin
> Geschäftsführer: Oskari Saarenmaa & Hannu Valtonen
> Amtsgericht Charlottenburg, HRB 209739 B
>

Re: [DISCUSS] Apache Kafka 3.8.0 release

[Josep Prat]

Hi all,

I just want to remind everybody that the code freeze deadline is
approaching. June 12th EOD is the deadline.

Please do not automatically backport any commit to the 3.8 branch after
June 12th EOD. Ping me if you think the commit should be backported (fixes
failures in the branch or critical bug fixes).

Thanks all!

On Sat, Jun 1, 2024 at 8:43 PM José Armando García Sancio
 wrote:

> Hi Josep,
>
> See my comments below.
>
> On Wed, May 29, 2024 at 10:52 AM Josep Prat 
> wrote:
> > So I would propose to leave the deadlines as they are and manually cherry
> > pick the commits related to KIP-853 and KIP-966.
>
> Your proposal sounds good to me. I suspect that will be doing feature
> development for KIP-853 past the feature freeze and code freeze date.
> Maybe feature development will be finished around the end of June.
>
> I'll make sure to cherry pick commits for KIP-853 to the 3.8 branch
> once we have one.
>
> Thanks,
> --
> -José
>


-- 
[image: Aiven] 

*Josep Prat*
Open Source Engineering Director, *Aiven*
josep.p...@aiven.io   |   +491715557497
aiven.io    |   
     
*Aiven Deutschland GmbH*
Alexanderufer 3-7, 10117 Berlin
Geschäftsführer: Oskari Saarenmaa & Hannu Valtonen
Amtsgericht Charlottenburg, HRB 209739 B

Re: [DISCUSS] Apache Kafka 3.8.0 release

[José Armando García Sancio]

Hi Josep,

See my comments below.

On Wed, May 29, 2024 at 10:52 AM Josep Prat  wrote:
> So I would propose to leave the deadlines as they are and manually cherry
> pick the commits related to KIP-853 and KIP-966.

Your proposal sounds good to me. I suspect that will be doing feature
development for KIP-853 past the feature freeze and code freeze date.
Maybe feature development will be finished around the end of June.

I'll make sure to cherry pick commits for KIP-853 to the 3.8 branch
once we have one.

Thanks,
-- 
-José

Re: [DISCUSS] Apache Kafka 3.8.0 release

[Justine Olshan]

Makes sense to me.

On Fri, May 31, 2024 at 2:05 AM Luke Chen  wrote:

> Hi Justine,
>
> In the KIP-1012 discussion thread
> , our
> conclusion should be having an "automatic" unclean leader election in
> KRaft, even if KIP-966 cannot complete in time.
>
> > We should specify in KIP-1012 that we need to have some way to configure
> the system to automatically do unclean leader election. If we run out of
> time implementing KIP-966, this could be something quite simple, like
> honoring the static unclean.leader.election = true configuration.
>
> I think we still need to include this in v3.8.0, to honor the static
> unclean.leader.election = true configuration.
>
> Thanks.
> Luke
>
>
>
> On Fri, May 31, 2024 at 1:55 AM Justine Olshan
> 
> wrote:
>
> > My understanding is on Kraft, automatic unclean leadership election is
> > disabled, but it can be manually triggered.
> >
> > See this note from Colin on another email thread:
> > > We do have the concept of unclean leader election in KRaft, but it has
> to
> > be triggered by the leader election tool currently. We've been talking
> > about adding configuration-based unclean leader election as part of the
> > KIP-966 work.
> >
> > Just wanted to add this clarification.
> >
> > Justine
> >
> > On Thu, May 30, 2024 at 9:38 AM Calvin Liu 
> > wrote:
> >
> > > Hi Mickael,
> > > Part 1 adds the ELR and enables the leader election improvements
> related
> > to
> > > ELR. It does not change unclean leader election behavior which I think
> is
> > > hard-coded to be disabled.
> > > Part 2 should replace the current unclean leader election with the
> > unclean
> > > recovery. Colin McCabe will help with part 2 as the Kraft controller
> > > expert. Thanks Colin!
> > >
> > >
> > >
> > >
> > > On Thu, May 30, 2024 at 2:43 AM Mickael Maison <
> mickael.mai...@gmail.com
> > >
> > > wrote:
> > >
> > > > Hi Calvin,
> > > >
> > > > What's not clear from your reply is whether "KIP-966 Part 1" contains
> > > > the ability to perform unclean leader elections with KRaft?
> > > > Hopefully we have committers already looking at these. If you need
> > > > additional help, please shout (well ping!)
> > > >
> > > > Thanks,
> > > > Mickael
> > > >
> > > > On Thu, May 30, 2024 at 6:05 AM Ismael Juma 
> wrote:
> > > > >
> > > > > Sounds good, thanks Josep!
> > > > >
> > > > > Ismael
> > > > >
> > > > > On Wed, May 29, 2024 at 7:51 AM Josep Prat
> >  > > >
> > > > > wrote:
> > > > >
> > > > > > Hi Ismael,
> > > > > >
> > > > > > I think your proposal makes more sense than mine. The end goal is
> > to
> > > > try to
> > > > > > get these 2 KIPs in 3.8.0 if possible. I think we can also
> achieve
> > > > this by
> > > > > > not delaying the general feature freeze, but rather by cherry
> > picking
> > > > the
> > > > > > future commits on these features to the 3.8 branch.
> > > > > >
> > > > > > So I would propose to leave the deadlines as they are and
> manually
> > > > cherry
> > > > > > pick the commits related to KIP-853 and KIP-966.
> > > > > >
> > > > > > Best,
> > > > > >
> > > > > > On Wed, May 29, 2024 at 3:48 PM Ismael Juma 
> > > wrote:
> > > > > >
> > > > > > > Hi Josep,
> > > > > > >
> > > > > > > It's generally a bad idea to push these dates because the scope
> > > keeps
> > > > > > > increasing then. If there are features that need more time and
> we
> > > > believe
> > > > > > > they are essential for 3.8 due to its special nature as the
> last
> > > > release
> > > > > > > before 4.0, we should allow them to be cherry-picked to the
> > release
> > > > > > branch
> > > > > > > versus delaying the feature freeze and code freeze for
> > everything.
> > > > > > >
> > > > > > > Ismael
> > > > > > >
> > > > > > > On Wed, May 29, 2024 at 2:38 AM Josep Prat
> > > > 
> > > > > > > wrote:
> > > > > > >
> > > > > > > > Hi Kafka developers,
> > > > > > > >
> > > > > > > > Given the fact we have a couple of KIPs that are halfway
> > through
> > > > their
> > > > > > > > implementation and it seems it's a matter of days (1 or 2
> > weeks)
> > > to
> > > > > > have
> > > > > > > > them completed. What would you think if we delay feature
> freeze
> > > and
> > > > > > code
> > > > > > > > freeze by 2 weeks? Let me know your thoughts.
> > > > > > > >
> > > > > > > > Best,
> > > > > > > >
> > > > > > > > On Tue, May 28, 2024 at 8:47 AM Josep Prat <
> > josep.p...@aiven.io>
> > > > > > wrote:
> > > > > > > >
> > > > > > > > > Hi Kafka developers,
> > > > > > > > >
> > > > > > > > > This is a reminder about the upcoming deadlines:
> > > > > > > > > - Feature freeze is on May 29th
> > > > > > > > > - Code freeze is June 12th
> > > > > > > > >
> > > > > > > > > I'll cut the new branch during morning hours (CEST) on May
> > > 30th.
> > > > > > > > >
> > > > > > > > > Thanks all!
> > > > > > > > >
> > > > > > > > > On Thu, May 16, 2024 at 8:34 AM Josep Prat <
> > > josep.p...@aiven.io>
> > > > > > > wrote:
> > > > > > > > >
> > > > > 

Re: [DISCUSS] Apache Kafka 3.8.0 release

[Luke Chen]

Hi Justine,

In the KIP-1012 discussion thread
, our
conclusion should be having an "automatic" unclean leader election in
KRaft, even if KIP-966 cannot complete in time.

> We should specify in KIP-1012 that we need to have some way to configure
the system to automatically do unclean leader election. If we run out of
time implementing KIP-966, this could be something quite simple, like
honoring the static unclean.leader.election = true configuration.

I think we still need to include this in v3.8.0, to honor the static
unclean.leader.election = true configuration.

Thanks.
Luke



On Fri, May 31, 2024 at 1:55 AM Justine Olshan 
wrote:

> My understanding is on Kraft, automatic unclean leadership election is
> disabled, but it can be manually triggered.
>
> See this note from Colin on another email thread:
> > We do have the concept of unclean leader election in KRaft, but it has to
> be triggered by the leader election tool currently. We've been talking
> about adding configuration-based unclean leader election as part of the
> KIP-966 work.
>
> Just wanted to add this clarification.
>
> Justine
>
> On Thu, May 30, 2024 at 9:38 AM Calvin Liu 
> wrote:
>
> > Hi Mickael,
> > Part 1 adds the ELR and enables the leader election improvements related
> to
> > ELR. It does not change unclean leader election behavior which I think is
> > hard-coded to be disabled.
> > Part 2 should replace the current unclean leader election with the
> unclean
> > recovery. Colin McCabe will help with part 2 as the Kraft controller
> > expert. Thanks Colin!
> >
> >
> >
> >
> > On Thu, May 30, 2024 at 2:43 AM Mickael Maison  >
> > wrote:
> >
> > > Hi Calvin,
> > >
> > > What's not clear from your reply is whether "KIP-966 Part 1" contains
> > > the ability to perform unclean leader elections with KRaft?
> > > Hopefully we have committers already looking at these. If you need
> > > additional help, please shout (well ping!)
> > >
> > > Thanks,
> > > Mickael
> > >
> > > On Thu, May 30, 2024 at 6:05 AM Ismael Juma  wrote:
> > > >
> > > > Sounds good, thanks Josep!
> > > >
> > > > Ismael
> > > >
> > > > On Wed, May 29, 2024 at 7:51 AM Josep Prat
>  > >
> > > > wrote:
> > > >
> > > > > Hi Ismael,
> > > > >
> > > > > I think your proposal makes more sense than mine. The end goal is
> to
> > > try to
> > > > > get these 2 KIPs in 3.8.0 if possible. I think we can also achieve
> > > this by
> > > > > not delaying the general feature freeze, but rather by cherry
> picking
> > > the
> > > > > future commits on these features to the 3.8 branch.
> > > > >
> > > > > So I would propose to leave the deadlines as they are and manually
> > > cherry
> > > > > pick the commits related to KIP-853 and KIP-966.
> > > > >
> > > > > Best,
> > > > >
> > > > > On Wed, May 29, 2024 at 3:48 PM Ismael Juma 
> > wrote:
> > > > >
> > > > > > Hi Josep,
> > > > > >
> > > > > > It's generally a bad idea to push these dates because the scope
> > keeps
> > > > > > increasing then. If there are features that need more time and we
> > > believe
> > > > > > they are essential for 3.8 due to its special nature as the last
> > > release
> > > > > > before 4.0, we should allow them to be cherry-picked to the
> release
> > > > > branch
> > > > > > versus delaying the feature freeze and code freeze for
> everything.
> > > > > >
> > > > > > Ismael
> > > > > >
> > > > > > On Wed, May 29, 2024 at 2:38 AM Josep Prat
> > > 
> > > > > > wrote:
> > > > > >
> > > > > > > Hi Kafka developers,
> > > > > > >
> > > > > > > Given the fact we have a couple of KIPs that are halfway
> through
> > > their
> > > > > > > implementation and it seems it's a matter of days (1 or 2
> weeks)
> > to
> > > > > have
> > > > > > > them completed. What would you think if we delay feature freeze
> > and
> > > > > code
> > > > > > > freeze by 2 weeks? Let me know your thoughts.
> > > > > > >
> > > > > > > Best,
> > > > > > >
> > > > > > > On Tue, May 28, 2024 at 8:47 AM Josep Prat <
> josep.p...@aiven.io>
> > > > > wrote:
> > > > > > >
> > > > > > > > Hi Kafka developers,
> > > > > > > >
> > > > > > > > This is a reminder about the upcoming deadlines:
> > > > > > > > - Feature freeze is on May 29th
> > > > > > > > - Code freeze is June 12th
> > > > > > > >
> > > > > > > > I'll cut the new branch during morning hours (CEST) on May
> > 30th.
> > > > > > > >
> > > > > > > > Thanks all!
> > > > > > > >
> > > > > > > > On Thu, May 16, 2024 at 8:34 AM Josep Prat <
> > josep.p...@aiven.io>
> > > > > > wrote:
> > > > > > > >
> > > > > > > >> Hi all,
> > > > > > > >>
> > > > > > > >> We are now officially past the KIP freeze deadline. KIPs
> that
> > > are
> > > > > > > >> approved after this point in time shouldn't be adopted in
> the
> > > 3.8.x
> > > > > > > release
> > > > > > > >> (except the 2 already mentioned KIPS 989 and 1028 assuming
> no
> > > vetoes
> > > > > > > occur).
> > > > > > > >>
> > > > > > > >> Reminder of the upcoming 

Re: [DISCUSS] Apache Kafka 3.8.0 release

[Justine Olshan]

My understanding is on Kraft, automatic unclean leadership election is
disabled, but it can be manually triggered.

See this note from Colin on another email thread:
> We do have the concept of unclean leader election in KRaft, but it has to
be triggered by the leader election tool currently. We've been talking
about adding configuration-based unclean leader election as part of the
KIP-966 work.

Just wanted to add this clarification.

Justine

On Thu, May 30, 2024 at 9:38 AM Calvin Liu 
wrote:

> Hi Mickael,
> Part 1 adds the ELR and enables the leader election improvements related to
> ELR. It does not change unclean leader election behavior which I think is
> hard-coded to be disabled.
> Part 2 should replace the current unclean leader election with the unclean
> recovery. Colin McCabe will help with part 2 as the Kraft controller
> expert. Thanks Colin!
>
>
>
>
> On Thu, May 30, 2024 at 2:43 AM Mickael Maison 
> wrote:
>
> > Hi Calvin,
> >
> > What's not clear from your reply is whether "KIP-966 Part 1" contains
> > the ability to perform unclean leader elections with KRaft?
> > Hopefully we have committers already looking at these. If you need
> > additional help, please shout (well ping!)
> >
> > Thanks,
> > Mickael
> >
> > On Thu, May 30, 2024 at 6:05 AM Ismael Juma  wrote:
> > >
> > > Sounds good, thanks Josep!
> > >
> > > Ismael
> > >
> > > On Wed, May 29, 2024 at 7:51 AM Josep Prat  >
> > > wrote:
> > >
> > > > Hi Ismael,
> > > >
> > > > I think your proposal makes more sense than mine. The end goal is to
> > try to
> > > > get these 2 KIPs in 3.8.0 if possible. I think we can also achieve
> > this by
> > > > not delaying the general feature freeze, but rather by cherry picking
> > the
> > > > future commits on these features to the 3.8 branch.
> > > >
> > > > So I would propose to leave the deadlines as they are and manually
> > cherry
> > > > pick the commits related to KIP-853 and KIP-966.
> > > >
> > > > Best,
> > > >
> > > > On Wed, May 29, 2024 at 3:48 PM Ismael Juma 
> wrote:
> > > >
> > > > > Hi Josep,
> > > > >
> > > > > It's generally a bad idea to push these dates because the scope
> keeps
> > > > > increasing then. If there are features that need more time and we
> > believe
> > > > > they are essential for 3.8 due to its special nature as the last
> > release
> > > > > before 4.0, we should allow them to be cherry-picked to the release
> > > > branch
> > > > > versus delaying the feature freeze and code freeze for everything.
> > > > >
> > > > > Ismael
> > > > >
> > > > > On Wed, May 29, 2024 at 2:38 AM Josep Prat
> > 
> > > > > wrote:
> > > > >
> > > > > > Hi Kafka developers,
> > > > > >
> > > > > > Given the fact we have a couple of KIPs that are halfway through
> > their
> > > > > > implementation and it seems it's a matter of days (1 or 2 weeks)
> to
> > > > have
> > > > > > them completed. What would you think if we delay feature freeze
> and
> > > > code
> > > > > > freeze by 2 weeks? Let me know your thoughts.
> > > > > >
> > > > > > Best,
> > > > > >
> > > > > > On Tue, May 28, 2024 at 8:47 AM Josep Prat 
> > > > wrote:
> > > > > >
> > > > > > > Hi Kafka developers,
> > > > > > >
> > > > > > > This is a reminder about the upcoming deadlines:
> > > > > > > - Feature freeze is on May 29th
> > > > > > > - Code freeze is June 12th
> > > > > > >
> > > > > > > I'll cut the new branch during morning hours (CEST) on May
> 30th.
> > > > > > >
> > > > > > > Thanks all!
> > > > > > >
> > > > > > > On Thu, May 16, 2024 at 8:34 AM Josep Prat <
> josep.p...@aiven.io>
> > > > > wrote:
> > > > > > >
> > > > > > >> Hi all,
> > > > > > >>
> > > > > > >> We are now officially past the KIP freeze deadline. KIPs that
> > are
> > > > > > >> approved after this point in time shouldn't be adopted in the
> > 3.8.x
> > > > > > release
> > > > > > >> (except the 2 already mentioned KIPS 989 and 1028 assuming no
> > vetoes
> > > > > > occur).
> > > > > > >>
> > > > > > >> Reminder of the upcoming deadlines:
> > > > > > >> - Feature freeze is on May 29th
> > > > > > >> - Code freeze is June 12th
> > > > > > >>
> > > > > > >> If you have an approved KIP that you know already you won't be
> > able
> > > > to
> > > > > > >> complete before the feature freeze deadline, please update the
> > > > Release
> > > > > > >> column in the
> > > > > > >>
> > > > > >
> > > > >
> > > >
> >
> https://cwiki.apache.org/confluence/display/KAFKA/Kafka+Improvement+Proposals
> > > > > > >> page.
> > > > > > >>
> > > > > > >> Thanks all,
> > > > > > >>
> > > > > > >> On Wed, May 15, 2024 at 8:53 PM Josep Prat <
> josep.p...@aiven.io
> > >
> > > > > wrote:
> > > > > > >>
> > > > > > >>> Hi Nick,
> > > > > > >>>
> > > > > > >>> If nobody comes up with concerns or pushback until the time
> of
> > > > > closing
> > > > > > >>> the vote, I think we can take it for 3.8.
> > > > > > >>>
> > > > > > >>> Best,
> > > > > > >>>
> > > > > > >>> -
> > > > > > >>>
> > > > > > >>> Josep Prat
> > > > > > >>> Open Source 

Re: [DISCUSS] Apache Kafka 3.8.0 release

[Calvin Liu]

Hi Mickael,
Part 1 adds the ELR and enables the leader election improvements related to
ELR. It does not change unclean leader election behavior which I think is
hard-coded to be disabled.
Part 2 should replace the current unclean leader election with the unclean
recovery. Colin McCabe will help with part 2 as the Kraft controller
expert. Thanks Colin!




On Thu, May 30, 2024 at 2:43 AM Mickael Maison 
wrote:

> Hi Calvin,
>
> What's not clear from your reply is whether "KIP-966 Part 1" contains
> the ability to perform unclean leader elections with KRaft?
> Hopefully we have committers already looking at these. If you need
> additional help, please shout (well ping!)
>
> Thanks,
> Mickael
>
> On Thu, May 30, 2024 at 6:05 AM Ismael Juma  wrote:
> >
> > Sounds good, thanks Josep!
> >
> > Ismael
> >
> > On Wed, May 29, 2024 at 7:51 AM Josep Prat 
> > wrote:
> >
> > > Hi Ismael,
> > >
> > > I think your proposal makes more sense than mine. The end goal is to
> try to
> > > get these 2 KIPs in 3.8.0 if possible. I think we can also achieve
> this by
> > > not delaying the general feature freeze, but rather by cherry picking
> the
> > > future commits on these features to the 3.8 branch.
> > >
> > > So I would propose to leave the deadlines as they are and manually
> cherry
> > > pick the commits related to KIP-853 and KIP-966.
> > >
> > > Best,
> > >
> > > On Wed, May 29, 2024 at 3:48 PM Ismael Juma  wrote:
> > >
> > > > Hi Josep,
> > > >
> > > > It's generally a bad idea to push these dates because the scope keeps
> > > > increasing then. If there are features that need more time and we
> believe
> > > > they are essential for 3.8 due to its special nature as the last
> release
> > > > before 4.0, we should allow them to be cherry-picked to the release
> > > branch
> > > > versus delaying the feature freeze and code freeze for everything.
> > > >
> > > > Ismael
> > > >
> > > > On Wed, May 29, 2024 at 2:38 AM Josep Prat
> 
> > > > wrote:
> > > >
> > > > > Hi Kafka developers,
> > > > >
> > > > > Given the fact we have a couple of KIPs that are halfway through
> their
> > > > > implementation and it seems it's a matter of days (1 or 2 weeks) to
> > > have
> > > > > them completed. What would you think if we delay feature freeze and
> > > code
> > > > > freeze by 2 weeks? Let me know your thoughts.
> > > > >
> > > > > Best,
> > > > >
> > > > > On Tue, May 28, 2024 at 8:47 AM Josep Prat 
> > > wrote:
> > > > >
> > > > > > Hi Kafka developers,
> > > > > >
> > > > > > This is a reminder about the upcoming deadlines:
> > > > > > - Feature freeze is on May 29th
> > > > > > - Code freeze is June 12th
> > > > > >
> > > > > > I'll cut the new branch during morning hours (CEST) on May 30th.
> > > > > >
> > > > > > Thanks all!
> > > > > >
> > > > > > On Thu, May 16, 2024 at 8:34 AM Josep Prat 
> > > > wrote:
> > > > > >
> > > > > >> Hi all,
> > > > > >>
> > > > > >> We are now officially past the KIP freeze deadline. KIPs that
> are
> > > > > >> approved after this point in time shouldn't be adopted in the
> 3.8.x
> > > > > release
> > > > > >> (except the 2 already mentioned KIPS 989 and 1028 assuming no
> vetoes
> > > > > occur).
> > > > > >>
> > > > > >> Reminder of the upcoming deadlines:
> > > > > >> - Feature freeze is on May 29th
> > > > > >> - Code freeze is June 12th
> > > > > >>
> > > > > >> If you have an approved KIP that you know already you won't be
> able
> > > to
> > > > > >> complete before the feature freeze deadline, please update the
> > > Release
> > > > > >> column in the
> > > > > >>
> > > > >
> > > >
> > >
> https://cwiki.apache.org/confluence/display/KAFKA/Kafka+Improvement+Proposals
> > > > > >> page.
> > > > > >>
> > > > > >> Thanks all,
> > > > > >>
> > > > > >> On Wed, May 15, 2024 at 8:53 PM Josep Prat  >
> > > > wrote:
> > > > > >>
> > > > > >>> Hi Nick,
> > > > > >>>
> > > > > >>> If nobody comes up with concerns or pushback until the time of
> > > > closing
> > > > > >>> the vote, I think we can take it for 3.8.
> > > > > >>>
> > > > > >>> Best,
> > > > > >>>
> > > > > >>> -
> > > > > >>>
> > > > > >>> Josep Prat
> > > > > >>> Open Source Engineering Director, aivenjosep.p...@aiven.io   |
> > > > > >>> +491715557497 | aiven.io
> > > > > >>> Aiven Deutschland GmbH
> > > > > >>> Alexanderufer 3-7, 10117 Berlin
> > > > > >>> Geschäftsführer: Oskari Saarenmaa & Hannu Valtonen
> > > > > >>> Amtsgericht Charlottenburg, HRB 209739 B
> > > > > >>>
> > > > > >>> On Wed, May 15, 2024, 20:48 Nick Telford <
> nick.telf...@gmail.com>
> > > > > wrote:
> > > > > >>>
> > > > >  Hi Josep,
> > > > > 
> > > > >  Would it be possible to sneak KIP-989 into 3.8? Just as with
> 1028,
> > > > > it's
> > > > >  currently being voted on and has already received the
> requisite
> > > > votes.
> > > > >  The
> > > > >  only thing holding it back is the 72 hour voting window.
> > > > > 
> > > > >  Vote thread here:
> > > > > 
> 

Re: [DISCUSS] Apache Kafka 3.8.0 release

[Mickael Maison]

Hi Calvin,

What's not clear from your reply is whether "KIP-966 Part 1" contains
the ability to perform unclean leader elections with KRaft?
Hopefully we have committers already looking at these. If you need
additional help, please shout (well ping!)

Thanks,
Mickael

On Thu, May 30, 2024 at 6:05 AM Ismael Juma  wrote:
>
> Sounds good, thanks Josep!
>
> Ismael
>
> On Wed, May 29, 2024 at 7:51 AM Josep Prat 
> wrote:
>
> > Hi Ismael,
> >
> > I think your proposal makes more sense than mine. The end goal is to try to
> > get these 2 KIPs in 3.8.0 if possible. I think we can also achieve this by
> > not delaying the general feature freeze, but rather by cherry picking the
> > future commits on these features to the 3.8 branch.
> >
> > So I would propose to leave the deadlines as they are and manually cherry
> > pick the commits related to KIP-853 and KIP-966.
> >
> > Best,
> >
> > On Wed, May 29, 2024 at 3:48 PM Ismael Juma  wrote:
> >
> > > Hi Josep,
> > >
> > > It's generally a bad idea to push these dates because the scope keeps
> > > increasing then. If there are features that need more time and we believe
> > > they are essential for 3.8 due to its special nature as the last release
> > > before 4.0, we should allow them to be cherry-picked to the release
> > branch
> > > versus delaying the feature freeze and code freeze for everything.
> > >
> > > Ismael
> > >
> > > On Wed, May 29, 2024 at 2:38 AM Josep Prat 
> > > wrote:
> > >
> > > > Hi Kafka developers,
> > > >
> > > > Given the fact we have a couple of KIPs that are halfway through their
> > > > implementation and it seems it's a matter of days (1 or 2 weeks) to
> > have
> > > > them completed. What would you think if we delay feature freeze and
> > code
> > > > freeze by 2 weeks? Let me know your thoughts.
> > > >
> > > > Best,
> > > >
> > > > On Tue, May 28, 2024 at 8:47 AM Josep Prat 
> > wrote:
> > > >
> > > > > Hi Kafka developers,
> > > > >
> > > > > This is a reminder about the upcoming deadlines:
> > > > > - Feature freeze is on May 29th
> > > > > - Code freeze is June 12th
> > > > >
> > > > > I'll cut the new branch during morning hours (CEST) on May 30th.
> > > > >
> > > > > Thanks all!
> > > > >
> > > > > On Thu, May 16, 2024 at 8:34 AM Josep Prat 
> > > wrote:
> > > > >
> > > > >> Hi all,
> > > > >>
> > > > >> We are now officially past the KIP freeze deadline. KIPs that are
> > > > >> approved after this point in time shouldn't be adopted in the 3.8.x
> > > > release
> > > > >> (except the 2 already mentioned KIPS 989 and 1028 assuming no vetoes
> > > > occur).
> > > > >>
> > > > >> Reminder of the upcoming deadlines:
> > > > >> - Feature freeze is on May 29th
> > > > >> - Code freeze is June 12th
> > > > >>
> > > > >> If you have an approved KIP that you know already you won't be able
> > to
> > > > >> complete before the feature freeze deadline, please update the
> > Release
> > > > >> column in the
> > > > >>
> > > >
> > >
> > https://cwiki.apache.org/confluence/display/KAFKA/Kafka+Improvement+Proposals
> > > > >> page.
> > > > >>
> > > > >> Thanks all,
> > > > >>
> > > > >> On Wed, May 15, 2024 at 8:53 PM Josep Prat 
> > > wrote:
> > > > >>
> > > > >>> Hi Nick,
> > > > >>>
> > > > >>> If nobody comes up with concerns or pushback until the time of
> > > closing
> > > > >>> the vote, I think we can take it for 3.8.
> > > > >>>
> > > > >>> Best,
> > > > >>>
> > > > >>> -
> > > > >>>
> > > > >>> Josep Prat
> > > > >>> Open Source Engineering Director, aivenjosep.p...@aiven.io   |
> > > > >>> +491715557497 | aiven.io
> > > > >>> Aiven Deutschland GmbH
> > > > >>> Alexanderufer 3-7, 10117 Berlin
> > > > >>> Geschäftsführer: Oskari Saarenmaa & Hannu Valtonen
> > > > >>> Amtsgericht Charlottenburg, HRB 209739 B
> > > > >>>
> > > > >>> On Wed, May 15, 2024, 20:48 Nick Telford 
> > > > wrote:
> > > > >>>
> > > >  Hi Josep,
> > > > 
> > > >  Would it be possible to sneak KIP-989 into 3.8? Just as with 1028,
> > > > it's
> > > >  currently being voted on and has already received the requisite
> > > votes.
> > > >  The
> > > >  only thing holding it back is the 72 hour voting window.
> > > > 
> > > >  Vote thread here:
> > > >  https://lists.apache.org/thread/nhr65h4784z49jbsyt5nx8ys81q90k6s
> > > > 
> > > >  Regards,
> > > > 
> > > >  Nick
> > > > 
> > > >  On Wed, 15 May 2024 at 17:47, Josep Prat
> > >  > > > >
> > > >  wrote:
> > > > 
> > > >  > And my maths are wrong! I added 24 hours more to all the numbers
> > > in
> > > >  there.
> > > >  > If after 72 hours no vetoes appear, I have no objections on
> > adding
> > > >  this
> > > >  > specific KIP as it shouldn't have a big blast radius of
> > > affectation.
> > > >  >
> > > >  > Best,
> > > >  >
> > > >  > On Wed, May 15, 2024 at 6:44 PM Josep Prat  > >
> > > >  wrote:
> > > >  >
> > > >  > > Ah, I see Chris was faster writing this than me.
> > > >  > 

Re: [DISCUSS] Apache Kafka 3.8.0 release

[Ismael Juma]

Sounds good, thanks Josep!

Ismael

On Wed, May 29, 2024 at 7:51 AM Josep Prat 
wrote:

> Hi Ismael,
>
> I think your proposal makes more sense than mine. The end goal is to try to
> get these 2 KIPs in 3.8.0 if possible. I think we can also achieve this by
> not delaying the general feature freeze, but rather by cherry picking the
> future commits on these features to the 3.8 branch.
>
> So I would propose to leave the deadlines as they are and manually cherry
> pick the commits related to KIP-853 and KIP-966.
>
> Best,
>
> On Wed, May 29, 2024 at 3:48 PM Ismael Juma  wrote:
>
> > Hi Josep,
> >
> > It's generally a bad idea to push these dates because the scope keeps
> > increasing then. If there are features that need more time and we believe
> > they are essential for 3.8 due to its special nature as the last release
> > before 4.0, we should allow them to be cherry-picked to the release
> branch
> > versus delaying the feature freeze and code freeze for everything.
> >
> > Ismael
> >
> > On Wed, May 29, 2024 at 2:38 AM Josep Prat 
> > wrote:
> >
> > > Hi Kafka developers,
> > >
> > > Given the fact we have a couple of KIPs that are halfway through their
> > > implementation and it seems it's a matter of days (1 or 2 weeks) to
> have
> > > them completed. What would you think if we delay feature freeze and
> code
> > > freeze by 2 weeks? Let me know your thoughts.
> > >
> > > Best,
> > >
> > > On Tue, May 28, 2024 at 8:47 AM Josep Prat 
> wrote:
> > >
> > > > Hi Kafka developers,
> > > >
> > > > This is a reminder about the upcoming deadlines:
> > > > - Feature freeze is on May 29th
> > > > - Code freeze is June 12th
> > > >
> > > > I'll cut the new branch during morning hours (CEST) on May 30th.
> > > >
> > > > Thanks all!
> > > >
> > > > On Thu, May 16, 2024 at 8:34 AM Josep Prat 
> > wrote:
> > > >
> > > >> Hi all,
> > > >>
> > > >> We are now officially past the KIP freeze deadline. KIPs that are
> > > >> approved after this point in time shouldn't be adopted in the 3.8.x
> > > release
> > > >> (except the 2 already mentioned KIPS 989 and 1028 assuming no vetoes
> > > occur).
> > > >>
> > > >> Reminder of the upcoming deadlines:
> > > >> - Feature freeze is on May 29th
> > > >> - Code freeze is June 12th
> > > >>
> > > >> If you have an approved KIP that you know already you won't be able
> to
> > > >> complete before the feature freeze deadline, please update the
> Release
> > > >> column in the
> > > >>
> > >
> >
> https://cwiki.apache.org/confluence/display/KAFKA/Kafka+Improvement+Proposals
> > > >> page.
> > > >>
> > > >> Thanks all,
> > > >>
> > > >> On Wed, May 15, 2024 at 8:53 PM Josep Prat 
> > wrote:
> > > >>
> > > >>> Hi Nick,
> > > >>>
> > > >>> If nobody comes up with concerns or pushback until the time of
> > closing
> > > >>> the vote, I think we can take it for 3.8.
> > > >>>
> > > >>> Best,
> > > >>>
> > > >>> -
> > > >>>
> > > >>> Josep Prat
> > > >>> Open Source Engineering Director, aivenjosep.p...@aiven.io   |
> > > >>> +491715557497 | aiven.io
> > > >>> Aiven Deutschland GmbH
> > > >>> Alexanderufer 3-7, 10117 Berlin
> > > >>> Geschäftsführer: Oskari Saarenmaa & Hannu Valtonen
> > > >>> Amtsgericht Charlottenburg, HRB 209739 B
> > > >>>
> > > >>> On Wed, May 15, 2024, 20:48 Nick Telford 
> > > wrote:
> > > >>>
> > >  Hi Josep,
> > > 
> > >  Would it be possible to sneak KIP-989 into 3.8? Just as with 1028,
> > > it's
> > >  currently being voted on and has already received the requisite
> > votes.
> > >  The
> > >  only thing holding it back is the 72 hour voting window.
> > > 
> > >  Vote thread here:
> > >  https://lists.apache.org/thread/nhr65h4784z49jbsyt5nx8ys81q90k6s
> > > 
> > >  Regards,
> > > 
> > >  Nick
> > > 
> > >  On Wed, 15 May 2024 at 17:47, Josep Prat
> >  > > >
> > >  wrote:
> > > 
> > >  > And my maths are wrong! I added 24 hours more to all the numbers
> > in
> > >  there.
> > >  > If after 72 hours no vetoes appear, I have no objections on
> adding
> > >  this
> > >  > specific KIP as it shouldn't have a big blast radius of
> > affectation.
> > >  >
> > >  > Best,
> > >  >
> > >  > On Wed, May 15, 2024 at 6:44 PM Josep Prat  >
> > >  wrote:
> > >  >
> > >  > > Ah, I see Chris was faster writing this than me.
> > >  > >
> > >  > > On Wed, May 15, 2024 at 6:43 PM Josep Prat <
> josep.p...@aiven.io
> > >
> > >  wrote:
> > >  > >
> > >  > >> Hi all,
> > >  > >> You still have the full day of today (independently for the
> > >  timezone) to
> > >  > >> get KIPs approved. Tomorrow morning (CEST timezone) I'll send
> > >  another
> > >  > email
> > >  > >> asking developers to assign future approved KIPs to another
> > > version
> > >  > that is
> > >  > >> not 3.8.
> > >  > >>
> > >  > >> So, the only problem I see with KIP-1028 is that it hasn't
> been
> > >  open for
> 

Re: [DISCUSS] Apache Kafka 3.8.0 release

[Josep Prat]

Hi Calvin,

Thanks for the update.
Then it makes sense to not delay the 3.8.0 release and check case by case
which commits if the mentioned KIPs should be cherry picked to the branch.

This means the dates stay. Today EoD is the deadline for feature freeze.
I'll cut the new branch before Friday EoD.


Thanks all and sorry for the noise!

--
Josep Prat
Open Source Engineering Director, aivenjosep.p...@aiven.io   |
+491715557497 | aiven.io
Aiven Deutschland GmbH
Alexanderufer 3-7, 10117 Berlin
Geschäftsführer: Oskari Saarenmaa & Hannu Valtonen
Amtsgericht Charlottenburg, HRB 209739 B

On Wed, May 29, 2024, 18:05 Calvin Liu  wrote:

> Hi
> Regarding the KIP-966, the implementation is split into 2 parts.
> Part 1 where we introduce the Eligible Leader Replicas to help increase the
> data durability is pretty close to finish. We have 1 feature PR pending.
> Currently, Colin McCabe is helping the review and hopefully we can get it
> merged within a week.
> Part 2 where we introduce the unclean recovery, an improvement for the
> unclean leader election has not started yet. It is surely postponed to
> later releases.
> Thanks.
>
> On Wed, May 29, 2024 at 8:48 AM Sebastien Viale <
> sebastien.vi...@michelin.com> wrote:
>
> >
> > Hi,
> > Regarding KIP-1033, we are not opposed to a slight delay. One of the
> > related PRs was merged today.
> > If possible, we would like to proceed in the same manner as with KIP-853
> > and KIP-966.
> > regards,
> >
> > De : Josep Prat 
> > Envoyé : mercredi 29 mai 2024 16:51
> > À : dev@kafka.apache.org 
> > Objet : [EXT] Re: [DISCUSS] Apache Kafka 3.8.0 release
> >
> > Warning External sender Do not click on any links or open any attachments
> > unless you trust the sender and know the content is safe.
> >
> > Hi Ismael,
> >
> > I think your proposal makes more sense than mine. The end goal is to try
> to
> > get these 2 KIPs in 3.8.0 if possible. I think we can also achieve this
> by
> > not delaying the general feature freeze, but rather by cherry picking the
> > future commits on these features to the 3.8 branch.
> >
> > So I would propose to leave the deadlines as they are and manually cherry
> > pick the commits related to KIP-853 and KIP-966.
> >
> > Best,
> >
> > This email was screened for spam and malicious content but exercise
> > caution anyway.
> >
> >
> >
> > On Wed, May 29, 2024 at 3:48 PM Ismael Juma  wrote:
> >
> > > Hi Josep,
> > >
> > > It's generally a bad idea to push these dates because the scope keeps
> > > increasing then. If there are features that need more time and we
> believe
> > > they are essential for 3.8 due to its special nature as the last
> release
> > > before 4.0, we should allow them to be cherry-picked to the release
> > branch
> > > versus delaying the feature freeze and code freeze for everything.
> > >
> > > Ismael
> > >
> > > On Wed, May 29, 2024 at 2:38 AM Josep Prat  >
> > > wrote:
> > >
> > > > Hi Kafka developers,
> > > >
> > > > Given the fact we have a couple of KIPs that are halfway through
> their
> > > > implementation and it seems it's a matter of days (1 or 2 weeks) to
> > have
> > > > them completed. What would you think if we delay feature freeze and
> > code
> > > > freeze by 2 weeks? Let me know your thoughts.
> > > >
> > > > Best,
> > > >
> > > > On Tue, May 28, 2024 at 8:47 AM Josep Prat 
> > wrote:
> > > >
> > > > > Hi Kafka developers,
> > > > >
> > > > > This is a reminder about the upcoming deadlines:
> > > > > - Feature freeze is on May 29th
> > > > > - Code freeze is June 12th
> > > > >
> > > > > I'll cut the new branch during morning hours (CEST) on May 30th.
> > > > >
> > > > > Thanks all!
> > > > >
> > > > > On Thu, May 16, 2024 at 8:34 AM Josep Prat 
> > > wrote:
> > > > >
> > > > >> Hi all,
> > > > >>
> > > > >> We are now officially past the KIP freeze deadline. KIPs that are
> > > > >> approved after this point in time shouldn't be adopted in the
> 3.8.x
> > > > release
> > > > >> (except the 2 already mentioned KIPS 989 and 1028 assuming no
> vetoes
> > > > occur).
> > > > >>
> >

Re: [DISCUSS] Apache Kafka 3.8.0 release

[Calvin Liu]

Hi
Regarding the KIP-966, the implementation is split into 2 parts.
Part 1 where we introduce the Eligible Leader Replicas to help increase the
data durability is pretty close to finish. We have 1 feature PR pending.
Currently, Colin McCabe is helping the review and hopefully we can get it
merged within a week.
Part 2 where we introduce the unclean recovery, an improvement for the
unclean leader election has not started yet. It is surely postponed to
later releases.
Thanks.

On Wed, May 29, 2024 at 8:48 AM Sebastien Viale <
sebastien.vi...@michelin.com> wrote:

>
> Hi,
> Regarding KIP-1033, we are not opposed to a slight delay. One of the
> related PRs was merged today.
> If possible, we would like to proceed in the same manner as with KIP-853
> and KIP-966.
> regards,
>
> De : Josep Prat 
> Envoyé : mercredi 29 mai 2024 16:51
> À : dev@kafka.apache.org 
> Objet : [EXT] Re: [DISCUSS] Apache Kafka 3.8.0 release
>
> Warning External sender Do not click on any links or open any attachments
> unless you trust the sender and know the content is safe.
>
> Hi Ismael,
>
> I think your proposal makes more sense than mine. The end goal is to try to
> get these 2 KIPs in 3.8.0 if possible. I think we can also achieve this by
> not delaying the general feature freeze, but rather by cherry picking the
> future commits on these features to the 3.8 branch.
>
> So I would propose to leave the deadlines as they are and manually cherry
> pick the commits related to KIP-853 and KIP-966.
>
> Best,
>
> This email was screened for spam and malicious content but exercise
> caution anyway.
>
>
>
> On Wed, May 29, 2024 at 3:48 PM Ismael Juma  wrote:
>
> > Hi Josep,
> >
> > It's generally a bad idea to push these dates because the scope keeps
> > increasing then. If there are features that need more time and we believe
> > they are essential for 3.8 due to its special nature as the last release
> > before 4.0, we should allow them to be cherry-picked to the release
> branch
> > versus delaying the feature freeze and code freeze for everything.
> >
> > Ismael
> >
> > On Wed, May 29, 2024 at 2:38 AM Josep Prat 
> > wrote:
> >
> > > Hi Kafka developers,
> > >
> > > Given the fact we have a couple of KIPs that are halfway through their
> > > implementation and it seems it's a matter of days (1 or 2 weeks) to
> have
> > > them completed. What would you think if we delay feature freeze and
> code
> > > freeze by 2 weeks? Let me know your thoughts.
> > >
> > > Best,
> > >
> > > On Tue, May 28, 2024 at 8:47 AM Josep Prat 
> wrote:
> > >
> > > > Hi Kafka developers,
> > > >
> > > > This is a reminder about the upcoming deadlines:
> > > > - Feature freeze is on May 29th
> > > > - Code freeze is June 12th
> > > >
> > > > I'll cut the new branch during morning hours (CEST) on May 30th.
> > > >
> > > > Thanks all!
> > > >
> > > > On Thu, May 16, 2024 at 8:34 AM Josep Prat 
> > wrote:
> > > >
> > > >> Hi all,
> > > >>
> > > >> We are now officially past the KIP freeze deadline. KIPs that are
> > > >> approved after this point in time shouldn't be adopted in the 3.8.x
> > > release
> > > >> (except the 2 already mentioned KIPS 989 and 1028 assuming no vetoes
> > > occur).
> > > >>
> > > >> Reminder of the upcoming deadlines:
> > > >> - Feature freeze is on May 29th
> > > >> - Code freeze is June 12th
> > > >>
> > > >> If you have an approved KIP that you know already you won't be able
> to
> > > >> complete before the feature freeze deadline, please update the
> Release
> > > >> column in the
> > > >>
> > >
> >
> https://cwiki.apache.org/confluence/display/KAFKA/Kafka+Improvement+Proposals
> <
> https://cwiki.apache.org/confluence/display/KAFKA/Kafka+Improvement+Proposals
> >
> > > >> page.
> > > >>
> > > >> Thanks all,
> > > >>
> > > >> On Wed, May 15, 2024 at 8:53 PM Josep Prat 
> > wrote:
> > > >>
> > > >>> Hi Nick,
> > > >>>
> > > >>> If nobody comes up with concerns or pushback until the time of
> > closing
> > > >>> the vote, I think we can take it for 3.8.
> > > >>>
> > > >>> Best,
> > > >>&

Re: [DISCUSS] Apache Kafka 3.8.0 release

[Sebastien Viale]

Hi,
Regarding KIP-1033, we are not opposed to a slight delay. One of the related 
PRs was merged today.
If possible, we would like to proceed in the same manner as with KIP-853 and 
KIP-966.
regards,

De : Josep Prat 
Envoyé : mercredi 29 mai 2024 16:51
À : dev@kafka.apache.org 
Objet : [EXT] Re: [DISCUSS] Apache Kafka 3.8.0 release

Warning External sender Do not click on any links or open any attachments 
unless you trust the sender and know the content is safe.

Hi Ismael,

I think your proposal makes more sense than mine. The end goal is to try to
get these 2 KIPs in 3.8.0 if possible. I think we can also achieve this by
not delaying the general feature freeze, but rather by cherry picking the
future commits on these features to the 3.8 branch.

So I would propose to leave the deadlines as they are and manually cherry
pick the commits related to KIP-853 and KIP-966.

Best,

This email was screened for spam and malicious content but exercise caution 
anyway.



On Wed, May 29, 2024 at 3:48 PM Ismael Juma  wrote:

> Hi Josep,
>
> It's generally a bad idea to push these dates because the scope keeps
> increasing then. If there are features that need more time and we believe
> they are essential for 3.8 due to its special nature as the last release
> before 4.0, we should allow them to be cherry-picked to the release branch
> versus delaying the feature freeze and code freeze for everything.
>
> Ismael
>
> On Wed, May 29, 2024 at 2:38 AM Josep Prat 
> wrote:
>
> > Hi Kafka developers,
> >
> > Given the fact we have a couple of KIPs that are halfway through their
> > implementation and it seems it's a matter of days (1 or 2 weeks) to have
> > them completed. What would you think if we delay feature freeze and code
> > freeze by 2 weeks? Let me know your thoughts.
> >
> > Best,
> >
> > On Tue, May 28, 2024 at 8:47 AM Josep Prat  wrote:
> >
> > > Hi Kafka developers,
> > >
> > > This is a reminder about the upcoming deadlines:
> > > - Feature freeze is on May 29th
> > > - Code freeze is June 12th
> > >
> > > I'll cut the new branch during morning hours (CEST) on May 30th.
> > >
> > > Thanks all!
> > >
> > > On Thu, May 16, 2024 at 8:34 AM Josep Prat 
> wrote:
> > >
> > >> Hi all,
> > >>
> > >> We are now officially past the KIP freeze deadline. KIPs that are
> > >> approved after this point in time shouldn't be adopted in the 3.8.x
> > release
> > >> (except the 2 already mentioned KIPS 989 and 1028 assuming no vetoes
> > occur).
> > >>
> > >> Reminder of the upcoming deadlines:
> > >> - Feature freeze is on May 29th
> > >> - Code freeze is June 12th
> > >>
> > >> If you have an approved KIP that you know already you won't be able to
> > >> complete before the feature freeze deadline, please update the Release
> > >> column in the
> > >>
> >
> https://cwiki.apache.org/confluence/display/KAFKA/Kafka+Improvement+Proposals<https://cwiki.apache.org/confluence/display/KAFKA/Kafka+Improvement+Proposals>
> > >> page.
> > >>
> > >> Thanks all,
> > >>
> > >> On Wed, May 15, 2024 at 8:53 PM Josep Prat 
> wrote:
> > >>
> > >>> Hi Nick,
> > >>>
> > >>> If nobody comes up with concerns or pushback until the time of
> closing
> > >>> the vote, I think we can take it for 3.8.
> > >>>
> > >>> Best,
> > >>>
> > >>> -
> > >>>
> > >>> Josep Prat
> > >>> Open Source Engineering Director, aivenjosep.p...@aiven.io |
> > >>> +491715557497 | aiven.io
> > >>> Aiven Deutschland GmbH
> > >>> Alexanderufer 3-7, 10117 Berlin
> > >>> Geschäftsführer: Oskari Saarenmaa & Hannu Valtonen
> > >>> Amtsgericht Charlottenburg, HRB 209739 B
> > >>>
> > >>> On Wed, May 15, 2024, 20:48 Nick Telford 
> > wrote:
> > >>>
> > >>>> Hi Josep,
> > >>>>
> > >>>> Would it be possible to sneak KIP-989 into 3.8? Just as with 1028,
> > it's
> > >>>> currently being voted on and has already received the requisite
> votes.
> > >>>> The
> > >>>> only thing holding it back is the 72 hour voting window.
> > >>>>
> > >>>> Vote thread here:
> > >>>> https://lists.apache.org/thread/nhr65h4784z49jbsyt5nx8ys81q90k6s&

Re: [DISCUSS] Apache Kafka 3.8.0 release

[Josep Prat]

Hi Ismael,

I think your proposal makes more sense than mine. The end goal is to try to
get these 2 KIPs in 3.8.0 if possible. I think we can also achieve this by
not delaying the general feature freeze, but rather by cherry picking the
future commits on these features to the 3.8 branch.

So I would propose to leave the deadlines as they are and manually cherry
pick the commits related to KIP-853 and KIP-966.

Best,

On Wed, May 29, 2024 at 3:48 PM Ismael Juma  wrote:

> Hi Josep,
>
> It's generally a bad idea to push these dates because the scope keeps
> increasing then. If there are features that need more time and we believe
> they are essential for 3.8 due to its special nature as the last release
> before 4.0, we should allow them to be cherry-picked to the release branch
> versus delaying the feature freeze and code freeze for everything.
>
> Ismael
>
> On Wed, May 29, 2024 at 2:38 AM Josep Prat 
> wrote:
>
> > Hi Kafka developers,
> >
> > Given the fact we have a couple of KIPs that are halfway through their
> > implementation and it seems it's a matter of days (1 or 2 weeks) to have
> > them completed. What would you think if we delay feature freeze and code
> > freeze by 2 weeks? Let me know your thoughts.
> >
> > Best,
> >
> > On Tue, May 28, 2024 at 8:47 AM Josep Prat  wrote:
> >
> > > Hi Kafka developers,
> > >
> > > This is a reminder about the upcoming deadlines:
> > > - Feature freeze is on May 29th
> > > - Code freeze is June 12th
> > >
> > > I'll cut the new branch during morning hours (CEST) on May 30th.
> > >
> > > Thanks all!
> > >
> > > On Thu, May 16, 2024 at 8:34 AM Josep Prat 
> wrote:
> > >
> > >> Hi all,
> > >>
> > >> We are now officially past the KIP freeze deadline. KIPs that are
> > >> approved after this point in time shouldn't be adopted in the 3.8.x
> > release
> > >> (except the 2 already mentioned KIPS 989 and 1028 assuming no vetoes
> > occur).
> > >>
> > >> Reminder of the upcoming deadlines:
> > >> - Feature freeze is on May 29th
> > >> - Code freeze is June 12th
> > >>
> > >> If you have an approved KIP that you know already you won't be able to
> > >> complete before the feature freeze deadline, please update the Release
> > >> column in the
> > >>
> >
> https://cwiki.apache.org/confluence/display/KAFKA/Kafka+Improvement+Proposals
> > >> page.
> > >>
> > >> Thanks all,
> > >>
> > >> On Wed, May 15, 2024 at 8:53 PM Josep Prat 
> wrote:
> > >>
> > >>> Hi Nick,
> > >>>
> > >>> If nobody comes up with concerns or pushback until the time of
> closing
> > >>> the vote, I think we can take it for 3.8.
> > >>>
> > >>> Best,
> > >>>
> > >>> -
> > >>>
> > >>> Josep Prat
> > >>> Open Source Engineering Director, aivenjosep.p...@aiven.io   |
> > >>> +491715557497 | aiven.io
> > >>> Aiven Deutschland GmbH
> > >>> Alexanderufer 3-7, 10117 Berlin
> > >>> Geschäftsführer: Oskari Saarenmaa & Hannu Valtonen
> > >>> Amtsgericht Charlottenburg, HRB 209739 B
> > >>>
> > >>> On Wed, May 15, 2024, 20:48 Nick Telford 
> > wrote:
> > >>>
> >  Hi Josep,
> > 
> >  Would it be possible to sneak KIP-989 into 3.8? Just as with 1028,
> > it's
> >  currently being voted on and has already received the requisite
> votes.
> >  The
> >  only thing holding it back is the 72 hour voting window.
> > 
> >  Vote thread here:
> >  https://lists.apache.org/thread/nhr65h4784z49jbsyt5nx8ys81q90k6s
> > 
> >  Regards,
> > 
> >  Nick
> > 
> >  On Wed, 15 May 2024 at 17:47, Josep Prat
>  > >
> >  wrote:
> > 
> >  > And my maths are wrong! I added 24 hours more to all the numbers
> in
> >  there.
> >  > If after 72 hours no vetoes appear, I have no objections on adding
> >  this
> >  > specific KIP as it shouldn't have a big blast radius of
> affectation.
> >  >
> >  > Best,
> >  >
> >  > On Wed, May 15, 2024 at 6:44 PM Josep Prat 
> >  wrote:
> >  >
> >  > > Ah, I see Chris was faster writing this than me.
> >  > >
> >  > > On Wed, May 15, 2024 at 6:43 PM Josep Prat  >
> >  wrote:
> >  > >
> >  > >> Hi all,
> >  > >> You still have the full day of today (independently for the
> >  timezone) to
> >  > >> get KIPs approved. Tomorrow morning (CEST timezone) I'll send
> >  another
> >  > email
> >  > >> asking developers to assign future approved KIPs to another
> > version
> >  > that is
> >  > >> not 3.8.
> >  > >>
> >  > >> So, the only problem I see with KIP-1028 is that it hasn't been
> >  open for
> >  > >> a vote for 72 hours (48 hours as of now). If there is no
> negative
> >  > voting on
> >  > >> the KIP I think we can let that one in, given it would only
> miss
> >  the
> >  > >> deadline by less than 12 hours (if my timezone maths add up).
> >  > >>
> >  > >> Best,
> >  > >>
> >  > >> On Wed, May 15, 2024 at 6:35 PM Ismael Juma  >
> >  wrote:
> >  > >>
> >  > >>> 

Re: [DISCUSS] Apache Kafka 3.8.0 release

[Ismael Juma]

Hi Josep,

It's generally a bad idea to push these dates because the scope keeps
increasing then. If there are features that need more time and we believe
they are essential for 3.8 due to its special nature as the last release
before 4.0, we should allow them to be cherry-picked to the release branch
versus delaying the feature freeze and code freeze for everything.

Ismael

On Wed, May 29, 2024 at 2:38 AM Josep Prat 
wrote:

> Hi Kafka developers,
>
> Given the fact we have a couple of KIPs that are halfway through their
> implementation and it seems it's a matter of days (1 or 2 weeks) to have
> them completed. What would you think if we delay feature freeze and code
> freeze by 2 weeks? Let me know your thoughts.
>
> Best,
>
> On Tue, May 28, 2024 at 8:47 AM Josep Prat  wrote:
>
> > Hi Kafka developers,
> >
> > This is a reminder about the upcoming deadlines:
> > - Feature freeze is on May 29th
> > - Code freeze is June 12th
> >
> > I'll cut the new branch during morning hours (CEST) on May 30th.
> >
> > Thanks all!
> >
> > On Thu, May 16, 2024 at 8:34 AM Josep Prat  wrote:
> >
> >> Hi all,
> >>
> >> We are now officially past the KIP freeze deadline. KIPs that are
> >> approved after this point in time shouldn't be adopted in the 3.8.x
> release
> >> (except the 2 already mentioned KIPS 989 and 1028 assuming no vetoes
> occur).
> >>
> >> Reminder of the upcoming deadlines:
> >> - Feature freeze is on May 29th
> >> - Code freeze is June 12th
> >>
> >> If you have an approved KIP that you know already you won't be able to
> >> complete before the feature freeze deadline, please update the Release
> >> column in the
> >>
> https://cwiki.apache.org/confluence/display/KAFKA/Kafka+Improvement+Proposals
> >> page.
> >>
> >> Thanks all,
> >>
> >> On Wed, May 15, 2024 at 8:53 PM Josep Prat  wrote:
> >>
> >>> Hi Nick,
> >>>
> >>> If nobody comes up with concerns or pushback until the time of closing
> >>> the vote, I think we can take it for 3.8.
> >>>
> >>> Best,
> >>>
> >>> -
> >>>
> >>> Josep Prat
> >>> Open Source Engineering Director, aivenjosep.p...@aiven.io   |
> >>> +491715557497 | aiven.io
> >>> Aiven Deutschland GmbH
> >>> Alexanderufer 3-7, 10117 Berlin
> >>> Geschäftsführer: Oskari Saarenmaa & Hannu Valtonen
> >>> Amtsgericht Charlottenburg, HRB 209739 B
> >>>
> >>> On Wed, May 15, 2024, 20:48 Nick Telford 
> wrote:
> >>>
>  Hi Josep,
> 
>  Would it be possible to sneak KIP-989 into 3.8? Just as with 1028,
> it's
>  currently being voted on and has already received the requisite votes.
>  The
>  only thing holding it back is the 72 hour voting window.
> 
>  Vote thread here:
>  https://lists.apache.org/thread/nhr65h4784z49jbsyt5nx8ys81q90k6s
> 
>  Regards,
> 
>  Nick
> 
>  On Wed, 15 May 2024 at 17:47, Josep Prat  >
>  wrote:
> 
>  > And my maths are wrong! I added 24 hours more to all the numbers in
>  there.
>  > If after 72 hours no vetoes appear, I have no objections on adding
>  this
>  > specific KIP as it shouldn't have a big blast radius of affectation.
>  >
>  > Best,
>  >
>  > On Wed, May 15, 2024 at 6:44 PM Josep Prat 
>  wrote:
>  >
>  > > Ah, I see Chris was faster writing this than me.
>  > >
>  > > On Wed, May 15, 2024 at 6:43 PM Josep Prat 
>  wrote:
>  > >
>  > >> Hi all,
>  > >> You still have the full day of today (independently for the
>  timezone) to
>  > >> get KIPs approved. Tomorrow morning (CEST timezone) I'll send
>  another
>  > email
>  > >> asking developers to assign future approved KIPs to another
> version
>  > that is
>  > >> not 3.8.
>  > >>
>  > >> So, the only problem I see with KIP-1028 is that it hasn't been
>  open for
>  > >> a vote for 72 hours (48 hours as of now). If there is no negative
>  > voting on
>  > >> the KIP I think we can let that one in, given it would only miss
>  the
>  > >> deadline by less than 12 hours (if my timezone maths add up).
>  > >>
>  > >> Best,
>  > >>
>  > >> On Wed, May 15, 2024 at 6:35 PM Ismael Juma 
>  wrote:
>  > >>
>  > >>> The KIP freeze is just about having the KIP accepted. Not sure
>  why we
>  > >>> would
>  > >>> need an exception for that.
>  > >>>
>  > >>> Ismael
>  > >>>
>  > >>> On Wed, May 15, 2024 at 9:20 AM Chris Egerton <
>  fearthecel...@gmail.com
>  > >
>  > >>> wrote:
>  > >>>
>  > >>> > FWIW I think that the low blast radius for KIP-1028 should
>  allow it
>  > to
>  > >>> > proceed without adhering to the usual KIP and feature freeze
>  dates.
>  > >>> Code
>  > >>> > freeze is probably worth still  respecting, at least if
> changes
>  are
>  > >>> > required to the docker/jvm/Dockerfile. But I defer to Josep's
>  > >>> judgement as
>  > >>> > the release manager.
>  > >>> >

Re: [DISCUSS] Apache Kafka 3.8.0 release

[Josep Prat]

Hi Mickael,

I'd need some help from @José Armando García Sancio 
and Calvin Liu (explicitly added to the email) to have a better estimation
on how much effort is left.
Regarding KIP-853, it seems a good deal of tasks are assigned and some seem
to be in progress (regardless of what the status says).

Best,

On Wed, May 29, 2024 at 2:35 PM Mickael Maison 
wrote:

> Hi Josep,
>
> The point of the 3.8.0 release was to bridge feature gaps we
> identified between ZooKeeper and KRaft based Kafka clusters.
> In KIP-1012, we had identified 2 features we needed before 4.0:
> KIP-853 and unclean leader elections (KIP-966?).
>
> Can we have a status update on both of these features?
> If we think we can deliver both shortly (or if these are already
> done), I think it makes sense to slightly adjust the dates. Otherwise
> we'll need to either make another release or reconsider our timed
> based release plan.
>
> Thanks,
> Mickael
>
>
>
>
>
> On Wed, May 29, 2024 at 1:33 PM Josep Prat 
> wrote:
> >
> > A correction on the dates as they should be:
> > - Feature freeze is on June 12th (you wrote May before)
> > - code freeze is on June 26th
> >
> > So these are the new proposed deadlines.
> >
> > Best,
> >
> > On Wed, May 29, 2024 at 12:48 PM Luke Chen  wrote:
> >
> > > Hi Josep,
> > >
> > > Thanks for raising this.
> > > I'm +1 for delaying some time to have features completed.
> > >
> > > But I think we might need to make it clear, what's the updated feature
> > > freeze date/code freeze date?
> > > Is this correct?
> > > - Feature freeze is on May 12th
> > > - Code freeze is June 26th
> > >
> > >
> > > Thanks.
> > > Luke
> > >
> > > On Wed, May 29, 2024 at 5:38 PM Josep Prat  >
> > > wrote:
> > >
> > > > Hi Kafka developers,
> > > >
> > > > Given the fact we have a couple of KIPs that are halfway through
> their
> > > > implementation and it seems it's a matter of days (1 or 2 weeks) to
> have
> > > > them completed. What would you think if we delay feature freeze and
> code
> > > > freeze by 2 weeks? Let me know your thoughts.
> > > >
> > > > Best,
> > > >
> > > > On Tue, May 28, 2024 at 8:47 AM Josep Prat 
> wrote:
> > > >
> > > > > Hi Kafka developers,
> > > > >
> > > > > This is a reminder about the upcoming deadlines:
> > > > > - Feature freeze is on May 29th
> > > > > - Code freeze is June 12th
> > > > >
> > > > > I'll cut the new branch during morning hours (CEST) on May 30th.
> > > > >
> > > > > Thanks all!
> > > > >
> > > > > On Thu, May 16, 2024 at 8:34 AM Josep Prat 
> > > wrote:
> > > > >
> > > > >> Hi all,
> > > > >>
> > > > >> We are now officially past the KIP freeze deadline. KIPs that are
> > > > >> approved after this point in time shouldn't be adopted in the
> 3.8.x
> > > > release
> > > > >> (except the 2 already mentioned KIPS 989 and 1028 assuming no
> vetoes
> > > > occur).
> > > > >>
> > > > >> Reminder of the upcoming deadlines:
> > > > >> - Feature freeze is on May 29th
> > > > >> - Code freeze is June 12th
> > > > >>
> > > > >> If you have an approved KIP that you know already you won't be
> able to
> > > > >> complete before the feature freeze deadline, please update the
> Release
> > > > >> column in the
> > > > >>
> > > >
> > >
> https://cwiki.apache.org/confluence/display/KAFKA/Kafka+Improvement+Proposals
> > > > >> page.
> > > > >>
> > > > >> Thanks all,
> > > > >>
> > > > >> On Wed, May 15, 2024 at 8:53 PM Josep Prat 
> > > wrote:
> > > > >>
> > > > >>> Hi Nick,
> > > > >>>
> > > > >>> If nobody comes up with concerns or pushback until the time of
> > > closing
> > > > >>> the vote, I think we can take it for 3.8.
> > > > >>>
> > > > >>> Best,
> > > > >>>
> > > > >>> -
> > > > >>>
> > > > >>> Josep Prat
> > > > >>> Open Source Engineering Director, aivenjosep.p...@aiven.io   |
> > > > >>> +491715557497 | aiven.io
> > > > >>> Aiven Deutschland GmbH
> > > > >>> Alexanderufer 3-7, 10117 Berlin
> > > > >>> Geschäftsführer: Oskari Saarenmaa & Hannu Valtonen
> > > > >>> Amtsgericht Charlottenburg, HRB 209739 B
> > > > >>>
> > > > >>> On Wed, May 15, 2024, 20:48 Nick Telford  >
> > > > wrote:
> > > > >>>
> > > >  Hi Josep,
> > > > 
> > > >  Would it be possible to sneak KIP-989 into 3.8? Just as with
> 1028,
> > > > it's
> > > >  currently being voted on and has already received the requisite
> > > votes.
> > > >  The
> > > >  only thing holding it back is the 72 hour voting window.
> > > > 
> > > >  Vote thread here:
> > > > 
> https://lists.apache.org/thread/nhr65h4784z49jbsyt5nx8ys81q90k6s
> > > > 
> > > >  Regards,
> > > > 
> > > >  Nick
> > > > 
> > > >  On Wed, 15 May 2024 at 17:47, Josep Prat
> > >  > > > >
> > > >  wrote:
> > > > 
> > > >  > And my maths are wrong! I added 24 hours more to all the
> numbers
> > > in
> > > >  there.
> > > >  > If after 72 hours no vetoes appear, I have no objections on
> adding
> > > >  this
> > > >  > specific KIP as it shouldn't have a big blast 

Re: [DISCUSS] Apache Kafka 3.8.0 release

[Mickael Maison]

Hi Josep,

The point of the 3.8.0 release was to bridge feature gaps we
identified between ZooKeeper and KRaft based Kafka clusters.
In KIP-1012, we had identified 2 features we needed before 4.0:
KIP-853 and unclean leader elections (KIP-966?).

Can we have a status update on both of these features?
If we think we can deliver both shortly (or if these are already
done), I think it makes sense to slightly adjust the dates. Otherwise
we'll need to either make another release or reconsider our timed
based release plan.

Thanks,
Mickael





On Wed, May 29, 2024 at 1:33 PM Josep Prat  wrote:
>
> A correction on the dates as they should be:
> - Feature freeze is on June 12th (you wrote May before)
> - code freeze is on June 26th
>
> So these are the new proposed deadlines.
>
> Best,
>
> On Wed, May 29, 2024 at 12:48 PM Luke Chen  wrote:
>
> > Hi Josep,
> >
> > Thanks for raising this.
> > I'm +1 for delaying some time to have features completed.
> >
> > But I think we might need to make it clear, what's the updated feature
> > freeze date/code freeze date?
> > Is this correct?
> > - Feature freeze is on May 12th
> > - Code freeze is June 26th
> >
> >
> > Thanks.
> > Luke
> >
> > On Wed, May 29, 2024 at 5:38 PM Josep Prat 
> > wrote:
> >
> > > Hi Kafka developers,
> > >
> > > Given the fact we have a couple of KIPs that are halfway through their
> > > implementation and it seems it's a matter of days (1 or 2 weeks) to have
> > > them completed. What would you think if we delay feature freeze and code
> > > freeze by 2 weeks? Let me know your thoughts.
> > >
> > > Best,
> > >
> > > On Tue, May 28, 2024 at 8:47 AM Josep Prat  wrote:
> > >
> > > > Hi Kafka developers,
> > > >
> > > > This is a reminder about the upcoming deadlines:
> > > > - Feature freeze is on May 29th
> > > > - Code freeze is June 12th
> > > >
> > > > I'll cut the new branch during morning hours (CEST) on May 30th.
> > > >
> > > > Thanks all!
> > > >
> > > > On Thu, May 16, 2024 at 8:34 AM Josep Prat 
> > wrote:
> > > >
> > > >> Hi all,
> > > >>
> > > >> We are now officially past the KIP freeze deadline. KIPs that are
> > > >> approved after this point in time shouldn't be adopted in the 3.8.x
> > > release
> > > >> (except the 2 already mentioned KIPS 989 and 1028 assuming no vetoes
> > > occur).
> > > >>
> > > >> Reminder of the upcoming deadlines:
> > > >> - Feature freeze is on May 29th
> > > >> - Code freeze is June 12th
> > > >>
> > > >> If you have an approved KIP that you know already you won't be able to
> > > >> complete before the feature freeze deadline, please update the Release
> > > >> column in the
> > > >>
> > >
> > https://cwiki.apache.org/confluence/display/KAFKA/Kafka+Improvement+Proposals
> > > >> page.
> > > >>
> > > >> Thanks all,
> > > >>
> > > >> On Wed, May 15, 2024 at 8:53 PM Josep Prat 
> > wrote:
> > > >>
> > > >>> Hi Nick,
> > > >>>
> > > >>> If nobody comes up with concerns or pushback until the time of
> > closing
> > > >>> the vote, I think we can take it for 3.8.
> > > >>>
> > > >>> Best,
> > > >>>
> > > >>> -
> > > >>>
> > > >>> Josep Prat
> > > >>> Open Source Engineering Director, aivenjosep.p...@aiven.io   |
> > > >>> +491715557497 | aiven.io
> > > >>> Aiven Deutschland GmbH
> > > >>> Alexanderufer 3-7, 10117 Berlin
> > > >>> Geschäftsführer: Oskari Saarenmaa & Hannu Valtonen
> > > >>> Amtsgericht Charlottenburg, HRB 209739 B
> > > >>>
> > > >>> On Wed, May 15, 2024, 20:48 Nick Telford 
> > > wrote:
> > > >>>
> > >  Hi Josep,
> > > 
> > >  Would it be possible to sneak KIP-989 into 3.8? Just as with 1028,
> > > it's
> > >  currently being voted on and has already received the requisite
> > votes.
> > >  The
> > >  only thing holding it back is the 72 hour voting window.
> > > 
> > >  Vote thread here:
> > >  https://lists.apache.org/thread/nhr65h4784z49jbsyt5nx8ys81q90k6s
> > > 
> > >  Regards,
> > > 
> > >  Nick
> > > 
> > >  On Wed, 15 May 2024 at 17:47, Josep Prat
> >  > > >
> > >  wrote:
> > > 
> > >  > And my maths are wrong! I added 24 hours more to all the numbers
> > in
> > >  there.
> > >  > If after 72 hours no vetoes appear, I have no objections on adding
> > >  this
> > >  > specific KIP as it shouldn't have a big blast radius of
> > affectation.
> > >  >
> > >  > Best,
> > >  >
> > >  > On Wed, May 15, 2024 at 6:44 PM Josep Prat 
> > >  wrote:
> > >  >
> > >  > > Ah, I see Chris was faster writing this than me.
> > >  > >
> > >  > > On Wed, May 15, 2024 at 6:43 PM Josep Prat  > >
> > >  wrote:
> > >  > >
> > >  > >> Hi all,
> > >  > >> You still have the full day of today (independently for the
> > >  timezone) to
> > >  > >> get KIPs approved. Tomorrow morning (CEST timezone) I'll send
> > >  another
> > >  > email
> > >  > >> asking developers to assign future approved KIPs to another
> > > version
> > >  > that 

Re: [DISCUSS] Apache Kafka 3.8.0 release

[Josep Prat]

A correction on the dates as they should be:
- Feature freeze is on June 12th (you wrote May before)
- code freeze is on June 26th

So these are the new proposed deadlines.

Best,

On Wed, May 29, 2024 at 12:48 PM Luke Chen  wrote:

> Hi Josep,
>
> Thanks for raising this.
> I'm +1 for delaying some time to have features completed.
>
> But I think we might need to make it clear, what's the updated feature
> freeze date/code freeze date?
> Is this correct?
> - Feature freeze is on May 12th
> - Code freeze is June 26th
>
>
> Thanks.
> Luke
>
> On Wed, May 29, 2024 at 5:38 PM Josep Prat 
> wrote:
>
> > Hi Kafka developers,
> >
> > Given the fact we have a couple of KIPs that are halfway through their
> > implementation and it seems it's a matter of days (1 or 2 weeks) to have
> > them completed. What would you think if we delay feature freeze and code
> > freeze by 2 weeks? Let me know your thoughts.
> >
> > Best,
> >
> > On Tue, May 28, 2024 at 8:47 AM Josep Prat  wrote:
> >
> > > Hi Kafka developers,
> > >
> > > This is a reminder about the upcoming deadlines:
> > > - Feature freeze is on May 29th
> > > - Code freeze is June 12th
> > >
> > > I'll cut the new branch during morning hours (CEST) on May 30th.
> > >
> > > Thanks all!
> > >
> > > On Thu, May 16, 2024 at 8:34 AM Josep Prat 
> wrote:
> > >
> > >> Hi all,
> > >>
> > >> We are now officially past the KIP freeze deadline. KIPs that are
> > >> approved after this point in time shouldn't be adopted in the 3.8.x
> > release
> > >> (except the 2 already mentioned KIPS 989 and 1028 assuming no vetoes
> > occur).
> > >>
> > >> Reminder of the upcoming deadlines:
> > >> - Feature freeze is on May 29th
> > >> - Code freeze is June 12th
> > >>
> > >> If you have an approved KIP that you know already you won't be able to
> > >> complete before the feature freeze deadline, please update the Release
> > >> column in the
> > >>
> >
> https://cwiki.apache.org/confluence/display/KAFKA/Kafka+Improvement+Proposals
> > >> page.
> > >>
> > >> Thanks all,
> > >>
> > >> On Wed, May 15, 2024 at 8:53 PM Josep Prat 
> wrote:
> > >>
> > >>> Hi Nick,
> > >>>
> > >>> If nobody comes up with concerns or pushback until the time of
> closing
> > >>> the vote, I think we can take it for 3.8.
> > >>>
> > >>> Best,
> > >>>
> > >>> -
> > >>>
> > >>> Josep Prat
> > >>> Open Source Engineering Director, aivenjosep.p...@aiven.io   |
> > >>> +491715557497 | aiven.io
> > >>> Aiven Deutschland GmbH
> > >>> Alexanderufer 3-7, 10117 Berlin
> > >>> Geschäftsführer: Oskari Saarenmaa & Hannu Valtonen
> > >>> Amtsgericht Charlottenburg, HRB 209739 B
> > >>>
> > >>> On Wed, May 15, 2024, 20:48 Nick Telford 
> > wrote:
> > >>>
> >  Hi Josep,
> > 
> >  Would it be possible to sneak KIP-989 into 3.8? Just as with 1028,
> > it's
> >  currently being voted on and has already received the requisite
> votes.
> >  The
> >  only thing holding it back is the 72 hour voting window.
> > 
> >  Vote thread here:
> >  https://lists.apache.org/thread/nhr65h4784z49jbsyt5nx8ys81q90k6s
> > 
> >  Regards,
> > 
> >  Nick
> > 
> >  On Wed, 15 May 2024 at 17:47, Josep Prat
>  > >
> >  wrote:
> > 
> >  > And my maths are wrong! I added 24 hours more to all the numbers
> in
> >  there.
> >  > If after 72 hours no vetoes appear, I have no objections on adding
> >  this
> >  > specific KIP as it shouldn't have a big blast radius of
> affectation.
> >  >
> >  > Best,
> >  >
> >  > On Wed, May 15, 2024 at 6:44 PM Josep Prat 
> >  wrote:
> >  >
> >  > > Ah, I see Chris was faster writing this than me.
> >  > >
> >  > > On Wed, May 15, 2024 at 6:43 PM Josep Prat  >
> >  wrote:
> >  > >
> >  > >> Hi all,
> >  > >> You still have the full day of today (independently for the
> >  timezone) to
> >  > >> get KIPs approved. Tomorrow morning (CEST timezone) I'll send
> >  another
> >  > email
> >  > >> asking developers to assign future approved KIPs to another
> > version
> >  > that is
> >  > >> not 3.8.
> >  > >>
> >  > >> So, the only problem I see with KIP-1028 is that it hasn't been
> >  open for
> >  > >> a vote for 72 hours (48 hours as of now). If there is no
> negative
> >  > voting on
> >  > >> the KIP I think we can let that one in, given it would only
> miss
> >  the
> >  > >> deadline by less than 12 hours (if my timezone maths add up).
> >  > >>
> >  > >> Best,
> >  > >>
> >  > >> On Wed, May 15, 2024 at 6:35 PM Ismael Juma  >
> >  wrote:
> >  > >>
> >  > >>> The KIP freeze is just about having the KIP accepted. Not sure
> >  why we
> >  > >>> would
> >  > >>> need an exception for that.
> >  > >>>
> >  > >>> Ismael
> >  > >>>
> >  > >>> On Wed, May 15, 2024 at 9:20 AM Chris Egerton <
> >  fearthecel...@gmail.com
> >  > >
> >  > >>> wrote:

Re: [DISCUSS] Apache Kafka 3.8.0 release

[Luke Chen]

Hi Josep,

Thanks for raising this.
I'm +1 for delaying some time to have features completed.

But I think we might need to make it clear, what's the updated feature
freeze date/code freeze date?
Is this correct?
- Feature freeze is on May 12th
- Code freeze is June 26th


Thanks.
Luke

On Wed, May 29, 2024 at 5:38 PM Josep Prat 
wrote:

> Hi Kafka developers,
>
> Given the fact we have a couple of KIPs that are halfway through their
> implementation and it seems it's a matter of days (1 or 2 weeks) to have
> them completed. What would you think if we delay feature freeze and code
> freeze by 2 weeks? Let me know your thoughts.
>
> Best,
>
> On Tue, May 28, 2024 at 8:47 AM Josep Prat  wrote:
>
> > Hi Kafka developers,
> >
> > This is a reminder about the upcoming deadlines:
> > - Feature freeze is on May 29th
> > - Code freeze is June 12th
> >
> > I'll cut the new branch during morning hours (CEST) on May 30th.
> >
> > Thanks all!
> >
> > On Thu, May 16, 2024 at 8:34 AM Josep Prat  wrote:
> >
> >> Hi all,
> >>
> >> We are now officially past the KIP freeze deadline. KIPs that are
> >> approved after this point in time shouldn't be adopted in the 3.8.x
> release
> >> (except the 2 already mentioned KIPS 989 and 1028 assuming no vetoes
> occur).
> >>
> >> Reminder of the upcoming deadlines:
> >> - Feature freeze is on May 29th
> >> - Code freeze is June 12th
> >>
> >> If you have an approved KIP that you know already you won't be able to
> >> complete before the feature freeze deadline, please update the Release
> >> column in the
> >>
> https://cwiki.apache.org/confluence/display/KAFKA/Kafka+Improvement+Proposals
> >> page.
> >>
> >> Thanks all,
> >>
> >> On Wed, May 15, 2024 at 8:53 PM Josep Prat  wrote:
> >>
> >>> Hi Nick,
> >>>
> >>> If nobody comes up with concerns or pushback until the time of closing
> >>> the vote, I think we can take it for 3.8.
> >>>
> >>> Best,
> >>>
> >>> -
> >>>
> >>> Josep Prat
> >>> Open Source Engineering Director, aivenjosep.p...@aiven.io   |
> >>> +491715557497 | aiven.io
> >>> Aiven Deutschland GmbH
> >>> Alexanderufer 3-7, 10117 Berlin
> >>> Geschäftsführer: Oskari Saarenmaa & Hannu Valtonen
> >>> Amtsgericht Charlottenburg, HRB 209739 B
> >>>
> >>> On Wed, May 15, 2024, 20:48 Nick Telford 
> wrote:
> >>>
>  Hi Josep,
> 
>  Would it be possible to sneak KIP-989 into 3.8? Just as with 1028,
> it's
>  currently being voted on and has already received the requisite votes.
>  The
>  only thing holding it back is the 72 hour voting window.
> 
>  Vote thread here:
>  https://lists.apache.org/thread/nhr65h4784z49jbsyt5nx8ys81q90k6s
> 
>  Regards,
> 
>  Nick
> 
>  On Wed, 15 May 2024 at 17:47, Josep Prat  >
>  wrote:
> 
>  > And my maths are wrong! I added 24 hours more to all the numbers in
>  there.
>  > If after 72 hours no vetoes appear, I have no objections on adding
>  this
>  > specific KIP as it shouldn't have a big blast radius of affectation.
>  >
>  > Best,
>  >
>  > On Wed, May 15, 2024 at 6:44 PM Josep Prat 
>  wrote:
>  >
>  > > Ah, I see Chris was faster writing this than me.
>  > >
>  > > On Wed, May 15, 2024 at 6:43 PM Josep Prat 
>  wrote:
>  > >
>  > >> Hi all,
>  > >> You still have the full day of today (independently for the
>  timezone) to
>  > >> get KIPs approved. Tomorrow morning (CEST timezone) I'll send
>  another
>  > email
>  > >> asking developers to assign future approved KIPs to another
> version
>  > that is
>  > >> not 3.8.
>  > >>
>  > >> So, the only problem I see with KIP-1028 is that it hasn't been
>  open for
>  > >> a vote for 72 hours (48 hours as of now). If there is no negative
>  > voting on
>  > >> the KIP I think we can let that one in, given it would only miss
>  the
>  > >> deadline by less than 12 hours (if my timezone maths add up).
>  > >>
>  > >> Best,
>  > >>
>  > >> On Wed, May 15, 2024 at 6:35 PM Ismael Juma 
>  wrote:
>  > >>
>  > >>> The KIP freeze is just about having the KIP accepted. Not sure
>  why we
>  > >>> would
>  > >>> need an exception for that.
>  > >>>
>  > >>> Ismael
>  > >>>
>  > >>> On Wed, May 15, 2024 at 9:20 AM Chris Egerton <
>  fearthecel...@gmail.com
>  > >
>  > >>> wrote:
>  > >>>
>  > >>> > FWIW I think that the low blast radius for KIP-1028 should
>  allow it
>  > to
>  > >>> > proceed without adhering to the usual KIP and feature freeze
>  dates.
>  > >>> Code
>  > >>> > freeze is probably worth still  respecting, at least if
> changes
>  are
>  > >>> > required to the docker/jvm/Dockerfile. But I defer to Josep's
>  > >>> judgement as
>  > >>> > the release manager.
>  > >>> >
>  > >>> > On Wed, May 15, 2024, 06:59 Vedarth Sharma <
>  

Re: [DISCUSS] Apache Kafka 3.8.0 release

[Josep Prat]

Hi Kafka developers,

Given the fact we have a couple of KIPs that are halfway through their
implementation and it seems it's a matter of days (1 or 2 weeks) to have
them completed. What would you think if we delay feature freeze and code
freeze by 2 weeks? Let me know your thoughts.

Best,

On Tue, May 28, 2024 at 8:47 AM Josep Prat  wrote:

> Hi Kafka developers,
>
> This is a reminder about the upcoming deadlines:
> - Feature freeze is on May 29th
> - Code freeze is June 12th
>
> I'll cut the new branch during morning hours (CEST) on May 30th.
>
> Thanks all!
>
> On Thu, May 16, 2024 at 8:34 AM Josep Prat  wrote:
>
>> Hi all,
>>
>> We are now officially past the KIP freeze deadline. KIPs that are
>> approved after this point in time shouldn't be adopted in the 3.8.x release
>> (except the 2 already mentioned KIPS 989 and 1028 assuming no vetoes occur).
>>
>> Reminder of the upcoming deadlines:
>> - Feature freeze is on May 29th
>> - Code freeze is June 12th
>>
>> If you have an approved KIP that you know already you won't be able to
>> complete before the feature freeze deadline, please update the Release
>> column in the
>> https://cwiki.apache.org/confluence/display/KAFKA/Kafka+Improvement+Proposals
>> page.
>>
>> Thanks all,
>>
>> On Wed, May 15, 2024 at 8:53 PM Josep Prat  wrote:
>>
>>> Hi Nick,
>>>
>>> If nobody comes up with concerns or pushback until the time of closing
>>> the vote, I think we can take it for 3.8.
>>>
>>> Best,
>>>
>>> -
>>>
>>> Josep Prat
>>> Open Source Engineering Director, aivenjosep.p...@aiven.io   |
>>> +491715557497 | aiven.io
>>> Aiven Deutschland GmbH
>>> Alexanderufer 3-7, 10117 Berlin
>>> Geschäftsführer: Oskari Saarenmaa & Hannu Valtonen
>>> Amtsgericht Charlottenburg, HRB 209739 B
>>>
>>> On Wed, May 15, 2024, 20:48 Nick Telford  wrote:
>>>
 Hi Josep,

 Would it be possible to sneak KIP-989 into 3.8? Just as with 1028, it's
 currently being voted on and has already received the requisite votes.
 The
 only thing holding it back is the 72 hour voting window.

 Vote thread here:
 https://lists.apache.org/thread/nhr65h4784z49jbsyt5nx8ys81q90k6s

 Regards,

 Nick

 On Wed, 15 May 2024 at 17:47, Josep Prat 
 wrote:

 > And my maths are wrong! I added 24 hours more to all the numbers in
 there.
 > If after 72 hours no vetoes appear, I have no objections on adding
 this
 > specific KIP as it shouldn't have a big blast radius of affectation.
 >
 > Best,
 >
 > On Wed, May 15, 2024 at 6:44 PM Josep Prat 
 wrote:
 >
 > > Ah, I see Chris was faster writing this than me.
 > >
 > > On Wed, May 15, 2024 at 6:43 PM Josep Prat 
 wrote:
 > >
 > >> Hi all,
 > >> You still have the full day of today (independently for the
 timezone) to
 > >> get KIPs approved. Tomorrow morning (CEST timezone) I'll send
 another
 > email
 > >> asking developers to assign future approved KIPs to another version
 > that is
 > >> not 3.8.
 > >>
 > >> So, the only problem I see with KIP-1028 is that it hasn't been
 open for
 > >> a vote for 72 hours (48 hours as of now). If there is no negative
 > voting on
 > >> the KIP I think we can let that one in, given it would only miss
 the
 > >> deadline by less than 12 hours (if my timezone maths add up).
 > >>
 > >> Best,
 > >>
 > >> On Wed, May 15, 2024 at 6:35 PM Ismael Juma 
 wrote:
 > >>
 > >>> The KIP freeze is just about having the KIP accepted. Not sure
 why we
 > >>> would
 > >>> need an exception for that.
 > >>>
 > >>> Ismael
 > >>>
 > >>> On Wed, May 15, 2024 at 9:20 AM Chris Egerton <
 fearthecel...@gmail.com
 > >
 > >>> wrote:
 > >>>
 > >>> > FWIW I think that the low blast radius for KIP-1028 should
 allow it
 > to
 > >>> > proceed without adhering to the usual KIP and feature freeze
 dates.
 > >>> Code
 > >>> > freeze is probably worth still  respecting, at least if changes
 are
 > >>> > required to the docker/jvm/Dockerfile. But I defer to Josep's
 > >>> judgement as
 > >>> > the release manager.
 > >>> >
 > >>> > On Wed, May 15, 2024, 06:59 Vedarth Sharma <
 vedarth.sha...@gmail.com
 > >
 > >>> > wrote:
 > >>> >
 > >>> > > Hey Josep!
 > >>> > >
 > >>> > > The KIP 1028 has received the required votes. Voting thread:-
 > >>> > >
 https://lists.apache.org/thread/cdq4wfv5v1gpqlxnf46ycwtcwk5wos4q
 > >>> > > But we are keeping the vote open for 72 hours as per the
 process.
 > >>> > >
 > >>> > > I would like to request you to please consider it for the
 3.8.0
 > >>> release.
 > >>> > >
 > >>> > > Thanks and regards,
 > >>> > > Vedarth
 > >>> > >
 > >>> > >
 > >>> > > On Wed, May 15, 2024 at 1:14 PM Josep Prat
 > >>> 
 > >>> > > 

Re: [DISCUSS] Apache Kafka 3.8.0 release

[Josep Prat]

Hi Kafka developers,

This is a reminder about the upcoming deadlines:
- Feature freeze is on May 29th
- Code freeze is June 12th

I'll cut the new branch during morning hours (CEST) on May 30th.

Thanks all!

On Thu, May 16, 2024 at 8:34 AM Josep Prat  wrote:

> Hi all,
>
> We are now officially past the KIP freeze deadline. KIPs that are approved
> after this point in time shouldn't be adopted in the 3.8.x release (except
> the 2 already mentioned KIPS 989 and 1028 assuming no vetoes occur).
>
> Reminder of the upcoming deadlines:
> - Feature freeze is on May 29th
> - Code freeze is June 12th
>
> If you have an approved KIP that you know already you won't be able to
> complete before the feature freeze deadline, please update the Release
> column in the
> https://cwiki.apache.org/confluence/display/KAFKA/Kafka+Improvement+Proposals
> page.
>
> Thanks all,
>
> On Wed, May 15, 2024 at 8:53 PM Josep Prat  wrote:
>
>> Hi Nick,
>>
>> If nobody comes up with concerns or pushback until the time of closing
>> the vote, I think we can take it for 3.8.
>>
>> Best,
>>
>> -
>>
>> Josep Prat
>> Open Source Engineering Director, aivenjosep.p...@aiven.io   |
>> +491715557497 | aiven.io
>> Aiven Deutschland GmbH
>> Alexanderufer 3-7, 10117 Berlin
>> Geschäftsführer: Oskari Saarenmaa & Hannu Valtonen
>> Amtsgericht Charlottenburg, HRB 209739 B
>>
>> On Wed, May 15, 2024, 20:48 Nick Telford  wrote:
>>
>>> Hi Josep,
>>>
>>> Would it be possible to sneak KIP-989 into 3.8? Just as with 1028, it's
>>> currently being voted on and has already received the requisite votes.
>>> The
>>> only thing holding it back is the 72 hour voting window.
>>>
>>> Vote thread here:
>>> https://lists.apache.org/thread/nhr65h4784z49jbsyt5nx8ys81q90k6s
>>>
>>> Regards,
>>>
>>> Nick
>>>
>>> On Wed, 15 May 2024 at 17:47, Josep Prat 
>>> wrote:
>>>
>>> > And my maths are wrong! I added 24 hours more to all the numbers in
>>> there.
>>> > If after 72 hours no vetoes appear, I have no objections on adding this
>>> > specific KIP as it shouldn't have a big blast radius of affectation.
>>> >
>>> > Best,
>>> >
>>> > On Wed, May 15, 2024 at 6:44 PM Josep Prat 
>>> wrote:
>>> >
>>> > > Ah, I see Chris was faster writing this than me.
>>> > >
>>> > > On Wed, May 15, 2024 at 6:43 PM Josep Prat 
>>> wrote:
>>> > >
>>> > >> Hi all,
>>> > >> You still have the full day of today (independently for the
>>> timezone) to
>>> > >> get KIPs approved. Tomorrow morning (CEST timezone) I'll send
>>> another
>>> > email
>>> > >> asking developers to assign future approved KIPs to another version
>>> > that is
>>> > >> not 3.8.
>>> > >>
>>> > >> So, the only problem I see with KIP-1028 is that it hasn't been
>>> open for
>>> > >> a vote for 72 hours (48 hours as of now). If there is no negative
>>> > voting on
>>> > >> the KIP I think we can let that one in, given it would only miss the
>>> > >> deadline by less than 12 hours (if my timezone maths add up).
>>> > >>
>>> > >> Best,
>>> > >>
>>> > >> On Wed, May 15, 2024 at 6:35 PM Ismael Juma 
>>> wrote:
>>> > >>
>>> > >>> The KIP freeze is just about having the KIP accepted. Not sure why
>>> we
>>> > >>> would
>>> > >>> need an exception for that.
>>> > >>>
>>> > >>> Ismael
>>> > >>>
>>> > >>> On Wed, May 15, 2024 at 9:20 AM Chris Egerton <
>>> fearthecel...@gmail.com
>>> > >
>>> > >>> wrote:
>>> > >>>
>>> > >>> > FWIW I think that the low blast radius for KIP-1028 should allow
>>> it
>>> > to
>>> > >>> > proceed without adhering to the usual KIP and feature freeze
>>> dates.
>>> > >>> Code
>>> > >>> > freeze is probably worth still  respecting, at least if changes
>>> are
>>> > >>> > required to the docker/jvm/Dockerfile. But I defer to Josep's
>>> > >>> judgement as
>>> > >>> > the release manager.
>>> > >>> >
>>> > >>> > On Wed, May 15, 2024, 06:59 Vedarth Sharma <
>>> vedarth.sha...@gmail.com
>>> > >
>>> > >>> > wrote:
>>> > >>> >
>>> > >>> > > Hey Josep!
>>> > >>> > >
>>> > >>> > > The KIP 1028 has received the required votes. Voting thread:-
>>> > >>> > >
>>> https://lists.apache.org/thread/cdq4wfv5v1gpqlxnf46ycwtcwk5wos4q
>>> > >>> > > But we are keeping the vote open for 72 hours as per the
>>> process.
>>> > >>> > >
>>> > >>> > > I would like to request you to please consider it for the 3.8.0
>>> > >>> release.
>>> > >>> > >
>>> > >>> > > Thanks and regards,
>>> > >>> > > Vedarth
>>> > >>> > >
>>> > >>> > >
>>> > >>> > > On Wed, May 15, 2024 at 1:14 PM Josep Prat
>>> > >>> 
>>> > >>> > > wrote:
>>> > >>> > >
>>> > >>> > > > Hi Kafka developers!
>>> > >>> > > >
>>> > >>> > > > Today is the KIP freeze deadline. All KIPs should be
>>> accepted by
>>> > >>> EOD
>>> > >>> > > today.
>>> > >>> > > > Tomorrow morning (CEST timezone) I'll start summarizing all
>>> KIPs
>>> > >>> that
>>> > >>> > > have
>>> > >>> > > > been approved. Please any KIP approved after tomorrow should
>>> be
>>> > >>> adopted
>>> > >>> > > in
>>> > >>> > > > a future release version, not 3.8.
>>> > >>> > > >
>>> > >>> > > > 

Re: [DISCUSS] Apache Kafka 3.8.0 release

[Josep Prat]

Hi all,

We are now officially past the KIP freeze deadline. KIPs that are approved
after this point in time shouldn't be adopted in the 3.8.x release (except
the 2 already mentioned KIPS 989 and 1028 assuming no vetoes occur).

Reminder of the upcoming deadlines:
- Feature freeze is on May 29th
- Code freeze is June 12th

If you have an approved KIP that you know already you won't be able to
complete before the feature freeze deadline, please update the Release
column in the
https://cwiki.apache.org/confluence/display/KAFKA/Kafka+Improvement+Proposals
page.

Thanks all,

On Wed, May 15, 2024 at 8:53 PM Josep Prat  wrote:

> Hi Nick,
>
> If nobody comes up with concerns or pushback until the time of closing the
> vote, I think we can take it for 3.8.
>
> Best,
>
> -
>
> Josep Prat
> Open Source Engineering Director, aivenjosep.p...@aiven.io   |
> +491715557497 | aiven.io
> Aiven Deutschland GmbH
> Alexanderufer 3-7, 10117 Berlin
> Geschäftsführer: Oskari Saarenmaa & Hannu Valtonen
> Amtsgericht Charlottenburg, HRB 209739 B
>
> On Wed, May 15, 2024, 20:48 Nick Telford  wrote:
>
>> Hi Josep,
>>
>> Would it be possible to sneak KIP-989 into 3.8? Just as with 1028, it's
>> currently being voted on and has already received the requisite votes. The
>> only thing holding it back is the 72 hour voting window.
>>
>> Vote thread here:
>> https://lists.apache.org/thread/nhr65h4784z49jbsyt5nx8ys81q90k6s
>>
>> Regards,
>>
>> Nick
>>
>> On Wed, 15 May 2024 at 17:47, Josep Prat 
>> wrote:
>>
>> > And my maths are wrong! I added 24 hours more to all the numbers in
>> there.
>> > If after 72 hours no vetoes appear, I have no objections on adding this
>> > specific KIP as it shouldn't have a big blast radius of affectation.
>> >
>> > Best,
>> >
>> > On Wed, May 15, 2024 at 6:44 PM Josep Prat  wrote:
>> >
>> > > Ah, I see Chris was faster writing this than me.
>> > >
>> > > On Wed, May 15, 2024 at 6:43 PM Josep Prat 
>> wrote:
>> > >
>> > >> Hi all,
>> > >> You still have the full day of today (independently for the
>> timezone) to
>> > >> get KIPs approved. Tomorrow morning (CEST timezone) I'll send another
>> > email
>> > >> asking developers to assign future approved KIPs to another version
>> > that is
>> > >> not 3.8.
>> > >>
>> > >> So, the only problem I see with KIP-1028 is that it hasn't been open
>> for
>> > >> a vote for 72 hours (48 hours as of now). If there is no negative
>> > voting on
>> > >> the KIP I think we can let that one in, given it would only miss the
>> > >> deadline by less than 12 hours (if my timezone maths add up).
>> > >>
>> > >> Best,
>> > >>
>> > >> On Wed, May 15, 2024 at 6:35 PM Ismael Juma 
>> wrote:
>> > >>
>> > >>> The KIP freeze is just about having the KIP accepted. Not sure why
>> we
>> > >>> would
>> > >>> need an exception for that.
>> > >>>
>> > >>> Ismael
>> > >>>
>> > >>> On Wed, May 15, 2024 at 9:20 AM Chris Egerton <
>> fearthecel...@gmail.com
>> > >
>> > >>> wrote:
>> > >>>
>> > >>> > FWIW I think that the low blast radius for KIP-1028 should allow
>> it
>> > to
>> > >>> > proceed without adhering to the usual KIP and feature freeze
>> dates.
>> > >>> Code
>> > >>> > freeze is probably worth still  respecting, at least if changes
>> are
>> > >>> > required to the docker/jvm/Dockerfile. But I defer to Josep's
>> > >>> judgement as
>> > >>> > the release manager.
>> > >>> >
>> > >>> > On Wed, May 15, 2024, 06:59 Vedarth Sharma <
>> vedarth.sha...@gmail.com
>> > >
>> > >>> > wrote:
>> > >>> >
>> > >>> > > Hey Josep!
>> > >>> > >
>> > >>> > > The KIP 1028 has received the required votes. Voting thread:-
>> > >>> > >
>> https://lists.apache.org/thread/cdq4wfv5v1gpqlxnf46ycwtcwk5wos4q
>> > >>> > > But we are keeping the vote open for 72 hours as per the
>> process.
>> > >>> > >
>> > >>> > > I would like to request you to please consider it for the 3.8.0
>> > >>> release.
>> > >>> > >
>> > >>> > > Thanks and regards,
>> > >>> > > Vedarth
>> > >>> > >
>> > >>> > >
>> > >>> > > On Wed, May 15, 2024 at 1:14 PM Josep Prat
>> > >>> 
>> > >>> > > wrote:
>> > >>> > >
>> > >>> > > > Hi Kafka developers!
>> > >>> > > >
>> > >>> > > > Today is the KIP freeze deadline. All KIPs should be accepted
>> by
>> > >>> EOD
>> > >>> > > today.
>> > >>> > > > Tomorrow morning (CEST timezone) I'll start summarizing all
>> KIPs
>> > >>> that
>> > >>> > > have
>> > >>> > > > been approved. Please any KIP approved after tomorrow should
>> be
>> > >>> adopted
>> > >>> > > in
>> > >>> > > > a future release version, not 3.8.
>> > >>> > > >
>> > >>> > > > Other relevant upcoming deadlines:
>> > >>> > > > - Feature freeze is on May 29th
>> > >>> > > > - Code freeze is June 12th
>> > >>> > > >
>> > >>> > > > Best,
>> > >>> > > >
>> > >>> > > > On Fri, May 3, 2024 at 3:59 PM Josep Prat <
>> josep.p...@aiven.io>
>> > >>> wrote:
>> > >>> > > >
>> > >>> > > > > Hi Kafka developers!
>> > >>> > > > > I just wanted to remind you all of the upcoming relevant
>> dates
>> > >>> for
>> > >>> > > Kafka
>> > 

Re: [DISCUSS] Apache Kafka 3.8.0 release

[Josep Prat]

Hi Nick,

If nobody comes up with concerns or pushback until the time of closing the
vote, I think we can take it for 3.8.

Best,

-

Josep Prat
Open Source Engineering Director, aivenjosep.p...@aiven.io   |
+491715557497 | aiven.io
Aiven Deutschland GmbH
Alexanderufer 3-7, 10117 Berlin
Geschäftsführer: Oskari Saarenmaa & Hannu Valtonen
Amtsgericht Charlottenburg, HRB 209739 B

On Wed, May 15, 2024, 20:48 Nick Telford  wrote:

> Hi Josep,
>
> Would it be possible to sneak KIP-989 into 3.8? Just as with 1028, it's
> currently being voted on and has already received the requisite votes. The
> only thing holding it back is the 72 hour voting window.
>
> Vote thread here:
> https://lists.apache.org/thread/nhr65h4784z49jbsyt5nx8ys81q90k6s
>
> Regards,
>
> Nick
>
> On Wed, 15 May 2024 at 17:47, Josep Prat 
> wrote:
>
> > And my maths are wrong! I added 24 hours more to all the numbers in
> there.
> > If after 72 hours no vetoes appear, I have no objections on adding this
> > specific KIP as it shouldn't have a big blast radius of affectation.
> >
> > Best,
> >
> > On Wed, May 15, 2024 at 6:44 PM Josep Prat  wrote:
> >
> > > Ah, I see Chris was faster writing this than me.
> > >
> > > On Wed, May 15, 2024 at 6:43 PM Josep Prat 
> wrote:
> > >
> > >> Hi all,
> > >> You still have the full day of today (independently for the timezone)
> to
> > >> get KIPs approved. Tomorrow morning (CEST timezone) I'll send another
> > email
> > >> asking developers to assign future approved KIPs to another version
> > that is
> > >> not 3.8.
> > >>
> > >> So, the only problem I see with KIP-1028 is that it hasn't been open
> for
> > >> a vote for 72 hours (48 hours as of now). If there is no negative
> > voting on
> > >> the KIP I think we can let that one in, given it would only miss the
> > >> deadline by less than 12 hours (if my timezone maths add up).
> > >>
> > >> Best,
> > >>
> > >> On Wed, May 15, 2024 at 6:35 PM Ismael Juma 
> wrote:
> > >>
> > >>> The KIP freeze is just about having the KIP accepted. Not sure why we
> > >>> would
> > >>> need an exception for that.
> > >>>
> > >>> Ismael
> > >>>
> > >>> On Wed, May 15, 2024 at 9:20 AM Chris Egerton <
> fearthecel...@gmail.com
> > >
> > >>> wrote:
> > >>>
> > >>> > FWIW I think that the low blast radius for KIP-1028 should allow it
> > to
> > >>> > proceed without adhering to the usual KIP and feature freeze dates.
> > >>> Code
> > >>> > freeze is probably worth still  respecting, at least if changes are
> > >>> > required to the docker/jvm/Dockerfile. But I defer to Josep's
> > >>> judgement as
> > >>> > the release manager.
> > >>> >
> > >>> > On Wed, May 15, 2024, 06:59 Vedarth Sharma <
> vedarth.sha...@gmail.com
> > >
> > >>> > wrote:
> > >>> >
> > >>> > > Hey Josep!
> > >>> > >
> > >>> > > The KIP 1028 has received the required votes. Voting thread:-
> > >>> > > https://lists.apache.org/thread/cdq4wfv5v1gpqlxnf46ycwtcwk5wos4q
> > >>> > > But we are keeping the vote open for 72 hours as per the process.
> > >>> > >
> > >>> > > I would like to request you to please consider it for the 3.8.0
> > >>> release.
> > >>> > >
> > >>> > > Thanks and regards,
> > >>> > > Vedarth
> > >>> > >
> > >>> > >
> > >>> > > On Wed, May 15, 2024 at 1:14 PM Josep Prat
> > >>> 
> > >>> > > wrote:
> > >>> > >
> > >>> > > > Hi Kafka developers!
> > >>> > > >
> > >>> > > > Today is the KIP freeze deadline. All KIPs should be accepted
> by
> > >>> EOD
> > >>> > > today.
> > >>> > > > Tomorrow morning (CEST timezone) I'll start summarizing all
> KIPs
> > >>> that
> > >>> > > have
> > >>> > > > been approved. Please any KIP approved after tomorrow should be
> > >>> adopted
> > >>> > > in
> > >>> > > > a future release version, not 3.8.
> > >>> > > >
> > >>> > > > Other relevant upcoming deadlines:
> > >>> > > > - Feature freeze is on May 29th
> > >>> > > > - Code freeze is June 12th
> > >>> > > >
> > >>> > > > Best,
> > >>> > > >
> > >>> > > > On Fri, May 3, 2024 at 3:59 PM Josep Prat  >
> > >>> wrote:
> > >>> > > >
> > >>> > > > > Hi Kafka developers!
> > >>> > > > > I just wanted to remind you all of the upcoming relevant
> dates
> > >>> for
> > >>> > > Kafka
> > >>> > > > > 3.8.0:
> > >>> > > > > - KIP freeze is on May 15th (this is in a little less than 2
> > >>> weeks)
> > >>> > > > > - Feature freeze is on May 29th (this is in a little more
> than
> > 25
> > >>> > > days).
> > >>> > > > >
> > >>> > > > > If there is a KIP you really want to have in the 3.8 series,
> > now
> > >>> is
> > >>> > the
> > >>> > > > > time to make the last push. Once the deadline for KIP freeze
> is
> > >>> over
> > >>> > > I'll
> > >>> > > > > update the release plan with the final list of KIPs accepted
> > and
> > >>> that
> > >>> > > may
> > >>> > > > > make it to the release.
> > >>> > > > >
> > >>> > > > > Best!
> > >>> > > > >
> > >>> > > > > On Wed, Mar 6, 2024 at 10:40 AM Josep Prat <
> > josep.p...@aiven.io>
> > >>> > > wrote:
> > >>> > > > >
> > >>> > > > >> Hi all,
> > >>> > > > >>
> > 

Re: [DISCUSS] Apache Kafka 3.8.0 release

[Nick Telford]

Hi Josep,

Would it be possible to sneak KIP-989 into 3.8? Just as with 1028, it's
currently being voted on and has already received the requisite votes. The
only thing holding it back is the 72 hour voting window.

Vote thread here:
https://lists.apache.org/thread/nhr65h4784z49jbsyt5nx8ys81q90k6s

Regards,

Nick

On Wed, 15 May 2024 at 17:47, Josep Prat 
wrote:

> And my maths are wrong! I added 24 hours more to all the numbers in there.
> If after 72 hours no vetoes appear, I have no objections on adding this
> specific KIP as it shouldn't have a big blast radius of affectation.
>
> Best,
>
> On Wed, May 15, 2024 at 6:44 PM Josep Prat  wrote:
>
> > Ah, I see Chris was faster writing this than me.
> >
> > On Wed, May 15, 2024 at 6:43 PM Josep Prat  wrote:
> >
> >> Hi all,
> >> You still have the full day of today (independently for the timezone) to
> >> get KIPs approved. Tomorrow morning (CEST timezone) I'll send another
> email
> >> asking developers to assign future approved KIPs to another version
> that is
> >> not 3.8.
> >>
> >> So, the only problem I see with KIP-1028 is that it hasn't been open for
> >> a vote for 72 hours (48 hours as of now). If there is no negative
> voting on
> >> the KIP I think we can let that one in, given it would only miss the
> >> deadline by less than 12 hours (if my timezone maths add up).
> >>
> >> Best,
> >>
> >> On Wed, May 15, 2024 at 6:35 PM Ismael Juma  wrote:
> >>
> >>> The KIP freeze is just about having the KIP accepted. Not sure why we
> >>> would
> >>> need an exception for that.
> >>>
> >>> Ismael
> >>>
> >>> On Wed, May 15, 2024 at 9:20 AM Chris Egerton  >
> >>> wrote:
> >>>
> >>> > FWIW I think that the low blast radius for KIP-1028 should allow it
> to
> >>> > proceed without adhering to the usual KIP and feature freeze dates.
> >>> Code
> >>> > freeze is probably worth still  respecting, at least if changes are
> >>> > required to the docker/jvm/Dockerfile. But I defer to Josep's
> >>> judgement as
> >>> > the release manager.
> >>> >
> >>> > On Wed, May 15, 2024, 06:59 Vedarth Sharma  >
> >>> > wrote:
> >>> >
> >>> > > Hey Josep!
> >>> > >
> >>> > > The KIP 1028 has received the required votes. Voting thread:-
> >>> > > https://lists.apache.org/thread/cdq4wfv5v1gpqlxnf46ycwtcwk5wos4q
> >>> > > But we are keeping the vote open for 72 hours as per the process.
> >>> > >
> >>> > > I would like to request you to please consider it for the 3.8.0
> >>> release.
> >>> > >
> >>> > > Thanks and regards,
> >>> > > Vedarth
> >>> > >
> >>> > >
> >>> > > On Wed, May 15, 2024 at 1:14 PM Josep Prat
> >>> 
> >>> > > wrote:
> >>> > >
> >>> > > > Hi Kafka developers!
> >>> > > >
> >>> > > > Today is the KIP freeze deadline. All KIPs should be accepted by
> >>> EOD
> >>> > > today.
> >>> > > > Tomorrow morning (CEST timezone) I'll start summarizing all KIPs
> >>> that
> >>> > > have
> >>> > > > been approved. Please any KIP approved after tomorrow should be
> >>> adopted
> >>> > > in
> >>> > > > a future release version, not 3.8.
> >>> > > >
> >>> > > > Other relevant upcoming deadlines:
> >>> > > > - Feature freeze is on May 29th
> >>> > > > - Code freeze is June 12th
> >>> > > >
> >>> > > > Best,
> >>> > > >
> >>> > > > On Fri, May 3, 2024 at 3:59 PM Josep Prat 
> >>> wrote:
> >>> > > >
> >>> > > > > Hi Kafka developers!
> >>> > > > > I just wanted to remind you all of the upcoming relevant dates
> >>> for
> >>> > > Kafka
> >>> > > > > 3.8.0:
> >>> > > > > - KIP freeze is on May 15th (this is in a little less than 2
> >>> weeks)
> >>> > > > > - Feature freeze is on May 29th (this is in a little more than
> 25
> >>> > > days).
> >>> > > > >
> >>> > > > > If there is a KIP you really want to have in the 3.8 series,
> now
> >>> is
> >>> > the
> >>> > > > > time to make the last push. Once the deadline for KIP freeze is
> >>> over
> >>> > > I'll
> >>> > > > > update the release plan with the final list of KIPs accepted
> and
> >>> that
> >>> > > may
> >>> > > > > make it to the release.
> >>> > > > >
> >>> > > > > Best!
> >>> > > > >
> >>> > > > > On Wed, Mar 6, 2024 at 10:40 AM Josep Prat <
> josep.p...@aiven.io>
> >>> > > wrote:
> >>> > > > >
> >>> > > > >> Hi all,
> >>> > > > >>
> >>> > > > >> Thanks for your support. I updated the skeleton release plan
> >>> created
> >>> > > by
> >>> > > > >> Colin. You can find it here:
> >>> > > > >>
> >>> > https://cwiki.apache.org/confluence/display/KAFKA/Release+Plan+3.8.0
> >>> > > > >>
> >>> > > > >> Our last release stumbled upon some problems while releasing
> >>> and was
> >>> > > > >> delayed by several weeks, so I won't try to shave some weeks
> >>> from
> >>> > our
> >>> > > > plan
> >>> > > > >> for 3.8.0 (we might end up having delays again). Please raise
> >>> your
> >>> > > > concerns
> >>> > > > >> if you don't agree with the proposed dates.
> >>> > > > >>
> >>> > > > >> The current proposal on dates are:
> >>> > > > >>
> >>> > > > >>- KIP Freeze: *15nd May *(Wednesday)
> >>> > > > >>   - A KIP must be 

Re: [DISCUSS] Apache Kafka 3.8.0 release

[Josep Prat]

And my maths are wrong! I added 24 hours more to all the numbers in there.
If after 72 hours no vetoes appear, I have no objections on adding this
specific KIP as it shouldn't have a big blast radius of affectation.

Best,

On Wed, May 15, 2024 at 6:44 PM Josep Prat  wrote:

> Ah, I see Chris was faster writing this than me.
>
> On Wed, May 15, 2024 at 6:43 PM Josep Prat  wrote:
>
>> Hi all,
>> You still have the full day of today (independently for the timezone) to
>> get KIPs approved. Tomorrow morning (CEST timezone) I'll send another email
>> asking developers to assign future approved KIPs to another version that is
>> not 3.8.
>>
>> So, the only problem I see with KIP-1028 is that it hasn't been open for
>> a vote for 72 hours (48 hours as of now). If there is no negative voting on
>> the KIP I think we can let that one in, given it would only miss the
>> deadline by less than 12 hours (if my timezone maths add up).
>>
>> Best,
>>
>> On Wed, May 15, 2024 at 6:35 PM Ismael Juma  wrote:
>>
>>> The KIP freeze is just about having the KIP accepted. Not sure why we
>>> would
>>> need an exception for that.
>>>
>>> Ismael
>>>
>>> On Wed, May 15, 2024 at 9:20 AM Chris Egerton 
>>> wrote:
>>>
>>> > FWIW I think that the low blast radius for KIP-1028 should allow it to
>>> > proceed without adhering to the usual KIP and feature freeze dates.
>>> Code
>>> > freeze is probably worth still  respecting, at least if changes are
>>> > required to the docker/jvm/Dockerfile. But I defer to Josep's
>>> judgement as
>>> > the release manager.
>>> >
>>> > On Wed, May 15, 2024, 06:59 Vedarth Sharma 
>>> > wrote:
>>> >
>>> > > Hey Josep!
>>> > >
>>> > > The KIP 1028 has received the required votes. Voting thread:-
>>> > > https://lists.apache.org/thread/cdq4wfv5v1gpqlxnf46ycwtcwk5wos4q
>>> > > But we are keeping the vote open for 72 hours as per the process.
>>> > >
>>> > > I would like to request you to please consider it for the 3.8.0
>>> release.
>>> > >
>>> > > Thanks and regards,
>>> > > Vedarth
>>> > >
>>> > >
>>> > > On Wed, May 15, 2024 at 1:14 PM Josep Prat
>>> 
>>> > > wrote:
>>> > >
>>> > > > Hi Kafka developers!
>>> > > >
>>> > > > Today is the KIP freeze deadline. All KIPs should be accepted by
>>> EOD
>>> > > today.
>>> > > > Tomorrow morning (CEST timezone) I'll start summarizing all KIPs
>>> that
>>> > > have
>>> > > > been approved. Please any KIP approved after tomorrow should be
>>> adopted
>>> > > in
>>> > > > a future release version, not 3.8.
>>> > > >
>>> > > > Other relevant upcoming deadlines:
>>> > > > - Feature freeze is on May 29th
>>> > > > - Code freeze is June 12th
>>> > > >
>>> > > > Best,
>>> > > >
>>> > > > On Fri, May 3, 2024 at 3:59 PM Josep Prat 
>>> wrote:
>>> > > >
>>> > > > > Hi Kafka developers!
>>> > > > > I just wanted to remind you all of the upcoming relevant dates
>>> for
>>> > > Kafka
>>> > > > > 3.8.0:
>>> > > > > - KIP freeze is on May 15th (this is in a little less than 2
>>> weeks)
>>> > > > > - Feature freeze is on May 29th (this is in a little more than 25
>>> > > days).
>>> > > > >
>>> > > > > If there is a KIP you really want to have in the 3.8 series, now
>>> is
>>> > the
>>> > > > > time to make the last push. Once the deadline for KIP freeze is
>>> over
>>> > > I'll
>>> > > > > update the release plan with the final list of KIPs accepted and
>>> that
>>> > > may
>>> > > > > make it to the release.
>>> > > > >
>>> > > > > Best!
>>> > > > >
>>> > > > > On Wed, Mar 6, 2024 at 10:40 AM Josep Prat 
>>> > > wrote:
>>> > > > >
>>> > > > >> Hi all,
>>> > > > >>
>>> > > > >> Thanks for your support. I updated the skeleton release plan
>>> created
>>> > > by
>>> > > > >> Colin. You can find it here:
>>> > > > >>
>>> > https://cwiki.apache.org/confluence/display/KAFKA/Release+Plan+3.8.0
>>> > > > >>
>>> > > > >> Our last release stumbled upon some problems while releasing
>>> and was
>>> > > > >> delayed by several weeks, so I won't try to shave some weeks
>>> from
>>> > our
>>> > > > plan
>>> > > > >> for 3.8.0 (we might end up having delays again). Please raise
>>> your
>>> > > > concerns
>>> > > > >> if you don't agree with the proposed dates.
>>> > > > >>
>>> > > > >> The current proposal on dates are:
>>> > > > >>
>>> > > > >>- KIP Freeze: *15nd May *(Wednesday)
>>> > > > >>   - A KIP must be accepted by this date in order to be
>>> > considered
>>> > > > >>   for this release. Note, any KIP that may not be
>>> implemented
>>> > in a
>>> > > > week, or
>>> > > > >>   that might destabilize the release, should be deferred.
>>> > > > >>- Feature Freeze: *29th May *(Wednesday)
>>> > > > >>   - *major features merged & working on stabilisation, minor
>>> > > > >>   features have PR, release branch cut; anything not in this
>>> > state
>>> > > > will be
>>> > > > >>   automatically moved to the next release in JIRA*
>>> > > > >>- Code Freeze: *12th June *(Wednesday)
>>> > > > >>- At least two weeks of stabilization will follow Code
>>> 

Re: [DISCUSS] Apache Kafka 3.8.0 release

[Josep Prat]

Ah, I see Chris was faster writing this than me.

On Wed, May 15, 2024 at 6:43 PM Josep Prat  wrote:

> Hi all,
> You still have the full day of today (independently for the timezone) to
> get KIPs approved. Tomorrow morning (CEST timezone) I'll send another email
> asking developers to assign future approved KIPs to another version that is
> not 3.8.
>
> So, the only problem I see with KIP-1028 is that it hasn't been open for a
> vote for 72 hours (48 hours as of now). If there is no negative voting on
> the KIP I think we can let that one in, given it would only miss the
> deadline by less than 12 hours (if my timezone maths add up).
>
> Best,
>
> On Wed, May 15, 2024 at 6:35 PM Ismael Juma  wrote:
>
>> The KIP freeze is just about having the KIP accepted. Not sure why we
>> would
>> need an exception for that.
>>
>> Ismael
>>
>> On Wed, May 15, 2024 at 9:20 AM Chris Egerton 
>> wrote:
>>
>> > FWIW I think that the low blast radius for KIP-1028 should allow it to
>> > proceed without adhering to the usual KIP and feature freeze dates. Code
>> > freeze is probably worth still  respecting, at least if changes are
>> > required to the docker/jvm/Dockerfile. But I defer to Josep's judgement
>> as
>> > the release manager.
>> >
>> > On Wed, May 15, 2024, 06:59 Vedarth Sharma 
>> > wrote:
>> >
>> > > Hey Josep!
>> > >
>> > > The KIP 1028 has received the required votes. Voting thread:-
>> > > https://lists.apache.org/thread/cdq4wfv5v1gpqlxnf46ycwtcwk5wos4q
>> > > But we are keeping the vote open for 72 hours as per the process.
>> > >
>> > > I would like to request you to please consider it for the 3.8.0
>> release.
>> > >
>> > > Thanks and regards,
>> > > Vedarth
>> > >
>> > >
>> > > On Wed, May 15, 2024 at 1:14 PM Josep Prat
>> 
>> > > wrote:
>> > >
>> > > > Hi Kafka developers!
>> > > >
>> > > > Today is the KIP freeze deadline. All KIPs should be accepted by EOD
>> > > today.
>> > > > Tomorrow morning (CEST timezone) I'll start summarizing all KIPs
>> that
>> > > have
>> > > > been approved. Please any KIP approved after tomorrow should be
>> adopted
>> > > in
>> > > > a future release version, not 3.8.
>> > > >
>> > > > Other relevant upcoming deadlines:
>> > > > - Feature freeze is on May 29th
>> > > > - Code freeze is June 12th
>> > > >
>> > > > Best,
>> > > >
>> > > > On Fri, May 3, 2024 at 3:59 PM Josep Prat 
>> wrote:
>> > > >
>> > > > > Hi Kafka developers!
>> > > > > I just wanted to remind you all of the upcoming relevant dates for
>> > > Kafka
>> > > > > 3.8.0:
>> > > > > - KIP freeze is on May 15th (this is in a little less than 2
>> weeks)
>> > > > > - Feature freeze is on May 29th (this is in a little more than 25
>> > > days).
>> > > > >
>> > > > > If there is a KIP you really want to have in the 3.8 series, now
>> is
>> > the
>> > > > > time to make the last push. Once the deadline for KIP freeze is
>> over
>> > > I'll
>> > > > > update the release plan with the final list of KIPs accepted and
>> that
>> > > may
>> > > > > make it to the release.
>> > > > >
>> > > > > Best!
>> > > > >
>> > > > > On Wed, Mar 6, 2024 at 10:40 AM Josep Prat 
>> > > wrote:
>> > > > >
>> > > > >> Hi all,
>> > > > >>
>> > > > >> Thanks for your support. I updated the skeleton release plan
>> created
>> > > by
>> > > > >> Colin. You can find it here:
>> > > > >>
>> > https://cwiki.apache.org/confluence/display/KAFKA/Release+Plan+3.8.0
>> > > > >>
>> > > > >> Our last release stumbled upon some problems while releasing and
>> was
>> > > > >> delayed by several weeks, so I won't try to shave some weeks from
>> > our
>> > > > plan
>> > > > >> for 3.8.0 (we might end up having delays again). Please raise
>> your
>> > > > concerns
>> > > > >> if you don't agree with the proposed dates.
>> > > > >>
>> > > > >> The current proposal on dates are:
>> > > > >>
>> > > > >>- KIP Freeze: *15nd May *(Wednesday)
>> > > > >>   - A KIP must be accepted by this date in order to be
>> > considered
>> > > > >>   for this release. Note, any KIP that may not be implemented
>> > in a
>> > > > week, or
>> > > > >>   that might destabilize the release, should be deferred.
>> > > > >>- Feature Freeze: *29th May *(Wednesday)
>> > > > >>   - *major features merged & working on stabilisation, minor
>> > > > >>   features have PR, release branch cut; anything not in this
>> > state
>> > > > will be
>> > > > >>   automatically moved to the next release in JIRA*
>> > > > >>- Code Freeze: *12th June *(Wednesday)
>> > > > >>- At least two weeks of stabilization will follow Code Freeze,
>> > > > >>meaning we expect to release *no earlier* than *June 26th*. We
>> > will
>> > > > >>move as fast as we can, and aim for completion the earliest we
>> > can
>> > > > in June.
>> > > > >>
>> > > > >> I went through the KIP list, and found that these are the ones
>> that
>> > > > might
>> > > > >> make it into the release:
>> > > > >> KIP-853: KRaft Controller Membership Changes (still under
>> > discussion)
>> 

Re: [DISCUSS] Apache Kafka 3.8.0 release

[Josep Prat]

Hi all,
You still have the full day of today (independently for the timezone) to
get KIPs approved. Tomorrow morning (CEST timezone) I'll send another email
asking developers to assign future approved KIPs to another version that is
not 3.8.

So, the only problem I see with KIP-1028 is that it hasn't been open for a
vote for 72 hours (48 hours as of now). If there is no negative voting on
the KIP I think we can let that one in, given it would only miss the
deadline by less than 12 hours (if my timezone maths add up).

Best,

On Wed, May 15, 2024 at 6:35 PM Ismael Juma  wrote:

> The KIP freeze is just about having the KIP accepted. Not sure why we would
> need an exception for that.
>
> Ismael
>
> On Wed, May 15, 2024 at 9:20 AM Chris Egerton 
> wrote:
>
> > FWIW I think that the low blast radius for KIP-1028 should allow it to
> > proceed without adhering to the usual KIP and feature freeze dates. Code
> > freeze is probably worth still  respecting, at least if changes are
> > required to the docker/jvm/Dockerfile. But I defer to Josep's judgement
> as
> > the release manager.
> >
> > On Wed, May 15, 2024, 06:59 Vedarth Sharma 
> > wrote:
> >
> > > Hey Josep!
> > >
> > > The KIP 1028 has received the required votes. Voting thread:-
> > > https://lists.apache.org/thread/cdq4wfv5v1gpqlxnf46ycwtcwk5wos4q
> > > But we are keeping the vote open for 72 hours as per the process.
> > >
> > > I would like to request you to please consider it for the 3.8.0
> release.
> > >
> > > Thanks and regards,
> > > Vedarth
> > >
> > >
> > > On Wed, May 15, 2024 at 1:14 PM Josep Prat  >
> > > wrote:
> > >
> > > > Hi Kafka developers!
> > > >
> > > > Today is the KIP freeze deadline. All KIPs should be accepted by EOD
> > > today.
> > > > Tomorrow morning (CEST timezone) I'll start summarizing all KIPs that
> > > have
> > > > been approved. Please any KIP approved after tomorrow should be
> adopted
> > > in
> > > > a future release version, not 3.8.
> > > >
> > > > Other relevant upcoming deadlines:
> > > > - Feature freeze is on May 29th
> > > > - Code freeze is June 12th
> > > >
> > > > Best,
> > > >
> > > > On Fri, May 3, 2024 at 3:59 PM Josep Prat 
> wrote:
> > > >
> > > > > Hi Kafka developers!
> > > > > I just wanted to remind you all of the upcoming relevant dates for
> > > Kafka
> > > > > 3.8.0:
> > > > > - KIP freeze is on May 15th (this is in a little less than 2 weeks)
> > > > > - Feature freeze is on May 29th (this is in a little more than 25
> > > days).
> > > > >
> > > > > If there is a KIP you really want to have in the 3.8 series, now is
> > the
> > > > > time to make the last push. Once the deadline for KIP freeze is
> over
> > > I'll
> > > > > update the release plan with the final list of KIPs accepted and
> that
> > > may
> > > > > make it to the release.
> > > > >
> > > > > Best!
> > > > >
> > > > > On Wed, Mar 6, 2024 at 10:40 AM Josep Prat 
> > > wrote:
> > > > >
> > > > >> Hi all,
> > > > >>
> > > > >> Thanks for your support. I updated the skeleton release plan
> created
> > > by
> > > > >> Colin. You can find it here:
> > > > >>
> > https://cwiki.apache.org/confluence/display/KAFKA/Release+Plan+3.8.0
> > > > >>
> > > > >> Our last release stumbled upon some problems while releasing and
> was
> > > > >> delayed by several weeks, so I won't try to shave some weeks from
> > our
> > > > plan
> > > > >> for 3.8.0 (we might end up having delays again). Please raise your
> > > > concerns
> > > > >> if you don't agree with the proposed dates.
> > > > >>
> > > > >> The current proposal on dates are:
> > > > >>
> > > > >>- KIP Freeze: *15nd May *(Wednesday)
> > > > >>   - A KIP must be accepted by this date in order to be
> > considered
> > > > >>   for this release. Note, any KIP that may not be implemented
> > in a
> > > > week, or
> > > > >>   that might destabilize the release, should be deferred.
> > > > >>- Feature Freeze: *29th May *(Wednesday)
> > > > >>   - *major features merged & working on stabilisation, minor
> > > > >>   features have PR, release branch cut; anything not in this
> > state
> > > > will be
> > > > >>   automatically moved to the next release in JIRA*
> > > > >>- Code Freeze: *12th June *(Wednesday)
> > > > >>- At least two weeks of stabilization will follow Code Freeze,
> > > > >>meaning we expect to release *no earlier* than *June 26th*. We
> > will
> > > > >>move as fast as we can, and aim for completion the earliest we
> > can
> > > > in June.
> > > > >>
> > > > >> I went through the KIP list, and found that these are the ones
> that
> > > > might
> > > > >> make it into the release:
> > > > >> KIP-853: KRaft Controller Membership Changes (still under
> > discussion)
> > > > >> KIP-942: Add Power(ppc64le) support
> > > > >> KIP-966: Eligible Leader Replicas
> > > > >> KIP-974: Docker Image for GraalVM based Native Kafka Broker
> > > > >> KIP-977: Partition-Level Throughput Metrics
> > > > >> KIP-993: Allow restricting files accessed 

Re: [DISCUSS] Apache Kafka 3.8.0 release

[Chris Egerton]

The KIP isn't officially accepted until its vote thread closes after being
open for at least three days. KIP-1028 won't make that deadline.

On Wed, May 15, 2024, 12:36 Ismael Juma  wrote:

> The KIP freeze is just about having the KIP accepted. Not sure why we would
> need an exception for that.
>
> Ismael
>
> On Wed, May 15, 2024 at 9:20 AM Chris Egerton 
> wrote:
>
> > FWIW I think that the low blast radius for KIP-1028 should allow it to
> > proceed without adhering to the usual KIP and feature freeze dates. Code
> > freeze is probably worth still  respecting, at least if changes are
> > required to the docker/jvm/Dockerfile. But I defer to Josep's judgement
> as
> > the release manager.
> >
> > On Wed, May 15, 2024, 06:59 Vedarth Sharma 
> > wrote:
> >
> > > Hey Josep!
> > >
> > > The KIP 1028 has received the required votes. Voting thread:-
> > > https://lists.apache.org/thread/cdq4wfv5v1gpqlxnf46ycwtcwk5wos4q
> > > But we are keeping the vote open for 72 hours as per the process.
> > >
> > > I would like to request you to please consider it for the 3.8.0
> release.
> > >
> > > Thanks and regards,
> > > Vedarth
> > >
> > >
> > > On Wed, May 15, 2024 at 1:14 PM Josep Prat  >
> > > wrote:
> > >
> > > > Hi Kafka developers!
> > > >
> > > > Today is the KIP freeze deadline. All KIPs should be accepted by EOD
> > > today.
> > > > Tomorrow morning (CEST timezone) I'll start summarizing all KIPs that
> > > have
> > > > been approved. Please any KIP approved after tomorrow should be
> adopted
> > > in
> > > > a future release version, not 3.8.
> > > >
> > > > Other relevant upcoming deadlines:
> > > > - Feature freeze is on May 29th
> > > > - Code freeze is June 12th
> > > >
> > > > Best,
> > > >
> > > > On Fri, May 3, 2024 at 3:59 PM Josep Prat 
> wrote:
> > > >
> > > > > Hi Kafka developers!
> > > > > I just wanted to remind you all of the upcoming relevant dates for
> > > Kafka
> > > > > 3.8.0:
> > > > > - KIP freeze is on May 15th (this is in a little less than 2 weeks)
> > > > > - Feature freeze is on May 29th (this is in a little more than 25
> > > days).
> > > > >
> > > > > If there is a KIP you really want to have in the 3.8 series, now is
> > the
> > > > > time to make the last push. Once the deadline for KIP freeze is
> over
> > > I'll
> > > > > update the release plan with the final list of KIPs accepted and
> that
> > > may
> > > > > make it to the release.
> > > > >
> > > > > Best!
> > > > >
> > > > > On Wed, Mar 6, 2024 at 10:40 AM Josep Prat 
> > > wrote:
> > > > >
> > > > >> Hi all,
> > > > >>
> > > > >> Thanks for your support. I updated the skeleton release plan
> created
> > > by
> > > > >> Colin. You can find it here:
> > > > >>
> > https://cwiki.apache.org/confluence/display/KAFKA/Release+Plan+3.8.0
> > > > >>
> > > > >> Our last release stumbled upon some problems while releasing and
> was
> > > > >> delayed by several weeks, so I won't try to shave some weeks from
> > our
> > > > plan
> > > > >> for 3.8.0 (we might end up having delays again). Please raise your
> > > > concerns
> > > > >> if you don't agree with the proposed dates.
> > > > >>
> > > > >> The current proposal on dates are:
> > > > >>
> > > > >>- KIP Freeze: *15nd May *(Wednesday)
> > > > >>   - A KIP must be accepted by this date in order to be
> > considered
> > > > >>   for this release. Note, any KIP that may not be implemented
> > in a
> > > > week, or
> > > > >>   that might destabilize the release, should be deferred.
> > > > >>- Feature Freeze: *29th May *(Wednesday)
> > > > >>   - *major features merged & working on stabilisation, minor
> > > > >>   features have PR, release branch cut; anything not in this
> > state
> > > > will be
> > > > >>   automatically moved to the next release in JIRA*
> > > > >>- Code Freeze: *12th June *(Wednesday)
> > > > >>- At least two weeks of stabilization will follow Code Freeze,
> > > > >>meaning we expect to release *no earlier* than *June 26th*. We
> > will
> > > > >>move as fast as we can, and aim for completion the earliest we
> > can
> > > > in June.
> > > > >>
> > > > >> I went through the KIP list, and found that these are the ones
> that
> > > > might
> > > > >> make it into the release:
> > > > >> KIP-853: KRaft Controller Membership Changes (still under
> > discussion)
> > > > >> KIP-942: Add Power(ppc64le) support
> > > > >> KIP-966: Eligible Leader Replicas
> > > > >> KIP-974: Docker Image for GraalVM based Native Kafka Broker
> > > > >> KIP-977: Partition-Level Throughput Metrics
> > > > >> KIP-993: Allow restricting files accessed by File and Directory
> > > > >> ConfigProviders
> > > > >> KIP-994: Minor Enhancements to ListTransactions and
> > > DescribeTransactions
> > > > >> APIs
> > > > >> KIP-996: Pre-Vote
> > > > >> KIP-1004: Enforce tasks.max property in Kafka Connect
> > > > >> KIP-1005: Expose EarliestLocalOffset and TieredOffset
> > > > >> KIP-1007: Introduce Remote Storage Not Ready Exception
> > > > >> 

Re: [DISCUSS] Apache Kafka 3.8.0 release

[Ismael Juma]

The KIP freeze is just about having the KIP accepted. Not sure why we would
need an exception for that.

Ismael

On Wed, May 15, 2024 at 9:20 AM Chris Egerton 
wrote:

> FWIW I think that the low blast radius for KIP-1028 should allow it to
> proceed without adhering to the usual KIP and feature freeze dates. Code
> freeze is probably worth still  respecting, at least if changes are
> required to the docker/jvm/Dockerfile. But I defer to Josep's judgement as
> the release manager.
>
> On Wed, May 15, 2024, 06:59 Vedarth Sharma 
> wrote:
>
> > Hey Josep!
> >
> > The KIP 1028 has received the required votes. Voting thread:-
> > https://lists.apache.org/thread/cdq4wfv5v1gpqlxnf46ycwtcwk5wos4q
> > But we are keeping the vote open for 72 hours as per the process.
> >
> > I would like to request you to please consider it for the 3.8.0 release.
> >
> > Thanks and regards,
> > Vedarth
> >
> >
> > On Wed, May 15, 2024 at 1:14 PM Josep Prat 
> > wrote:
> >
> > > Hi Kafka developers!
> > >
> > > Today is the KIP freeze deadline. All KIPs should be accepted by EOD
> > today.
> > > Tomorrow morning (CEST timezone) I'll start summarizing all KIPs that
> > have
> > > been approved. Please any KIP approved after tomorrow should be adopted
> > in
> > > a future release version, not 3.8.
> > >
> > > Other relevant upcoming deadlines:
> > > - Feature freeze is on May 29th
> > > - Code freeze is June 12th
> > >
> > > Best,
> > >
> > > On Fri, May 3, 2024 at 3:59 PM Josep Prat  wrote:
> > >
> > > > Hi Kafka developers!
> > > > I just wanted to remind you all of the upcoming relevant dates for
> > Kafka
> > > > 3.8.0:
> > > > - KIP freeze is on May 15th (this is in a little less than 2 weeks)
> > > > - Feature freeze is on May 29th (this is in a little more than 25
> > days).
> > > >
> > > > If there is a KIP you really want to have in the 3.8 series, now is
> the
> > > > time to make the last push. Once the deadline for KIP freeze is over
> > I'll
> > > > update the release plan with the final list of KIPs accepted and that
> > may
> > > > make it to the release.
> > > >
> > > > Best!
> > > >
> > > > On Wed, Mar 6, 2024 at 10:40 AM Josep Prat 
> > wrote:
> > > >
> > > >> Hi all,
> > > >>
> > > >> Thanks for your support. I updated the skeleton release plan created
> > by
> > > >> Colin. You can find it here:
> > > >>
> https://cwiki.apache.org/confluence/display/KAFKA/Release+Plan+3.8.0
> > > >>
> > > >> Our last release stumbled upon some problems while releasing and was
> > > >> delayed by several weeks, so I won't try to shave some weeks from
> our
> > > plan
> > > >> for 3.8.0 (we might end up having delays again). Please raise your
> > > concerns
> > > >> if you don't agree with the proposed dates.
> > > >>
> > > >> The current proposal on dates are:
> > > >>
> > > >>- KIP Freeze: *15nd May *(Wednesday)
> > > >>   - A KIP must be accepted by this date in order to be
> considered
> > > >>   for this release. Note, any KIP that may not be implemented
> in a
> > > week, or
> > > >>   that might destabilize the release, should be deferred.
> > > >>- Feature Freeze: *29th May *(Wednesday)
> > > >>   - *major features merged & working on stabilisation, minor
> > > >>   features have PR, release branch cut; anything not in this
> state
> > > will be
> > > >>   automatically moved to the next release in JIRA*
> > > >>- Code Freeze: *12th June *(Wednesday)
> > > >>- At least two weeks of stabilization will follow Code Freeze,
> > > >>meaning we expect to release *no earlier* than *June 26th*. We
> will
> > > >>move as fast as we can, and aim for completion the earliest we
> can
> > > in June.
> > > >>
> > > >> I went through the KIP list, and found that these are the ones that
> > > might
> > > >> make it into the release:
> > > >> KIP-853: KRaft Controller Membership Changes (still under
> discussion)
> > > >> KIP-942: Add Power(ppc64le) support
> > > >> KIP-966: Eligible Leader Replicas
> > > >> KIP-974: Docker Image for GraalVM based Native Kafka Broker
> > > >> KIP-977: Partition-Level Throughput Metrics
> > > >> KIP-993: Allow restricting files accessed by File and Directory
> > > >> ConfigProviders
> > > >> KIP-994: Minor Enhancements to ListTransactions and
> > DescribeTransactions
> > > >> APIs
> > > >> KIP-996: Pre-Vote
> > > >> KIP-1004: Enforce tasks.max property in Kafka Connect
> > > >> KIP-1005: Expose EarliestLocalOffset and TieredOffset
> > > >> KIP-1007: Introduce Remote Storage Not Ready Exception
> > > >> KIP-1019: Expose method to determine Metric Measurability
> > > >>
> > > >> Please review the plan and provide any additional information or
> > updates
> > > >> regarding KIPs that target this release version (3.8).
> > > >> If you have authored any KIPs that have an inaccurate status in the
> > > list,
> > > >> or are not in the list and should be, or are in the list and should
> > not
> > > be
> > > >> - please share it in this thread so that I can keep the 

Re: [DISCUSS] Apache Kafka 3.8.0 release

[Chris Egerton]

FWIW I think that the low blast radius for KIP-1028 should allow it to
proceed without adhering to the usual KIP and feature freeze dates. Code
freeze is probably worth still  respecting, at least if changes are
required to the docker/jvm/Dockerfile. But I defer to Josep's judgement as
the release manager.

On Wed, May 15, 2024, 06:59 Vedarth Sharma  wrote:

> Hey Josep!
>
> The KIP 1028 has received the required votes. Voting thread:-
> https://lists.apache.org/thread/cdq4wfv5v1gpqlxnf46ycwtcwk5wos4q
> But we are keeping the vote open for 72 hours as per the process.
>
> I would like to request you to please consider it for the 3.8.0 release.
>
> Thanks and regards,
> Vedarth
>
>
> On Wed, May 15, 2024 at 1:14 PM Josep Prat 
> wrote:
>
> > Hi Kafka developers!
> >
> > Today is the KIP freeze deadline. All KIPs should be accepted by EOD
> today.
> > Tomorrow morning (CEST timezone) I'll start summarizing all KIPs that
> have
> > been approved. Please any KIP approved after tomorrow should be adopted
> in
> > a future release version, not 3.8.
> >
> > Other relevant upcoming deadlines:
> > - Feature freeze is on May 29th
> > - Code freeze is June 12th
> >
> > Best,
> >
> > On Fri, May 3, 2024 at 3:59 PM Josep Prat  wrote:
> >
> > > Hi Kafka developers!
> > > I just wanted to remind you all of the upcoming relevant dates for
> Kafka
> > > 3.8.0:
> > > - KIP freeze is on May 15th (this is in a little less than 2 weeks)
> > > - Feature freeze is on May 29th (this is in a little more than 25
> days).
> > >
> > > If there is a KIP you really want to have in the 3.8 series, now is the
> > > time to make the last push. Once the deadline for KIP freeze is over
> I'll
> > > update the release plan with the final list of KIPs accepted and that
> may
> > > make it to the release.
> > >
> > > Best!
> > >
> > > On Wed, Mar 6, 2024 at 10:40 AM Josep Prat 
> wrote:
> > >
> > >> Hi all,
> > >>
> > >> Thanks for your support. I updated the skeleton release plan created
> by
> > >> Colin. You can find it here:
> > >> https://cwiki.apache.org/confluence/display/KAFKA/Release+Plan+3.8.0
> > >>
> > >> Our last release stumbled upon some problems while releasing and was
> > >> delayed by several weeks, so I won't try to shave some weeks from our
> > plan
> > >> for 3.8.0 (we might end up having delays again). Please raise your
> > concerns
> > >> if you don't agree with the proposed dates.
> > >>
> > >> The current proposal on dates are:
> > >>
> > >>- KIP Freeze: *15nd May *(Wednesday)
> > >>   - A KIP must be accepted by this date in order to be considered
> > >>   for this release. Note, any KIP that may not be implemented in a
> > week, or
> > >>   that might destabilize the release, should be deferred.
> > >>- Feature Freeze: *29th May *(Wednesday)
> > >>   - *major features merged & working on stabilisation, minor
> > >>   features have PR, release branch cut; anything not in this state
> > will be
> > >>   automatically moved to the next release in JIRA*
> > >>- Code Freeze: *12th June *(Wednesday)
> > >>- At least two weeks of stabilization will follow Code Freeze,
> > >>meaning we expect to release *no earlier* than *June 26th*. We will
> > >>move as fast as we can, and aim for completion the earliest we can
> > in June.
> > >>
> > >> I went through the KIP list, and found that these are the ones that
> > might
> > >> make it into the release:
> > >> KIP-853: KRaft Controller Membership Changes (still under discussion)
> > >> KIP-942: Add Power(ppc64le) support
> > >> KIP-966: Eligible Leader Replicas
> > >> KIP-974: Docker Image for GraalVM based Native Kafka Broker
> > >> KIP-977: Partition-Level Throughput Metrics
> > >> KIP-993: Allow restricting files accessed by File and Directory
> > >> ConfigProviders
> > >> KIP-994: Minor Enhancements to ListTransactions and
> DescribeTransactions
> > >> APIs
> > >> KIP-996: Pre-Vote
> > >> KIP-1004: Enforce tasks.max property in Kafka Connect
> > >> KIP-1005: Expose EarliestLocalOffset and TieredOffset
> > >> KIP-1007: Introduce Remote Storage Not Ready Exception
> > >> KIP-1019: Expose method to determine Metric Measurability
> > >>
> > >> Please review the plan and provide any additional information or
> updates
> > >> regarding KIPs that target this release version (3.8).
> > >> If you have authored any KIPs that have an inaccurate status in the
> > list,
> > >> or are not in the list and should be, or are in the list and should
> not
> > be
> > >> - please share it in this thread so that I can keep the document
> > accurate
> > >> and up to date.
> > >>
> > >> Looking forward to your feedback.
> > >>
> > >> Best,
> > >>
> > >> On Wed, Feb 28, 2024 at 10:07 AM Satish Duggana <
> > satish.dugg...@gmail.com>
> > >> wrote:
> > >>
> > >>> Thanks Josep, +1.
> > >>>
> > >>> On Tue, 27 Feb 2024 at 17:29, Divij Vaidya 
> > >>> wrote:
> > >>> >
> > >>> > Thank you for volunteering Josep. +1 from me.
> > >>> >
> > >>> > --
> > >>> > 

Re: [DISCUSS] Apache Kafka 3.8.0 release

[Vedarth Sharma]

Hey Josep!

The KIP 1028 has received the required votes. Voting thread:-
https://lists.apache.org/thread/cdq4wfv5v1gpqlxnf46ycwtcwk5wos4q
But we are keeping the vote open for 72 hours as per the process.

I would like to request you to please consider it for the 3.8.0 release.

Thanks and regards,
Vedarth


On Wed, May 15, 2024 at 1:14 PM Josep Prat 
wrote:

> Hi Kafka developers!
>
> Today is the KIP freeze deadline. All KIPs should be accepted by EOD today.
> Tomorrow morning (CEST timezone) I'll start summarizing all KIPs that have
> been approved. Please any KIP approved after tomorrow should be adopted in
> a future release version, not 3.8.
>
> Other relevant upcoming deadlines:
> - Feature freeze is on May 29th
> - Code freeze is June 12th
>
> Best,
>
> On Fri, May 3, 2024 at 3:59 PM Josep Prat  wrote:
>
> > Hi Kafka developers!
> > I just wanted to remind you all of the upcoming relevant dates for Kafka
> > 3.8.0:
> > - KIP freeze is on May 15th (this is in a little less than 2 weeks)
> > - Feature freeze is on May 29th (this is in a little more than 25 days).
> >
> > If there is a KIP you really want to have in the 3.8 series, now is the
> > time to make the last push. Once the deadline for KIP freeze is over I'll
> > update the release plan with the final list of KIPs accepted and that may
> > make it to the release.
> >
> > Best!
> >
> > On Wed, Mar 6, 2024 at 10:40 AM Josep Prat  wrote:
> >
> >> Hi all,
> >>
> >> Thanks for your support. I updated the skeleton release plan created by
> >> Colin. You can find it here:
> >> https://cwiki.apache.org/confluence/display/KAFKA/Release+Plan+3.8.0
> >>
> >> Our last release stumbled upon some problems while releasing and was
> >> delayed by several weeks, so I won't try to shave some weeks from our
> plan
> >> for 3.8.0 (we might end up having delays again). Please raise your
> concerns
> >> if you don't agree with the proposed dates.
> >>
> >> The current proposal on dates are:
> >>
> >>- KIP Freeze: *15nd May *(Wednesday)
> >>   - A KIP must be accepted by this date in order to be considered
> >>   for this release. Note, any KIP that may not be implemented in a
> week, or
> >>   that might destabilize the release, should be deferred.
> >>- Feature Freeze: *29th May *(Wednesday)
> >>   - *major features merged & working on stabilisation, minor
> >>   features have PR, release branch cut; anything not in this state
> will be
> >>   automatically moved to the next release in JIRA*
> >>- Code Freeze: *12th June *(Wednesday)
> >>- At least two weeks of stabilization will follow Code Freeze,
> >>meaning we expect to release *no earlier* than *June 26th*. We will
> >>move as fast as we can, and aim for completion the earliest we can
> in June.
> >>
> >> I went through the KIP list, and found that these are the ones that
> might
> >> make it into the release:
> >> KIP-853: KRaft Controller Membership Changes (still under discussion)
> >> KIP-942: Add Power(ppc64le) support
> >> KIP-966: Eligible Leader Replicas
> >> KIP-974: Docker Image for GraalVM based Native Kafka Broker
> >> KIP-977: Partition-Level Throughput Metrics
> >> KIP-993: Allow restricting files accessed by File and Directory
> >> ConfigProviders
> >> KIP-994: Minor Enhancements to ListTransactions and DescribeTransactions
> >> APIs
> >> KIP-996: Pre-Vote
> >> KIP-1004: Enforce tasks.max property in Kafka Connect
> >> KIP-1005: Expose EarliestLocalOffset and TieredOffset
> >> KIP-1007: Introduce Remote Storage Not Ready Exception
> >> KIP-1019: Expose method to determine Metric Measurability
> >>
> >> Please review the plan and provide any additional information or updates
> >> regarding KIPs that target this release version (3.8).
> >> If you have authored any KIPs that have an inaccurate status in the
> list,
> >> or are not in the list and should be, or are in the list and should not
> be
> >> - please share it in this thread so that I can keep the document
> accurate
> >> and up to date.
> >>
> >> Looking forward to your feedback.
> >>
> >> Best,
> >>
> >> On Wed, Feb 28, 2024 at 10:07 AM Satish Duggana <
> satish.dugg...@gmail.com>
> >> wrote:
> >>
> >>> Thanks Josep, +1.
> >>>
> >>> On Tue, 27 Feb 2024 at 17:29, Divij Vaidya 
> >>> wrote:
> >>> >
> >>> > Thank you for volunteering Josep. +1 from me.
> >>> >
> >>> > --
> >>> > Divij Vaidya
> >>> >
> >>> >
> >>> >
> >>> > On Tue, Feb 27, 2024 at 9:35 AM Bruno Cadonna 
> >>> wrote:
> >>> >
> >>> > > Thanks Josep!
> >>> > >
> >>> > > +1
> >>> > >
> >>> > > Best,
> >>> > > Bruno
> >>> > >
> >>> > > On 2/26/24 9:53 PM, Chris Egerton wrote:
> >>> > > > Thanks Josep, I'm +1 as well.
> >>> > > >
> >>> > > > On Mon, Feb 26, 2024 at 12:32 PM Justine Olshan
> >>> > > >  wrote:
> >>> > > >
> >>> > > >> Thanks Joesp. +1 from me.
> >>> > > >>
> >>> > > >> On Mon, Feb 26, 2024 at 3:37 AM Josep Prat
> >>>  >>> > > >
> >>> > > >> wrote:
> >>> > > >>
> >>> > > >>> Hi all,
> >>> > > >>>
> >>> > > >>> I'd 

Re: [DISCUSS] Apache Kafka 3.8.0 release

[Josep Prat]

Hi Kafka developers!

Today is the KIP freeze deadline. All KIPs should be accepted by EOD today.
Tomorrow morning (CEST timezone) I'll start summarizing all KIPs that have
been approved. Please any KIP approved after tomorrow should be adopted in
a future release version, not 3.8.

Other relevant upcoming deadlines:
- Feature freeze is on May 29th
- Code freeze is June 12th

Best,

On Fri, May 3, 2024 at 3:59 PM Josep Prat  wrote:

> Hi Kafka developers!
> I just wanted to remind you all of the upcoming relevant dates for Kafka
> 3.8.0:
> - KIP freeze is on May 15th (this is in a little less than 2 weeks)
> - Feature freeze is on May 29th (this is in a little more than 25 days).
>
> If there is a KIP you really want to have in the 3.8 series, now is the
> time to make the last push. Once the deadline for KIP freeze is over I'll
> update the release plan with the final list of KIPs accepted and that may
> make it to the release.
>
> Best!
>
> On Wed, Mar 6, 2024 at 10:40 AM Josep Prat  wrote:
>
>> Hi all,
>>
>> Thanks for your support. I updated the skeleton release plan created by
>> Colin. You can find it here:
>> https://cwiki.apache.org/confluence/display/KAFKA/Release+Plan+3.8.0
>>
>> Our last release stumbled upon some problems while releasing and was
>> delayed by several weeks, so I won't try to shave some weeks from our plan
>> for 3.8.0 (we might end up having delays again). Please raise your concerns
>> if you don't agree with the proposed dates.
>>
>> The current proposal on dates are:
>>
>>- KIP Freeze: *15nd May *(Wednesday)
>>   - A KIP must be accepted by this date in order to be considered
>>   for this release. Note, any KIP that may not be implemented in a week, 
>> or
>>   that might destabilize the release, should be deferred.
>>- Feature Freeze: *29th May *(Wednesday)
>>   - *major features merged & working on stabilisation, minor
>>   features have PR, release branch cut; anything not in this state will 
>> be
>>   automatically moved to the next release in JIRA*
>>- Code Freeze: *12th June *(Wednesday)
>>- At least two weeks of stabilization will follow Code Freeze,
>>meaning we expect to release *no earlier* than *June 26th*. We will
>>move as fast as we can, and aim for completion the earliest we can in 
>> June.
>>
>> I went through the KIP list, and found that these are the ones that might
>> make it into the release:
>> KIP-853: KRaft Controller Membership Changes (still under discussion)
>> KIP-942: Add Power(ppc64le) support
>> KIP-966: Eligible Leader Replicas
>> KIP-974: Docker Image for GraalVM based Native Kafka Broker
>> KIP-977: Partition-Level Throughput Metrics
>> KIP-993: Allow restricting files accessed by File and Directory
>> ConfigProviders
>> KIP-994: Minor Enhancements to ListTransactions and DescribeTransactions
>> APIs
>> KIP-996: Pre-Vote
>> KIP-1004: Enforce tasks.max property in Kafka Connect
>> KIP-1005: Expose EarliestLocalOffset and TieredOffset
>> KIP-1007: Introduce Remote Storage Not Ready Exception
>> KIP-1019: Expose method to determine Metric Measurability
>>
>> Please review the plan and provide any additional information or updates
>> regarding KIPs that target this release version (3.8).
>> If you have authored any KIPs that have an inaccurate status in the list,
>> or are not in the list and should be, or are in the list and should not be
>> - please share it in this thread so that I can keep the document accurate
>> and up to date.
>>
>> Looking forward to your feedback.
>>
>> Best,
>>
>> On Wed, Feb 28, 2024 at 10:07 AM Satish Duggana 
>> wrote:
>>
>>> Thanks Josep, +1.
>>>
>>> On Tue, 27 Feb 2024 at 17:29, Divij Vaidya 
>>> wrote:
>>> >
>>> > Thank you for volunteering Josep. +1 from me.
>>> >
>>> > --
>>> > Divij Vaidya
>>> >
>>> >
>>> >
>>> > On Tue, Feb 27, 2024 at 9:35 AM Bruno Cadonna 
>>> wrote:
>>> >
>>> > > Thanks Josep!
>>> > >
>>> > > +1
>>> > >
>>> > > Best,
>>> > > Bruno
>>> > >
>>> > > On 2/26/24 9:53 PM, Chris Egerton wrote:
>>> > > > Thanks Josep, I'm +1 as well.
>>> > > >
>>> > > > On Mon, Feb 26, 2024 at 12:32 PM Justine Olshan
>>> > > >  wrote:
>>> > > >
>>> > > >> Thanks Joesp. +1 from me.
>>> > > >>
>>> > > >> On Mon, Feb 26, 2024 at 3:37 AM Josep Prat
>>> >> > > >
>>> > > >> wrote:
>>> > > >>
>>> > > >>> Hi all,
>>> > > >>>
>>> > > >>> I'd like to volunteer as release manager for the Apache Kafka
>>> 3.8.0
>>> > > >>> release.
>>> > > >>> If there are no objections, I'll start building a release plan
>>> (or
>>> > > >> adapting
>>> > > >>> the one Colin made some weeks ago) in the wiki in the next days.
>>> > > >>>
>>> > > >>> Thank you.
>>> > > >>>
>>> > > >>> --
>>> > > >>> [image: Aiven] 
>>> > > >>>
>>> > > >>> *Josep Prat*
>>> > > >>> Open Source Engineering Director, *Aiven*
>>> > > >>> josep.p...@aiven.io   |   +491715557497
>>> > > >>> aiven.io    |   <
>>> > > >> https://www.facebook.com/aivencloud
>>> > > 
>>> > > 

Re: [DISCUSS] Apache Kafka 3.8.0 release

[Josep Prat]

Hi Kafka developers!
I just wanted to remind you all of the upcoming relevant dates for Kafka
3.8.0:
- KIP freeze is on May 15th (this is in a little less than 2 weeks)
- Feature freeze is on May 29th (this is in a little more than 25 days).

If there is a KIP you really want to have in the 3.8 series, now is the
time to make the last push. Once the deadline for KIP freeze is over I'll
update the release plan with the final list of KIPs accepted and that may
make it to the release.

Best!

On Wed, Mar 6, 2024 at 10:40 AM Josep Prat  wrote:

> Hi all,
>
> Thanks for your support. I updated the skeleton release plan created by
> Colin. You can find it here:
> https://cwiki.apache.org/confluence/display/KAFKA/Release+Plan+3.8.0
>
> Our last release stumbled upon some problems while releasing and was
> delayed by several weeks, so I won't try to shave some weeks from our plan
> for 3.8.0 (we might end up having delays again). Please raise your concerns
> if you don't agree with the proposed dates.
>
> The current proposal on dates are:
>
>- KIP Freeze: *15nd May *(Wednesday)
>   - A KIP must be accepted by this date in order to be considered for
>   this release. Note, any KIP that may not be implemented in a week, or 
> that
>   might destabilize the release, should be deferred.
>- Feature Freeze: *29th May *(Wednesday)
>   - *major features merged & working on stabilisation, minor features
>   have PR, release branch cut; anything not in this state will be
>   automatically moved to the next release in JIRA*
>- Code Freeze: *12th June *(Wednesday)
>- At least two weeks of stabilization will follow Code Freeze, meaning
>we expect to release *no earlier* than *June 26th*. We will move as
>fast as we can, and aim for completion the earliest we can in June.
>
> I went through the KIP list, and found that these are the ones that might
> make it into the release:
> KIP-853: KRaft Controller Membership Changes (still under discussion)
> KIP-942: Add Power(ppc64le) support
> KIP-966: Eligible Leader Replicas
> KIP-974: Docker Image for GraalVM based Native Kafka Broker
> KIP-977: Partition-Level Throughput Metrics
> KIP-993: Allow restricting files accessed by File and Directory
> ConfigProviders
> KIP-994: Minor Enhancements to ListTransactions and DescribeTransactions
> APIs
> KIP-996: Pre-Vote
> KIP-1004: Enforce tasks.max property in Kafka Connect
> KIP-1005: Expose EarliestLocalOffset and TieredOffset
> KIP-1007: Introduce Remote Storage Not Ready Exception
> KIP-1019: Expose method to determine Metric Measurability
>
> Please review the plan and provide any additional information or updates
> regarding KIPs that target this release version (3.8).
> If you have authored any KIPs that have an inaccurate status in the list,
> or are not in the list and should be, or are in the list and should not be
> - please share it in this thread so that I can keep the document accurate
> and up to date.
>
> Looking forward to your feedback.
>
> Best,
>
> On Wed, Feb 28, 2024 at 10:07 AM Satish Duggana 
> wrote:
>
>> Thanks Josep, +1.
>>
>> On Tue, 27 Feb 2024 at 17:29, Divij Vaidya 
>> wrote:
>> >
>> > Thank you for volunteering Josep. +1 from me.
>> >
>> > --
>> > Divij Vaidya
>> >
>> >
>> >
>> > On Tue, Feb 27, 2024 at 9:35 AM Bruno Cadonna 
>> wrote:
>> >
>> > > Thanks Josep!
>> > >
>> > > +1
>> > >
>> > > Best,
>> > > Bruno
>> > >
>> > > On 2/26/24 9:53 PM, Chris Egerton wrote:
>> > > > Thanks Josep, I'm +1 as well.
>> > > >
>> > > > On Mon, Feb 26, 2024 at 12:32 PM Justine Olshan
>> > > >  wrote:
>> > > >
>> > > >> Thanks Joesp. +1 from me.
>> > > >>
>> > > >> On Mon, Feb 26, 2024 at 3:37 AM Josep Prat
>> > > > >
>> > > >> wrote:
>> > > >>
>> > > >>> Hi all,
>> > > >>>
>> > > >>> I'd like to volunteer as release manager for the Apache Kafka
>> 3.8.0
>> > > >>> release.
>> > > >>> If there are no objections, I'll start building a release plan (or
>> > > >> adapting
>> > > >>> the one Colin made some weeks ago) in the wiki in the next days.
>> > > >>>
>> > > >>> Thank you.
>> > > >>>
>> > > >>> --
>> > > >>> [image: Aiven] 
>> > > >>>
>> > > >>> *Josep Prat*
>> > > >>> Open Source Engineering Director, *Aiven*
>> > > >>> josep.p...@aiven.io   |   +491715557497
>> > > >>> aiven.io    |   <
>> > > >> https://www.facebook.com/aivencloud
>> > > 
>> > > >>>   <
>> > > >>> https://twitter.com/aiven_io>
>> > > >>> *Aiven Deutschland GmbH*
>> > > >>> Alexanderufer 3-7, 10117 Berlin
>> > > >>> Geschäftsführer: Oskari Saarenmaa & Hannu Valtonen
>> > > >>> Amtsgericht Charlottenburg, HRB 209739 B
>> > > >>>
>> > > >>
>> > > >
>> > >
>>
>
>
> --
> [image: Aiven] 
>
> *Josep Prat*
> Open Source Engineering Director, *Aiven*
> josep.p...@aiven.io   |   +491715557497
> aiven.io    |
> 
> 

Re: [DISCUSS] Apache Kafka 3.8.0 release

[Josep Prat]

Hi all,

Thanks for your support. I updated the skeleton release plan created by
Colin. You can find it here:
https://cwiki.apache.org/confluence/display/KAFKA/Release+Plan+3.8.0

Our last release stumbled upon some problems while releasing and was
delayed by several weeks, so I won't try to shave some weeks from our plan
for 3.8.0 (we might end up having delays again). Please raise your concerns
if you don't agree with the proposed dates.

The current proposal on dates are:

   - KIP Freeze: *15nd May *(Wednesday)
  - A KIP must be accepted by this date in order to be considered for
  this release. Note, any KIP that may not be implemented in a
week, or that
  might destabilize the release, should be deferred.
   - Feature Freeze: *29th May *(Wednesday)
  - *major features merged & working on stabilisation, minor features
  have PR, release branch cut; anything not in this state will be
  automatically moved to the next release in JIRA*
   - Code Freeze: *12th June *(Wednesday)
   - At least two weeks of stabilization will follow Code Freeze, meaning
   we expect to release *no earlier* than *June 26th*. We will move as fast
   as we can, and aim for completion the earliest we can in June.

I went through the KIP list, and found that these are the ones that might
make it into the release:
KIP-853: KRaft Controller Membership Changes (still under discussion)
KIP-942: Add Power(ppc64le) support
KIP-966: Eligible Leader Replicas
KIP-974: Docker Image for GraalVM based Native Kafka Broker
KIP-977: Partition-Level Throughput Metrics
KIP-993: Allow restricting files accessed by File and Directory
ConfigProviders
KIP-994: Minor Enhancements to ListTransactions and DescribeTransactions
APIs
KIP-996: Pre-Vote
KIP-1004: Enforce tasks.max property in Kafka Connect
KIP-1005: Expose EarliestLocalOffset and TieredOffset
KIP-1007: Introduce Remote Storage Not Ready Exception
KIP-1019: Expose method to determine Metric Measurability

Please review the plan and provide any additional information or updates
regarding KIPs that target this release version (3.8).
If you have authored any KIPs that have an inaccurate status in the list,
or are not in the list and should be, or are in the list and should not be
- please share it in this thread so that I can keep the document accurate
and up to date.

Looking forward to your feedback.

Best,

On Wed, Feb 28, 2024 at 10:07 AM Satish Duggana 
wrote:

> Thanks Josep, +1.
>
> On Tue, 27 Feb 2024 at 17:29, Divij Vaidya 
> wrote:
> >
> > Thank you for volunteering Josep. +1 from me.
> >
> > --
> > Divij Vaidya
> >
> >
> >
> > On Tue, Feb 27, 2024 at 9:35 AM Bruno Cadonna 
> wrote:
> >
> > > Thanks Josep!
> > >
> > > +1
> > >
> > > Best,
> > > Bruno
> > >
> > > On 2/26/24 9:53 PM, Chris Egerton wrote:
> > > > Thanks Josep, I'm +1 as well.
> > > >
> > > > On Mon, Feb 26, 2024 at 12:32 PM Justine Olshan
> > > >  wrote:
> > > >
> > > >> Thanks Joesp. +1 from me.
> > > >>
> > > >> On Mon, Feb 26, 2024 at 3:37 AM Josep Prat
>  > > >
> > > >> wrote:
> > > >>
> > > >>> Hi all,
> > > >>>
> > > >>> I'd like to volunteer as release manager for the Apache Kafka 3.8.0
> > > >>> release.
> > > >>> If there are no objections, I'll start building a release plan (or
> > > >> adapting
> > > >>> the one Colin made some weeks ago) in the wiki in the next days.
> > > >>>
> > > >>> Thank you.
> > > >>>
> > > >>> --
> > > >>> [image: Aiven] 
> > > >>>
> > > >>> *Josep Prat*
> > > >>> Open Source Engineering Director, *Aiven*
> > > >>> josep.p...@aiven.io   |   +491715557497
> > > >>> aiven.io    |   <
> > > >> https://www.facebook.com/aivencloud
> > > 
> > > >>>   <
> > > >>> https://twitter.com/aiven_io>
> > > >>> *Aiven Deutschland GmbH*
> > > >>> Alexanderufer 3-7, 10117 Berlin
> > > >>> Geschäftsführer: Oskari Saarenmaa & Hannu Valtonen
> > > >>> Amtsgericht Charlottenburg, HRB 209739 B
> > > >>>
> > > >>
> > > >
> > >
>


-- 
[image: Aiven] 

*Josep Prat*
Open Source Engineering Director, *Aiven*
josep.p...@aiven.io   |   +491715557497
aiven.io    |   
     
*Aiven Deutschland GmbH*
Alexanderufer 3-7, 10117 Berlin
Geschäftsführer: Oskari Saarenmaa & Hannu Valtonen
Amtsgericht Charlottenburg, HRB 209739 B

Re: [DISCUSS] Apache Kafka 3.8.0 release

[Satish Duggana]

Thanks Josep, +1.

On Tue, 27 Feb 2024 at 17:29, Divij Vaidya  wrote:
>
> Thank you for volunteering Josep. +1 from me.
>
> --
> Divij Vaidya
>
>
>
> On Tue, Feb 27, 2024 at 9:35 AM Bruno Cadonna  wrote:
>
> > Thanks Josep!
> >
> > +1
> >
> > Best,
> > Bruno
> >
> > On 2/26/24 9:53 PM, Chris Egerton wrote:
> > > Thanks Josep, I'm +1 as well.
> > >
> > > On Mon, Feb 26, 2024 at 12:32 PM Justine Olshan
> > >  wrote:
> > >
> > >> Thanks Joesp. +1 from me.
> > >>
> > >> On Mon, Feb 26, 2024 at 3:37 AM Josep Prat  > >
> > >> wrote:
> > >>
> > >>> Hi all,
> > >>>
> > >>> I'd like to volunteer as release manager for the Apache Kafka 3.8.0
> > >>> release.
> > >>> If there are no objections, I'll start building a release plan (or
> > >> adapting
> > >>> the one Colin made some weeks ago) in the wiki in the next days.
> > >>>
> > >>> Thank you.
> > >>>
> > >>> --
> > >>> [image: Aiven] 
> > >>>
> > >>> *Josep Prat*
> > >>> Open Source Engineering Director, *Aiven*
> > >>> josep.p...@aiven.io   |   +491715557497
> > >>> aiven.io    |   <
> > >> https://www.facebook.com/aivencloud
> > 
> > >>>   <
> > >>> https://twitter.com/aiven_io>
> > >>> *Aiven Deutschland GmbH*
> > >>> Alexanderufer 3-7, 10117 Berlin
> > >>> Geschäftsführer: Oskari Saarenmaa & Hannu Valtonen
> > >>> Amtsgericht Charlottenburg, HRB 209739 B
> > >>>
> > >>
> > >
> >

Re: [DISCUSS] Apache Kafka 3.8.0 release

[Divij Vaidya]

Thank you for volunteering Josep. +1 from me.

--
Divij Vaidya



On Tue, Feb 27, 2024 at 9:35 AM Bruno Cadonna  wrote:

> Thanks Josep!
>
> +1
>
> Best,
> Bruno
>
> On 2/26/24 9:53 PM, Chris Egerton wrote:
> > Thanks Josep, I'm +1 as well.
> >
> > On Mon, Feb 26, 2024 at 12:32 PM Justine Olshan
> >  wrote:
> >
> >> Thanks Joesp. +1 from me.
> >>
> >> On Mon, Feb 26, 2024 at 3:37 AM Josep Prat  >
> >> wrote:
> >>
> >>> Hi all,
> >>>
> >>> I'd like to volunteer as release manager for the Apache Kafka 3.8.0
> >>> release.
> >>> If there are no objections, I'll start building a release plan (or
> >> adapting
> >>> the one Colin made some weeks ago) in the wiki in the next days.
> >>>
> >>> Thank you.
> >>>
> >>> --
> >>> [image: Aiven] 
> >>>
> >>> *Josep Prat*
> >>> Open Source Engineering Director, *Aiven*
> >>> josep.p...@aiven.io   |   +491715557497
> >>> aiven.io    |   <
> >> https://www.facebook.com/aivencloud
> 
> >>>   <
> >>> https://twitter.com/aiven_io>
> >>> *Aiven Deutschland GmbH*
> >>> Alexanderufer 3-7, 10117 Berlin
> >>> Geschäftsführer: Oskari Saarenmaa & Hannu Valtonen
> >>> Amtsgericht Charlottenburg, HRB 209739 B
> >>>
> >>
> >
>

Re: [DISCUSS] Apache Kafka 3.8.0 release

[Bruno Cadonna]

Thanks Josep!

+1

Best,
Bruno

On 2/26/24 9:53 PM, Chris Egerton wrote:

Thanks Josep, I'm +1 as well.

On Mon, Feb 26, 2024 at 12:32 PM Justine Olshan
 wrote:


Thanks Joesp. +1 from me.

On Mon, Feb 26, 2024 at 3:37 AM Josep Prat 
wrote:


Hi all,

I'd like to volunteer as release manager for the Apache Kafka 3.8.0
release.
If there are no objections, I'll start building a release plan (or

adapting

the one Colin made some weeks ago) in the wiki in the next days.

Thank you.

--
[image: Aiven] 

*Josep Prat*
Open Source Engineering Director, *Aiven*
josep.p...@aiven.io   |   +491715557497
aiven.io    |   <

https://www.facebook.com/aivencloud



      <
https://twitter.com/aiven_io>
*Aiven Deutschland GmbH*
Alexanderufer 3-7, 10117 Berlin
Geschäftsführer: Oskari Saarenmaa & Hannu Valtonen
Amtsgericht Charlottenburg, HRB 209739 B

Re: [DISCUSS] Apache Kafka 3.8.0 release

[Chris Egerton]

Thanks Josep, I'm +1 as well.

On Mon, Feb 26, 2024 at 12:32 PM Justine Olshan
 wrote:

> Thanks Joesp. +1 from me.
>
> On Mon, Feb 26, 2024 at 3:37 AM Josep Prat 
> wrote:
>
> > Hi all,
> >
> > I'd like to volunteer as release manager for the Apache Kafka 3.8.0
> > release.
> > If there are no objections, I'll start building a release plan (or
> adapting
> > the one Colin made some weeks ago) in the wiki in the next days.
> >
> > Thank you.
> >
> > --
> > [image: Aiven] 
> >
> > *Josep Prat*
> > Open Source Engineering Director, *Aiven*
> > josep.p...@aiven.io   |   +491715557497
> > aiven.io    |   <
> https://www.facebook.com/aivencloud
> > >
> >      <
> > https://twitter.com/aiven_io>
> > *Aiven Deutschland GmbH*
> > Alexanderufer 3-7, 10117 Berlin
> > Geschäftsführer: Oskari Saarenmaa & Hannu Valtonen
> > Amtsgericht Charlottenburg, HRB 209739 B
> >
>

Re: [DISCUSS] Apache Kafka 3.8.0 release

[Justine Olshan]

Thanks Joesp. +1 from me.

On Mon, Feb 26, 2024 at 3:37 AM Josep Prat 
wrote:

> Hi all,
>
> I'd like to volunteer as release manager for the Apache Kafka 3.8.0
> release.
> If there are no objections, I'll start building a release plan (or adapting
> the one Colin made some weeks ago) in the wiki in the next days.
>
> Thank you.
>
> --
> [image: Aiven] 
>
> *Josep Prat*
> Open Source Engineering Director, *Aiven*
> josep.p...@aiven.io   |   +491715557497
> aiven.io    |    >
>      <
> https://twitter.com/aiven_io>
> *Aiven Deutschland GmbH*
> Alexanderufer 3-7, 10117 Berlin
> Geschäftsführer: Oskari Saarenmaa & Hannu Valtonen
> Amtsgericht Charlottenburg, HRB 209739 B
>