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 > 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`. Otherwise, I will backport it to 3.9.1 > > Best, > Chia-Ping > > On 2024/08/23 20:18:23 Colin McCabe wrote: >> 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) 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 RC >> > artifacts under dist.apache.org/dev instead. >> > >> > Best, >> > >> > On Fri, Aug 9, 2024 at 11:38 PM Colin McCabe <cmcc...@apache.org> wrote: >> > >> >> 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 >> >> >> >> KIP-996: Postponed to subsequent release >> >> >> >> KIP-994: Postponed to subsequent release >> >> >> >> KIP-997: Postponed to subsequent release >> >> >> >> KIP-966: Postponed to subsequent release >> >> >> >> KIP-956: Postponed to subsequent release >> >> >> >> KIP-950: Marked 3.9 status as Done >> >> >> >> best, >> >> Colin >> >> >> >> On Fri, Aug 9, 2024, at 14:13, Colin McCabe wrote: >> >> > 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 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 big thanks to >> >> >> Colin, Jose, and other contributors to ship KIP-853 to 3.9! >> >> >> >> >> >> Best, >> >> >> Chia-Ping >> >> >> >> >> >> >> >> >>> >> >> >>> Colin McCabe <cmcc...@apache.org> 於 2024年8月9日 上午9:47 寫道： >> >> >>> >> >> >>> 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 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.) >> >> >>> >> >> >>> - After speaking with Calvin, I moved KIP-966 out of 3.9 and into 4.0. >> >> I do feel bad about this but I just don't think we'll be able to get it >> >> into this short release. >> >> >>> >> >> >>> There are a few other KIPs that probably need to be moved to 4.0, such >> >> as KIP-1023 and KIP-1025. I will do a more thorough review tomorrow and >> >> reach out to people if there are gray areas. If you have a feature that >> >> you >> >> have questions about, please reach out. >> >> >>> >> >> >>> I would like to extend code freeze for Kafka 3.9 to August 29th. My >> >> reasoning is that code freeze was 2 weeks later than expected, and also, I >> >> will be out of the office most of next week. >> >> >>> >> >> >>> I have also created a PR to mark 3.9-IV0 as stable, so look for that >> >> shortly in trunk and 3.9. >> >> >>> >> >> >>> As previously mentioned, please refrain from changing the Java version >> >> in trunk (kafka 4.0) until we get an RC out. (However, please do continue >> >> working on your 4.0 features and other refactors in trunk, even if they >> >> don't apply to 3.9!) >> >> >>> >> >> >>> Thanks to everyone who has worked on this release, and thanks for your >> >> patience. I do believe we will deliver on the promise of a >> >> much-shorter-than-usual release cycle, even with the 2 week delay. >> >> >>> >> >> >>> best, >> >> >>> Colin >> >> >> > >> > >> > -- >> > [image: Aiven] <https://www.aiven.io> >> > >> > *Josep Prat* >> > Open Source Engineering Director, *Aiven* >> > josep.p...@aiven.io | +491715557497 >> > aiven.io <https://www.aiven.io> | <https://www.facebook.com/aivencloud> >> > <https://www.linkedin.com/company/aiven/> >> > <https://twitter.com/aiven_io> >> > *Aiven Deutschland GmbH* >> > Alexanderufer 3-7, 10117 Berlin >> > Geschäftsführer: Oskari Saarenmaa, Hannu Valtonen, >> > Anna Richardson, Kenneth Chen >> > Amtsgericht Charlottenburg, HRB 209739 B >>
