+1 binding. I have checked signatures, given the javadocs a quick look, followed the quickstart for KRaft and run the tests.
Thanks Chris for running the release. Tom On Mon, 9 Jan 2023 at 15:29, Chris Egerton <chr...@aiven.io.invalid> wrote: > Hi all, > > Thanks to everyone who has tested and voted for the release so far! Since > we only have two binding votes so far, I'll be keeping the vote thread open > until we either discover a blocker that requires a new release candidate to > be generated, or get a third binding vote. > > For anyone following along, it may appear that there have already been > three binding votes, but Satish's vote is actually non-binding since he is > a committer, but not on the PMC (see the "Product Release" action in the > project bylaws [1]). We've already clarified this offline and I'm only > reiterating here to help prevent any confusion over the number of binding > votes that have been cast. And either way--thank you for testing out the > release, Satish! > > Cheers, > > Chris > > [1] - > https://cwiki.apache.org/confluence/display/KAFKA/Bylaws#Bylaws-Actions > > On Thu, Jan 5, 2023 at 9:45 AM Mickael Maison <mickael.mai...@gmail.com> > wrote: > > > +1 binding > > > > - Checked signatures > > - Ran quickstart with Scala 2.13 binaries > > - Ran unit and integration tests > > > > Thanks Chris for running this release > > > > > > On Wed, Jan 4, 2023 at 11:37 AM Satish Duggana <satish.dugg...@gmail.com > > > > wrote: > > > > > > Hi Chris, > > > Thanks for running the release. > > > > > > +1 (binding) > > > > > > - Verified signatures and artifacts > > > - Ran testAll/releaseTarGzAll successfully with no failures. > > > - Ran through quickstart of core/streams on builds generated from the > > tag. > > > - Ran a few internal apps targeting to topics on 3 node cluster. > > > > > > On Wed, 4 Jan 2023 at 00:49, Manikumar <manikumar.re...@gmail.com> > > wrote: > > > > > > > > Hi Chris, > > > > > > > > +1 (binding) > > > > > > > > - verified the signatures, artifacts > > > > - ran the tests on the source archive > > > > - verified the quickstarts > > > > > > > > Thanks for running the release! > > > > > > > > Thanks, > > > > Manikumar > > > > > > > > > > > > On Fri, Dec 23, 2022 at 4:44 PM Federico Valeri < > fedeval...@gmail.com> > > wrote: > > > > > > > > > > Hi, I did the following to validate the release: > > > > > > > > > > - Checksums and signatures ok > > > > > - Build from source using Java 17 and Scala 2.13 ok > > > > > - Unit and integration tests ok > > > > > - Quickstart in both ZK and KRaft modes ok > > > > > - Test app with staging Maven artifacts ok > > > > > > > > > > +1 (non binding) > > > > > > > > > > Thanks > > > > > Fede > > > > > > > > > > On Wed, Dec 21, 2022 at 11:21 PM Chris Egerton > > <chr...@aiven.io.invalid> wrote: > > > > > > > > > > > > Hello Kafka users, developers and client-developers, > > > > > > > > > > > > This is the second candidate for release of Apache Kafka 3.3.2. > > > > > > > > > > > > This is a bugfix release with several fixes since the release of > > 3.3.1. A > > > > > > few of the major issues include: > > > > > > > > > > > > * KAFKA-14358 Users should not be able to create a regular topic > > name > > > > > > __cluster_metadata > > > > > > KAFKA-14379 Consumer should refresh preferred read replica on > > update > > > > > > metadata > > > > > > * KAFKA-13586 Prevent exception thrown during connector update > from > > > > > > crashing distributed herder > > > > > > > > > > > > > > > > > > Release notes for the 3.3.2 release: > > > > > > > > https://home.apache.org/~cegerton/kafka-3.3.2-rc1/RELEASE_NOTES.html > > > > > > > > > > > > *** Please download, test and vote by Friday, January 6, 2023, > > 10pm UTC > > > > > > (this date is chosen to accommodate the various upcoming holidays > > that > > > > > > members of the community will be taking and give everyone enough > > time to > > > > > > test out the release candidate, without unduly delaying the > > release) > > > > > > > > > > > > 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/~cegerton/kafka-3.3.2-rc1/ > > > > > > > > > > > > * Maven artifacts to be voted upon: > > > > > > > > https://repository.apache.org/content/groups/staging/org/apache/kafka/ > > > > > > > > > > > > * Javadoc: > > > > > > https://home.apache.org/~cegerton/kafka-3.3.2-rc1/javadoc/ > > > > > > > > > > > > * Tag to be voted upon (off 3.3 branch) is the 3.3.2 tag: > > > > > > https://github.com/apache/kafka/releases/tag/3.3.2-rc1 > > > > > > > > > > > > * Documentation: > > > > > > https://kafka.apache.org/33/documentation.html > > > > > > > > > > > > * Protocol: > > > > > > https://kafka.apache.org/33/protocol.html > > > > > > > > > > > > The most recent build has had test failures. These all appear to > > be due to > > > > > > flakiness, but it would be nice if someone more familiar with the > > failed > > > > > > tests could confirm this. I may update this thread with passing > > build links > > > > > > if I can get one, or start a new release vote thread if test > > failures must > > > > > > be addressed beyond re-running builds until they pass. > > > > > > > > > > > > Unit/integration tests: > > > > > > > > https://ci-builds.apache.org/job/Kafka/job/kafka/job/3.3/142/testReport/ > > > > > > > > > > > > José, would it be possible to re-run the system tests for 3.3 on > > the latest > > > > > > commit for 3.3 (e3212f2), and share the results on this thread? > > > > > > > > > > > > Cheers, > > > > > > > > > > > > Chris > > >
