Hi Luke,

I ran the following checks:
- Verified signatures and checksums
- Ran the KRaft and ZooKeeper quickstarts with the 2.13 binaries
- Built sources and ran unit/integration tests with Java 17

+1 (binding)

Thanks,
Mickael


On Fri, Nov 24, 2023 at 10:41 AM Jakub Scholz <ja...@scholz.cz> wrote:
>
> +1 non-binding. I used the staged Scala 2.13 binaries and the staged Maven
> repo to run my tests and all seems to work fine.
>
> Thanks & Regards
> Jakub
>
> On Tue, Nov 21, 2023 at 11:09 AM Luke Chen <show...@apache.org> wrote:
>
> > Hello Kafka users, developers and client-developers,
> >
> > This is the first candidate for release of Apache Kafka 3.5.2.
> >
> > This is a bugfix release with several fixes since the release of 3.5.1,
> > including dependency version bumps for CVEs.
> >
> > Release notes for the 3.5.2 release:
> > https://home.apache.org/~showuon/kafka-3.5.2-rc1/RELEASE_NOTES.html
> >
> > *** Please download, test and vote by Nov. 28.
> >
> > Kafka's KEYS file containing PGP keys we use to sign the release:
> > https://kafka.apache.org/KEYS
> >
> > * Release artifacts to be voted upon (source and binary):
> > https://home.apache.org/~showuon/kafka-3.5.2-rc1/
> >
> > * Maven artifacts to be voted upon:
> > https://repository.apache.org/content/groups/staging/org/apache/kafka/
> >
> > * Javadoc:
> > https://home.apache.org/~showuon/kafka-3.5.2-rc1/javadoc/
> >
> > * Tag to be voted upon (off 3.5 branch) is the 3.5.2 tag:
> > https://github.com/apache/kafka/releases/tag/3.5.2-rc1
> >
> > * Documentation:
> > https://kafka.apache.org/35/documentation.html
> >
> > * Protocol:
> > https://kafka.apache.org/35/protocol.html
> >
> > * Successful Jenkins builds for the 3.5 branch:
> > Unit/integration tests:
> > https://ci-builds.apache.org/job/Kafka/job/kafka/job/3.5/98/
> > There are some falky tests, including the testSingleIP test failure. It
> > failed because of some infra change and we fixed it
> > <https://github.com/apache/kafka/pull/14741> recently.
> >
> > System tests: running, will update the results later.
> >
> >
> >
> > Thank you.
> > Luke
> >

Reply via email to