Re: New release branch 3.9

Hi Colin, I agree with you, this is not a blocker. We merged those to trunk and 3.8 already, but without your feedback. I'll try to address it today. Best, -- Josep Prat Open Source Engineering Director, Aiven josep.p...@aiven.io | +491715557497 | aiven.io Aiven Deutschland Gmb

Re: New release branch 3.9

Thanks for the PR, Josep. I don't think it's critical to re-generate the RC since we can simply update the docs on the website later as we've done in the past. If there is a new RC after RC2, it will be there, though. Also it looks like this will be a good fix for 3.8.1 as well :) best, Colin

Re: New release branch 3.9

Hi Colin, if you haven't started probably it makes sense to merge https://github.com/apache/kafka/pull/17447 as well. Best, -- Josep Prat Open Source Engineering Director, Aiven josep.p...@aiven.io | +491715557497 | aiven.io Aiven Deutschland GmbH Alexanderufer 3-7, 10117 Berl

Re: New release branch 3.9

Hi all, I have merged KAFKA-17731 and KAFKA-17749 to 3.9. Also KAFKA-17751. We should be ready for the next RC now. Colin On Thu, Oct 10, 2024, at 08:45, Mickael Maison wrote: > Hi, > > Following up on https://issues.apache.org/jira/browse/KAFKA-17749. We > merged the fix in trunk and 3.8. > I

Re: New release branch 3.9

Hi, Following up on https://issues.apache.org/jira/browse/KAFKA-17749. We merged the fix in trunk and 3.8. I opened a PR for 3.9: https://github.com/apache/kafka/pull/17457 Thanks, Mickael On Thu, Oct 10, 2024 at 3:14 PM Lianet M. wrote: > > Hi Colin, > > Also, we discovered a bug affecting 3.9

Re: New release branch 3.9

Hi Colin, Also, we discovered a bug affecting 3.9, that I would see as a regression given that it degrades the consumer#close. Fix has been merged to trunk with https://github.com/apache/kafka/pull/17431 so wonder if we should include it. Thanks, Lianet On Thu, Oct 10, 2024 at 9:09 AM Mickael

Re: New release branch 3.9

Hi Colin, In Kafka 3.8 we accidentally renamed a metric: https://issues.apache.org/jira/browse/KAFKA-17749 I wonder if we should include the fix to revert it to its original name in 3.9.0 (and 3.8.1) to limit the impact: https://github.com/apache/kafka/pull/17430 Thanks, Mickael On Wed, Oct 9, 2

Re: New release branch 3.9

Thanks Colin, I reviewed the PR you shared. Best, On Wed, Oct 9, 2024 at 6:26 PM Colin McCabe wrote: > Hi Josep, > > I marked this as a blocker. We will take a look. I also found some > dependencies that need to be updated due to CVEs. See > github.com/apache/kafka/pull/17436 > > best, > Colin

Re: New release branch 3.9

Hi Josep, I marked this as a blocker. We will take a look. I also found some dependencies that need to be updated due to CVEs. See github.com/apache/kafka/pull/17436 best, Colin On Wed, Oct 9, 2024, at 05:52, Josep Prat wrote: > Hi Colin, > > I want to raise a bug we encountered while testing 3

Re: New release branch 3.9

Thanks Josep. I also agree that we should try to include this fix in 3.9.0. It is a regression that would cause the CPU resource to get wasted. On Wed, Oct 9, 2024 at 8:53 AM Josep Prat wrote: > > Hi Colin, > > I want to raise a bug we encountered while testing 3.9 RC0. You can find > the report

Re: New release branch 3.9

Hi Colin, I want to raise a bug we encountered while testing 3.9 RC0. You can find the report here: https://issues.apache.org/jira/browse/KAFKA-17751 Its current severity is "high", but IMO it might even be a blocker. What do you think? Best, On Fri, Oct 4, 2024 at 5:18 PM José Armando García Sa

Re: New release branch 3.9

Thanks Colin. KAFKA-16927 has been merged to trunk and the 3.9 branch. -- -José

Re: New release branch 3.9

Also, as a quick update, the PR for KAFKA-17608 has been merged to 3.9. KAFKA-16927 is the only current remaining blocker. best, Colin On Thu, Oct 3, 2024, at 12:49, Colin McCabe wrote: > Hi José, > > Yes, this seems like a regression in 3.9, so we need to fix it there. > Thanks for the heads u

Re: New release branch 3.9

Hi José, Yes, this seems like a regression in 3.9, so we need to fix it there. Thanks for the heads up. best, Colin On Thu, Oct 3, 2024, at 11:59, José Armando García Sancio wrote: > Hi all, > > We found a bug that should be fixed for 3.9.0: > https://issues.apache.org/jira/browse/KAFKA-16927 >

Re: New release branch 3.9

Hi all, We found a bug that should be fixed for 3.9.0: https://issues.apache.org/jira/browse/KAFKA-16927 I have created a PR to fix this issue: https://github.com/apache/kafka/pull/17363 Colin, can we include this in 3.9.0? Thanks, -- -José

Re: New release branch 3.9

Federico, thanks for the report. I also tried it locally and it looks like a regression for 3.9. I agree that this should be a blocker. -David On Fri, Sep 27, 2024 at 2:03 PM Colin McCabe wrote: > Hi Greg, > > I think new JDK support is a new feature rather than a bugfix. So we > wouldn't inclu

Re: New release branch 3.9

Hi Greg, I think new JDK support is a new feature rather than a bugfix. So we wouldn't include it in 3.9.x for that reason. It may be a compatible new feature, of course (most new features are...) but still a new feature. I'll comment more on the KIP-1006 thread... my main comment there is tha

Re: New release branch 3.9

Hello, I think I found a blocker, because the issue is related to a fairly common setup: https://issues.apache.org/jira/browse/KAFKA-17636 Let me know if you agree, or I'm missing something here. Thanks Fede On Thu, Sep 26, 2024 at 7:31 PM Greg Harris wrote: > > Hey Colin, > > KIP-1006 and the

Re: New release branch 3.9

Hi Colin, It has been brought to my attention that Java 23 is now GA, and Kafka clients, brokers, and connect are now experiencing UnsupportedOperationExceptions by default due our use of the deprecated-for-removal SecurityManager. This only happens upon upgrading to Java 23, so this is not a regr

Re: New release branch 3.9

Hey Colin, KIP-1006 and the associated vote are about removing support for SecurityManager, which is a user-facing breaking change. The PR is an internal-facing, backwards-compatible change that I motivated and described in the KIP as an interim solution, and doesn't require the vote to pass in or

Re: New release branch 3.9

Hi Greg, Thank you for working on this. Isn't this work part of KIP-1006? That KIP hasn't even been approved (although it seems very likely to be so). Certainly it isn't in 3.9. The PR is also kind of large with 16 files changed. I think supporting new JDK versions that we haven't supported bef

Re: New release branch 3.9

Hi all, I wanted to give a quick update on the 3.9.0 release. We had several fixes in the last few days (KAFKA-17459, KAFKA-17584, etc.) and uncovered two new blocker bugs which now have PRs available (KAFKA-17608, KAFKA-17604). Once those are in, I'll create a new RC. thanks, all. Colin On T

Re: New release branch 3.9

Hi Colin, We found a bug that we should fix for 3.9.0 (https://issues.apache.org/jira/browse/KAFKA-17608). Alyssa is going to work on the fix and we expect a PR soon. Thanks, -José

Re: New release branch 3.9

hi Colin The PR (https://github.com/apache/kafka/pull/17256) addresses the documentation issue. Since it’s a small patch, I’ve backported it directly to the 3.9 branch. Additionally, I noticed that the kafka_config.html file in the kafka-site 3.9 folder is empty. Is this expected? Best, Chia-P

Re: New release branch 3.9

hi Colin KAFKA-17459 has been fixed and backported to 3.9. Thanks for your patience! Best, Chia-Ping On 2024/09/24 00:23:59 Colin McCabe wrote: > Thanks Chia-Ping Tsai! Please do backport the test fix to the 3.9 branch if > we can get it in soon. (I don't think it's a blocker though...) > > be

Re: New release branch 3.9

Thanks Chia-Ping Tsai! Please do backport the test fix to the 3.9 branch if we can get it in soon. (I don't think it's a blocker though...) best, Colin On Sun, Sep 22, 2024, at 05:29, Chia-Ping Tsai wrote: > hi Colin > > The `reassign_partitions_test.py` is unstable in 3.9 on my local, and > ht

Re: New release branch 3.9

KAFKA-17584 looks like an issue with our handling of configuration synonyms. I have created a PR here. https://github.com/apache/kafka/pull/17258 I think we can get this into RC1 if we hurry. On a related note, now that 3.9 RC0 is out, please consider dropping JDK8 and removing ZK support as unb

Re: New release branch 3.9

hi Colin The `reassign_partitions_test.py` is unstable in 3.9 on my local, and https://issues.apache.org/jira/browse/KAFKA-17459 will stabilize it. The root cause is unrelated to production code so I will backport it to 3.9.0 only if 3.9.0 RC get obstructed by the `reassign_partitions_test.py`.

Re: New release branch 3.9

Hi Christo, Thanks for the bug report! It's a bit tricky to decide if this is a blocker or not since it apparently has been around for a long time (it's not new in 3.9, or even in 3.7, apparently...) I also don't have a clear idea of how long we'd have to delay the release to accommodate this f

Re: New release branch 3.9

Hello, I have filed https://issues.apache.org/jira/browse/KAFKA-17584 as a blocker. While it has not been introduced by a KIP, I think this has durability implications and needs to be addressed immediately. Let me know if you disagree! Best, Christo On Thu, 19 Sept 2024 at 16:01, José Armando G

Re: New release branch 3.9

Hi Colin, I have a minor improvement to the rendering of our documentation that we should include in 3.9: https://github.com/apache/kafka/pull/17235 Thanks -Jose

Re: New release branch 3.9

Hi Colin, The release notes (and the KAFKA-17543 JIRA) say this: [KAFKA-17543] - Enforce that broker.id.generation.enable is disabled when migrating to KRaft When I read that, it meant to me that the option "broker.id.generation.enable" needs to be disabled (i.e. set to false). Given this option

Re: New release branch 3.9

Hi Jakub, Can you say more about what you would like to see in the release notes? best, Colin On Wed, Sep 18, 2024, at 02:13, Jakub Scholz wrote: > Maybe you could have at least fixed the release notes which is what I was > suggesting :-(. > > On Wed, Sep 18, 2024 at 12:22 AM Colin McCabe wrot

Re: New release branch 3.9

Maybe you could have at least fixed the release notes which is what I was suggesting :-(. On Wed, Sep 18, 2024 at 12:22 AM Colin McCabe wrote: > Hi Chia-Ping Tsai, > > I've already pushed the RC0 to maven central, so we cannot include this > now. (I am waiting on some other release phases to co

Re: New release branch 3.9

Hi Chia-Ping Tsai, I've already pushed the RC0 to maven central, so we cannot include this now. (I am waiting on some other release phases to complete before I can announce the RC!) However, I suspect that there will be another RC, so don't abandon the PR just yet :) best, Colin On Tue, Se

Re: New release branch 3.9

hi Colin https://github.com/apache/kafka/pull/17210 tries to revise the error message of KAFKA-17543. I guess the 3.9 RC is in progress, so could you please take a look at the PR? If it is too trivial to be included, I think it can be excluded from trunk too since 4.0 will abandon the zk. Than

Re: New release branch 3.9

Thanks, everyone. It looks like the blockers list is empty now. I am running some ducktape tests and if they look good, will create a release candidate for 3.9.0 soon. regards, Colin On Wed, Sep 11, 2024, at 10:01, Matthias J. Sax wrote: > Hi Colin, > > we found another blocker bug: > https:/

Re: New release branch 3.9

Hi Colin, we found another blocker bug: https://issues.apache.org/jira/browse/KAFKA-17527 Working on a fix. -Matthias On 9/9/24 6:51 PM, David Arthur wrote: Colin, I found a race condition in the migration while investigating a flaky test. If encountered, the migration driver will get stu

Re: New release branch 3.9

Hi Colin, about KAFKA-17489, the bug Bruno mentioned. This needs to be fixed in 3.8 as well. The fix is probably small but tricky to get right - Bruno has attempted to fix it, but soaking revealed that the fix is not complete. Bruno is now out with Covid, so I will look into it. I'll update this t

Re: New release branch 3.9

hi Colin I raise a issue (https://issues.apache.org/jira/browse/KAFKA-17492) as 3.9 blocker, since the bug obstructs us from registering 3.9 broker to 3.8 controller Best, Chia-Ping On 2024/08/09 01:46:35 Colin McCabe wrote: > Hi all, > > I think it's time to transition the 3.9 branch to feat

Re: New release branch 3.9

Hi Colin, Unfortunately, we found a bug in Kafka Streams yesterday that make operating a Kafka Streams application challenging. The bug is described in the following ticket: https://issues.apache.org/jira/browse/KAFKA-17489 The bug happens when task fail due to consumption issues like Offs

Re: New release branch 3.9

On Mon, Sep 2, 2024, at 20:15, Luke Chen wrote: > Hi Colin, > > I've made KAFKA-17412 ( > PR ) as v3.9.0 blocker for > documenting the unclean leader election behavior change in KRaft mode. > This is jus

Re: New release branch 3.9

On Fri, Aug 30, 2024, at 11:53, Chia-Ping Tsai wrote: > hi Colin > > I open the https://issues.apache.org/jira/browse/KAFKA-17454 to be a > blocker for 3.9 since the e2e transactions_mixed_versions_test fail on > 3.9 definitely > > We will fix it tomorrow. > > Best, > Chia-Ping Thanks, Chia-Ping

Re: New release branch 3.9

Hi Colin, I've made KAFKA-17412 ( PR ) as v3.9.0 blocker for documenting the unclean leader election behavior change in KRaft mode. This is just a document change, so I think it should be fine. Let me

Re: New release branch 3.9

hi Colin I open the https://issues.apache.org/jira/browse/KAFKA-17454 to be a blocker for 3.9 since the e2e transactions_mixed_versions_test fail on 3.9 definitely We will fix it tomorrow. Best, Chia-Ping On 2024/08/30 15:38:48 Colin McCabe wrote: > No worries. Thanks for checking. > > best,

Re: New release branch 3.9

No worries. Thanks for checking. best, Colin On Thu, Aug 29, 2024, at 19:00, Kirk True wrote: > Thanks Chia-Ping! > > Sorry for the noise, everyone else :) > >> On Aug 29, 2024, at 6:36 PM, Chia-Ping Tsai wrote: >> >> hi Kirk >> >> I have updated the fix versions of KAFKA-17335 to include 3.9

Re: New release branch 3.9

Thanks Chia-Ping! Sorry for the noise, everyone else :) > On Aug 29, 2024, at 6:36 PM, Chia-Ping Tsai wrote: > > hi Kirk > > I have updated the fix versions of KAFKA-17335 to include 3.9 > > https://issues.apache.org/jira/browse/KAFKA-17335 > > Best, > Chia-Ping > > Chia-Ping Tsai 於 2024年8

Re: New release branch 3.9

hi Kirk I have updated the fix versions of KAFKA-17335 to include 3.9 https://issues.apache.org/jira/browse/KAFKA-17335 Best, Chia-Ping Chia-Ping Tsai 於 2024年8月30日 週五 上午9:32寫道： > hi Kirk > > KAFKA-17335 is already in 3.9 ( > https://github.com/apache/kafka/commit/a87b501a47a55a1f9038b6c52e31b

Re: New release branch 3.9

hi Kirk KAFKA-17335 is already in 3.9 ( https://github.com/apache/kafka/commit/a87b501a47a55a1f9038b6c52e31b71590c3a80a ) Best, Chia-Ping Kirk True 於 2024年8月30日 週五 上午4:36寫道： > Hi Colin, > > KAFKA-17335 (Lack of default for URL encoding configuration for OAuth > causes NPE) affects the internal

Re: New release branch 3.9

Hi Colin, KAFKA-17335 (Lack of default for URL encoding configuration for OAuth causes NPE) affects the internal use of the OAuth-based AuthenticateCallbackHandler. Can we back port the fix (https://github.com/apache/kafka/pull/16990) to the 3.9 branch? Thanks, Kirk > On Aug 29, 2024, at 11:2

Re: New release branch 3.9

Hi all, Code freeze has officially arrived for Apache Kafka 3.9! If you have additional fixes to get into the branch at this point, please ping me first (unless it's already marked as a blocker in JIRA). I did a first pass on the list of open JIRAs for 3.9, and moved out any that were not bloc

Re: New release branch 3.9

I wanted to give a quick update on 3.9. Code freeze is coming up next Thursday on the 29th. As usual, after that point, only critical bug fixes will be accepted. Thanks again to everyone who has helped with this release. best, Colin On Fri, Aug 23, 2024, at 13:18, Colin McCabe wrote: > Thanks

Re: New release branch 3.9

Thanks for the heads up, Josep. I saw both emails but I didn't make the connection until now. It does seem likely that we'll have to modify this (either for 3.9... or soon.) best, Colin On Tue, Aug 13, 2024, at 05:09, Josep Prat wrote: > Hi Colin, > > Just to make sure you (as a Release Manager

Re: New release branch 3.9

Hi Colin, Just to make sure you (as a Release Manager) are aware of the change. ASF Infra just communicated the removal of the home.apache.org machines (in 4 weeks they will be gone). This means the release.py script wouldn't work if executed after that date and would need to be modified to store

Re: New release branch 3.9

Updates: KIP-1007: I have removed this PR from the Apache Kafka 3.9 release plan. Since the KIP was discarded, I did not add it in the "postponed to subsequent release" section. KIP-1025: Marked 3.9 status as Done KIP-1023: Postponed to subsequent release KIP-1005: Marked 3.9 status as Done

Re: New release branch 3.9

Hi Chia-Ping Tsai, Thank you! And thanks for your own contributions, especially the many code reviews (not only of my PRs, but everyone's). best, Colin On Thu, Aug 8, 2024, at 19:14, Chia-Ping Tsai wrote: >> - We have completed all the feature work for KIP-853: KRaft controller >> membership c

Re: New release branch 3.9

> - We have completed all the feature work for KIP-853: KRaft controller > membership changes. (Please note that there are still a few bug fixes > remaining, and the docs JIRA, KAFKA-17048, but those are all > post-feature-freeze tasks.) Sorry to make meaningless reply on this mail thread, but

Re: New release branch 3.9

Hi all, I think it's time to transition the 3.9 branch to feature freeze. Please note that this is 2 weeks past the original planned date. I apologize for this; our planning wasn't perfect. A few updates on features that are in or out of Apache Kafka 3.9: - We have completed all the feature wo

Re: New release branch 3.9

On Wed, Jul 31, 2024 at 12:28 AM Ismael Juma wrote: > I would recommend against large refactorings in trunk until the first RC > for 3.9 - that will reduce cherry-pick friction. Once we have the first RC, > subsequent changes to 3.9 should be limited in scope. > I agree. We should specially dela

Re: New release branch 3.9

Jakub, Yes but that can be done after code freeze. It needs to get done before RC and the announcement email. Thanks, On Thu, Aug 1, 2024 at 3:43 PM Jakub Scholz wrote: > Surely "Document how to use KIP-853" ( > https://issues.apache.org/jira/browse/KAFKA-17048) should be required for > the re

Re: New release branch 3.9

Hi Josep, I don't think that all of the metrics are required to operate a kraft cluster. The KIP documents at different points which metrics should be monitored by the operator. I'll make that clear in the jira and we can implement those in 3.9.1. Thanks On Thu, Aug 1, 2024 at 3:29 PM Josep Pra

Re: New release branch 3.9

Surely "Document how to use KIP-853" ( https://issues.apache.org/jira/browse/KAFKA-17048) should be required for the release, or? Why bother with the KIP and the release if you don't tell the users how to use it? Jakub On Thu, Aug 1, 2024 at 8:40 PM Colin McCabe wrote: > Hi Mickael, > > KAFKA-1

Re: New release branch 3.9

Hi Colin, Looking at the JIRAs of the new umbrella issue ( https://issues.apache.org/jira/browse/KAFKA-17241) it seems to me that the adding metrics one is the only one that is different. As you mention most of the tasks are refactors, optimizations and tests. However, having proper metrics I thin

Re: New release branch 3.9

Hi all, I've moved the optional and follow-on JIRAs for KIP-853 (many of which were "refactors," "optimizations", "tests", etc.) to KAFKA-17241 to hopefully clear up the confusion a bit. I think a lot of these would be good newbie JIRAs (although probably not the "refactor" ones :) As I said,

Re: New release branch 3.9

Hi Josep, I don't have a strong opinion on whether KAFKA-16524 should land in 3.9.1. Let's discuss that more on the mailing list when it's time for 3.9.1. best, Colin On Thu, Aug 1, 2024, at 12:07, Josep Prat wrote: > Hi Colin, > Will JIRAs like adding metrics ( > https://issues.apache.org/jir

Re: New release branch 3.9

Hi Colin, Will JIRAs like adding metrics ( https://issues.apache.org/jira/browse/KAFKA-16524) make it in patch version of 3.9? Best, On Thu, Aug 1, 2024 at 8:49 PM Mickael Maison wrote: > Hi Colin, > > Thanks for the clarification. This makes much more sense now. > > Mickael > > On Thu, Aug 1,

Re: New release branch 3.9

Hi Colin, Thanks for the clarification. This makes much more sense now. Mickael On Thu, Aug 1, 2024 at 8:43 PM Colin McCabe wrote: > > Hi Chris, > > I don't see why this shouldn't go to 3.9. Would you call this a bugfix? > > best, > Colin > > > On Wed, Jul 31, 2024, at 13:54, Chris Egerton wrot

Re: New release branch 3.9

Hi Chris, I don't see why this shouldn't go to 3.9. Would you call this a bugfix? best, Colin On Wed, Jul 31, 2024, at 13:54, Chris Egerton wrote: > Hi Colin, > > Would it be alright if I cherry-picked > https://github.com/apache/kafka/pull/16678 onto 3.9? This isn't a > regression but it's a l

Re: New release branch 3.9

Hi Mickael, KAFKA-14094 is basically a long list of things that we might want to do at some time in the future, that are related to KIP-853. They are certainly not all required for Kafka 3.9. Sorry that this was confusing. In order to avoid confusion about this in the future, I'll move the stu

Re: New release branch 3.9

Hi, Considering KIP-853 does not look like it's near completion (20 out of 49 tasks done in https://issues.apache.org/jira/browse/KAFKA-14094), I'm not sure I understand why we decided to cut the 3.9 branch this early. By waiting a bit longer we could have reduced the risks in case KIP-853 is furt

Re: New release branch 3.9

Hi Colin, Would it be alright if I cherry-picked https://github.com/apache/kafka/pull/16678 onto 3.9? This isn't a regression but it's a low-risk fix that I'd like to get into the next release if possible. Cheers, Chris On Wed, Jul 31, 2024 at 12:29 AM Ismael Juma wrote: > I would recommend a

Re: New release branch 3.9

I would recommend against large refactorings in trunk until the first RC for 3.9 - that will reduce cherry-pick friction. Once we have the first RC, subsequent changes to 3.9 should be limited in scope. Ismael On Tue, Jul 30, 2024 at 4:31 PM Colin McCabe wrote: > Yeah, please go ahead. I know a

Re: New release branch 3.9

Hi Colin and all, If KIP-853 can complete in v3.9.0 in time (or a little delay), I agree we should try to keep v3.9.0 as the last release before v4.0. This way, it will let all Kafka ecosystem projects have a clear (and certain) picture about what will happen in Apache Kafka. Hi Colin, For KIP-95

Re: New release branch 3.9

Yeah, please go ahead. I know a lot of people are waiting for 4.0. best, Colin On Tue, Jul 30, 2024, at 16:05, Matthias J. Sax wrote: > Thanks for clarifying Colin. So my assumptions were actually correct. > > We have a lot of contributors waiting to pick-up 4.0 tickets, and I'll > go ahead a t

Re: New release branch 3.9

Thanks for clarifying Colin. So my assumptions were actually correct. We have a lot of contributors waiting to pick-up 4.0 tickets, and I'll go ahead a tell them that we are ready and they can start to pick them up. Thanks. -Matthias On 7/30/24 3:51 PM, Colin McCabe wrote: Hi Chia-Ping Tsa

Re: New release branch 3.9

Hi Igor, Correct. The whole point of 3.9 is to complete KIP-853. We had many email threads on this :) As release manager I have discretion to delay the release until this is complete. And I will do that. But I do not think the delay will be more than a few days, based on what we're looking at

Re: New release branch 3.9

Hi Chia-Ping Tsai, If you can get them done this week then I think we can merge them in to 3.9. If not, then let's wait until 4.0, please. best, Colin On Tue, Jul 30, 2024, at 09:07, Chia-Ping Tsai wrote: > hi Colin, > > Could you please consider adding > https://issues.apache.org/jira/browse/

Re: New release branch 3.9

On Tue, Jul 30, 2024, at 15:22, Matthias J. Sax wrote: > Thanks Greg. Overall, this makes sense to me. > > The only assumption on my side was, that we are actually pretty sure > that we will hit case (1) or (2)... > > And I actually also thought, that completing the required KRaft work > would on

Re: New release branch 3.9

On Tue, Jul 30, 2024, at 15:35, Greg Harris wrote: > Hi Matthias, > > I agree with you. > >> The only assumption on my side was, that we are actually pretty sure >> that we will hit case (1) or (2)... > > I want this to be the case, but we were pretty sure that KIP-853 was going > to be in 3.8 up u

Re: New release branch 3.9

On Tue, Jul 30, 2024, at 09:52, Matthias J. Sax wrote: > Thanks for cutting the release branch. > > It's great to see `trunk` being bumped to 4.0-SNAPSHOT, and I wanted to > follow up on this: > > We have a bunch of tickets that we can only ship with 4.0 release, and > these tickets were blocked

Re: New release branch 3.9

On Tue, Jul 30, 2024, at 08:59, José Armando García Sancio wrote: > Thanks Colin. > > For KIP-853 (KRaft Controller Membership Changes), we still have the > following features that are in progress. > > 1. UpdateVoter RPC and request handling > > 2

Re: New release branch 3.9

Hi all, KIP-853 is shipping in 3.9. If we have to delay 3.9 to accomplish this, we will, but that seems very unlikely at this point. We are mostly on schedule so far. Trunk is 4.0. best, Colin On Tue, Jul 30, 2024, at 15:35, Greg Harris wrote: > Hi Matthias, > > I agree with you. > >> The on

Re: New release branch 3.9

Hi Matthias, I agree with you. > The only assumption on my side was, that we are actually pretty sure > that we will hit case (1) or (2)... I want this to be the case, but we were pretty sure that KIP-853 was going to be in 3.8 up until it wasn't ready. I believe we need to plan for the worst ca

Re: New release branch 3.9

Thanks Greg. Overall, this makes sense to me. The only assumption on my side was, that we are actually pretty sure that we will hit case (1) or (2)... And I actually also thought, that completing the required KRaft work would only take a few more weeks, and that is also why we have a 3.9 rel

Re: New release branch 3.9

Hi all, I'd like to clarify my understanding of the path forward, the one I voted for in KIP-1012 and what I understood to be the consensus in the 3.8.0 release thread. 1. If KIP-853 is feature-complete before October, Kafka 3.9 can be released ASAP with KIP-853. There will be no 3.10 release, an

Re: New release branch 3.9

My understanding was that the reason for the shorter cycle to the 3.9 release was based on the assumption that KIP-1012 would be ready soon, so we could get to 4.0 quicker. If we can't move to 4.0 sooner, what's to gain with an early 3.9? -- Igor

Re: New release branch 3.9

Hi Matthias, Note that is KIP-853 the one with the feature parity with ZK. KIP-1012 was the one were we agreed to stay on 3.x until feature parity. The reason to have a 3.10 is to have a safe way to upgrade to KRaft Kafkas while ZK is still around. We try to explain this in KIP-1012 --

Re: New release branch 3.9

Thanks for the input. However, I am wondering if releasing 3.9 makes sense if KIP-1012 won't make it? My understanding was we do 3.9 only to not delay 3.8 and not delay 4.0. If we would go with a 3.10, would it also be an "intermediate" release like 3.9? Or would it replace 4.0? For the first

Re: New release branch 3.9

One option is to just have a separate 4.0 branch for development to not block work on new features. With Apache Accumulo we have a similar situation where we have a separate branch (ironically also 4.0) that we are calling "elasticity" that is a long running br

Re: New release branch 3.9

+1 Greg. I'd be really happy to bump trunk to 4.0.0, but only once we know we can safely do so. On Tue, Jul 30, 2024 at 7:24 PM Greg Harris wrote: > Hi all, > > I agree that we are not yet ready for breaking changes on trunk, so I > opened a PR to bump to 3.10.0-SNAPSHOT: > https://github.com/ap

Re: New release branch 3.9

Hi all, I agree that we are not yet ready for breaking changes on trunk, so I opened a PR to bump to 3.10.0-SNAPSHOT: https://github.com/apache/kafka/pull/16732 When KIP-853 is feature complete, we can bump to 4.0.0-SNAPSHOT. Thanks, Greg On Tue, Jul 30, 2024 at 10:01 AM Josep Prat wrote: > H

Re: New release branch 3.9

Hi all, As per KIP-1012[1] we can't yet say if the next release will be 3.10.0 or 4.0.0. It will come down to the state of KIP-853 in 3.9.0. So, in my opinion we should still wait before committing breaking changes on trunk until we know for sure that KIP-853 will make it. Maybe Jose can share mor

Re: New release branch 3.9

Thanks for cutting the release branch. It's great to see `trunk` being bumped to 4.0-SNAPSHOT, and I wanted to follow up on this: We have a bunch of tickets that we can only ship with 4.0 release, and these tickets were blocked so far. I wanted to get confirmation that we will stick with 4.0

Re: New release branch 3.9

hi Colin, Could you please consider adding https://issues.apache.org/jira/browse/KAFKA-1 to 3.9.0 The issue is used to deprecate the formatters in core module. Also, it implements the replacements for them. In order to follow the deprecation rules, it would be nice to have KAFKA-1 in 3.9

Re: New release branch 3.9

Thanks Colin. For KIP-853 (KRaft Controller Membership Changes), we still have the following features that are in progress. 1. UpdateVoter RPC and request handling 2. Storage tool changes for KIP-853