Hi David,
I did the following:
1. Checked the signatures and checksums of all the release artifacts
2. Built from source
3. Ran the unit tests (encountered the same error pointed out by others
before)
4. Ran the quickstart with the downloaded code
5. Ran the Kafka Streams quickstart against
1. AK
2. Docker AK 4.0 image
3. Docker AK-Native 4.0 image
6. Spot checked the javadoc
7. Spot checked the documentation
+1(binding)
Thanks,
Bill
On Thu, Mar 13, 2025 at 11:32 AM José Armando García Sancio
<jsan...@confluent.io.invalid> wrote:
> Hi Luke and David,
>
> On Thu, Mar 13, 2025 at 8:27 AM Luke Chen <show...@gmail.com> wrote:
> >
> > Hi David and all,
> >
> > Sorry, I found a bug KAFKA-18979, and in my opinion, it should be a
> blocker. But I'd like to get @José Armando García Sancio 's confirmation.
>
> This is an unfortunate bug that can cause confusion to the user but I
> don't think it should be a blocker for the 4.0.0 release for two
> reasons. The same issue should be present in 3.9 so it is not a
> regression. I would argue that this is a UI issue.
>
> I am planning to fix this inconsistency in my PR for KAFKA-16538. That
> PR will support upgrades of the kraft.version and fix any
> FeatureLevelRecord that were incorrectly added to the cluster metadata
> log because of this issue.
>
> What do you think?
> -Jose
>
