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, and 4.0 will follow 4 months after 3.9, no later than February. 2. If KIP-853 is feature complete in October, Kafka 3.9 should be released in October as a normal release, with KIP-853. There will be no 3.10 release, and 4.0 will follow 4 months after 3.9, in February. 3. If KIP-853 is not feature complete in October, Kafka 3.9 should be released in October as a normal release, without KIP-853. There will be a 3.10 release that may or may not contain KIP-853 no later than February. As we are not sure which path will be taken, the most conservative strategy is to bump to 3.10, and only after we know we're in case 1 or 2, bump the version to 4.0 and skip 3.10. If we leave the version bump to 4.0 in place, and later discover that we are in case 3, it will be very damaging for the project, causing either a big release delay, confusion for users, or unaddressed bugs. Thanks, Greg On Tue, Jul 30, 2024 at 2:14 PM Igor Soarez <i...@soarez.me> wrote: > 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 >
