Re: [DISCUSS] Apache Kafka 3.8.0 release

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-

Re: [DISCUSS] Apache Kafka 3.8.0 release

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 pro

Re: [DISCUSS] Apache Kafka 3.8.0 release

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 Alexande

Re: [DISCUSS] Apache Kafka 3.8.0 release

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: Work

Re: [DISCUSS] Apache Kafka 3.8.0 release

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 Kafk

Re: [DISCUSS] Apache Kafka 3.8.0 release

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 A

Re: [DISCUSS] Apache Kafka 3.8.0 release

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 Berl

Re: [DISCUSS] Apache Kafka 3.8.0 release

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:

Re: [DISCUSS] Apache Kafka 3.8.0 release

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: htt

Re: [DISCUSS] Apache Kafka 3.8.0 release

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

Re: [DISCUSS] Apache Kafka 3.8.0 release

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 testin

Re: [DISCUSS] Apache Kafka 3.8.0 release

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

Re: [DISCUSS] Apache Kafka 3.8.0 release

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.

Re: [DISCUSS] Apache Kafka 3.8.0 release

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, 2

Re: [DISCUSS] Apache Kafka 3.8.0 release

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* ses

Re: [DISCUSS] Apache Kafka 3.8.0 release

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_q

Re: [DISCUSS] Apache Kafka 3.8.0 release

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 ru

Re: [DISCUSS] Apache Kafka 3.8.0 release

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

Re: [DISCUSS] Apache Kafka 3.8.0 release

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

Re: [DISCUSS] Apache Kafka 3.8.0 release

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 Alexand

Re: [DISCUSS] Apache Kafka 3.8.0 release

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

Re: [DISCUSS] Apache Kafka 3.8.0 release

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 i

Re: [DISCUSS] Apache Kafka 3.8.0 release

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

Re: [DISCUSS] Apache Kafka 3.8.0 release

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 o

Re: [DISCUSS] Apache Kafka 3.8.0 release

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

Re: [DISCUSS] Apache Kafka 3.8.0 release

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. > > J

Re: [DISCUSS] Apache Kafka 3.8.0 release

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, no

Re: [DISCUSS] Apache Kafka 3.8.0 release

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 cu

Re: [DISCUSS] Apache Kafka 3.8.0 release

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.

Re: [DISCUSS] Apache Kafka 3.8.0 release

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

Re: [DISCUSS] Apache Kafka 3.8.0 release

+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

Re: [DISCUSS] Apache Kafka 3.8.0 release

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.

Re: [DISCUSS] Apache Kafka 3.8.0 release

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! > > O

Re: [DISCUSS] Apache Kafka 3.8.0 release

+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

Re: [DISCUSS] Apache Kafka 3.8.0 release

+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 br

Re: [DISCUSS] Apache Kafka 3.8.0 release

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 sta

Re: [DISCUSS] Apache Kafka 3.8.0 release

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/confluen

Re: [DISCUSS] Apache Kafka 3.8.0 release

+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 t

Re: [DISCUSS] Apache Kafka 3.8.0 release

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 maintain

Re: [DISCUSS] Apache Kafka 3.8.0 release

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, w

Re: [DISCUSS] Apache Kafka 3.8.0 release

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, > >

Re: [DISCUSS] Apache Kafka 3.8.0 release

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 releasi

Re: [DISCUSS] Apache Kafka 3.8.0 release

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 > >

Re: [DISCUSS] Apache Kafka 3.8.0 release

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

Re: [DISCUSS] Apache Kafka 3.8.0 release

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...@

Re: [DISCUSS] Apache Kafka 3.8.0 release

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

Re: [DISCUSS] Apache Kafka 3.8.0 release

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

Re: [DISCUSS] Apache Kafka 3.8.0 release

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

Re: [DISCUSS] Apache Kafka 3.8.0 release

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, 2

Re: [DISCUSS] Apache Kafka 3.8.0 release

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 Ju

Re: [DISCUSS] Apache Kafka 3.8.0 release

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 rel

Re: [DISCUSS] Apache Kafka 3.8.0 release

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

Re: [DISCUSS] Apache Kafka 3.8.0 release

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 b

Re: [DISCUSS] Apache Kafka 3.8.0 release

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

Re: [DISCUSS] Apache Kafka 3.8.0 release

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 cher

Re: [DISCUSS] Apache Kafka 3.8.0 release

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

Re: [DISCUSS] Apache Kafka 3.8.0 release

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 rea

Re: [DISCUSS] Apache Kafka 3.8.0 release

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

Re: [DISCUSS] Apache Kafka 3.8.0 release

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 comple

Re: [DISCUSS] Apache Kafka 3.8.0 release

> > 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-p

Re: [DISCUSS] Apache Kafka 3.8.0 release

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 th

Re: [DISCUSS] Apache Kafka 3.8.0 release

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

Re: [DISCUSS] Apache Kafka 3.8.0 release

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

Re: [DISCUSS] Apache Kafka 3.8.0 release

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 critica

Re: [DISCUSS] Apache Kafka 3.8.0 release

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 fo

Re: [DISCUSS] Apache Kafka 3.8.0 release

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 canno

Re: [DISCUSS] Apache Kafka 3.8.0 release

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

Re: [DISCUSS] Apache Kafka 3.8.0 release

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

Re: [DISCUSS] Apache Kafka 3.8.0 release

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 wi

Re: [DISCUSS] Apache Kafka 3.8.0 release

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 

Re: [DISCUSS] Apache Kafka 3.8.0 release

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

Re: [DISCUSS] Apache Kafka 3.8.0 release

n 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 Exte

Re: [DISCUSS] Apache Kafka 3.8.0 release

pache.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. Th

Re: [DISCUSS] Apache Kafka 3.8.0 release

: [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

Re: [DISCUSS] Apache Kafka 3.8.0 release

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 woul

Re: [DISCUSS] Apache Kafka 3.8.0 release

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 bra

Re: [DISCUSS] Apache Kafka 3.8.0 release

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)

Re: [DISCUSS] Apache Kafka 3.8.0 release

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 feature

Re: [DISCUSS] Apache Kafka 3.8.0 release

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 som

Re: [DISCUSS] Apache Kafka 3.8.0 release

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

Re: [DISCUSS] Apache Kafka 3.8.0 release

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

Re: [DISCUSS] Apache Kafka 3.8.0 release

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 p

Re: [DISCUSS] Apache Kafka 3.8.0 release

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 -

Re: [DISCUSS] Apache Kafka 3.8.0 release

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 Be

Re: [DISCUSS] Apache Kafka 3.8.0 release

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

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 f

Re: [DISCUSS] Apache Kafka 3.8.0 release

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 futu

Re: [DISCUSS] Apache Kafka 3.8.0 release

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

Re: [DISCUSS] Apache Kafka 3.8.0 release

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. >

Re: [DISCUSS] Apache Kafka 3.8.0 release

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 fr

Re: [DISCUSS] Apache Kafka 3.8.0 release

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

Re: [DISCUSS] Apache Kafka 3.8.0 release

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,

Re: [DISCUSS] Apache Kafka 3.8.0 release

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

Re: [DISCUSS] Apache Kafka 3.8.0 release

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 ser

Re: [DISCUSS] Apache Kafka 3.8.0 release

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

Re: [DISCUSS] Apache Kafka 3.8.0 release

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 Egerto

Re: [DISCUSS] Apache Kafka 3.8.0 release

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 >

Re: [DISCUSS] Apache Kafka 3.8.0 release

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 t

Re: [DISCUSS] Apache Kafka 3.8.0 release

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 obj

Re: [DISCUSS] Apache Kafka 3.8.0 release

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

  1   2   >