+1 (binding)
I checked the signatures/checksums, built from source and ran tests,
and ran the quickstart with the 2.13 binaries.

Thanks José and David for running this release

On Mon, Sep 26, 2022 at 11:07 PM David Arthur <davidart...@apache.org> wrote:
>
> Thanks for the votes, everyone!
>
> Here is the best recent run of the system tests on 3.3
> http://confluent-kafka-system-test-results.s3-us-west-2.amazonaws.com/3.3/2022-09-24--001.system-test-kafka-3.3--1664037736--confluentinc--3.3--b084e9068c/report.html.
> I'm currently re-running the failed tests to confirm that they are
> merely flaky and not broken. One exception is the failing delegation
> token test that is consistently failing. This appears to be an issue
> with the test itself due to changes in the command output introduced
> recently.
>
> Similarly, the unit/integration tests are mostly passing, with some
> flaky failures. Here is a recent run that has two out of three jobs
> passing https://ci-builds.apache.org/job/Kafka/job/kafka/job/3.3/86/.
>
> Once I verify the system tests are good, I'll update this thread and
> close out the vote.
>
> Thanks!
> David
>
>
> On Mon, Sep 26, 2022 at 2:24 PM Ismael Juma <ism...@juma.me.uk> wrote:
> >
> > +1 provided that the system test results are good. Can you please post them
> > along with the JUnit test results (these seem ok although there are some
> > flakes)?
> >
> > I tested the kraft quick start with the Scala 2.13 binary and ran the tests
> > on the source release. I noticed a non-blocker issue with the KRaft readme
> > and submitted a PR:
> >
> > https://github.com/apache/kafka/pull/12688
> >
> > Ismael
> >
> > On Tue, Sep 20, 2022 at 4:17 PM David Arthur <davidart...@apache.org> wrote:
> >
> > > Hello Kafka users, developers and client-developers,
> > >
> > > This is the second release candidate for Apache Kafka 3.3.0. Many new
> > > features and bug fixes are included in this major release of Kafka. A
> > > significant number of the issues in this release are related to KRaft,
> > > which will be considered "production ready" as part of this release
> > > (KIP-833)
> > >
> > > KRaft improvements:
> > > * KIP-778: Online KRaft to KRaft Upgrades
> > > * KIP-833: Mark KRaft as Production Ready
> > > * KIP-835: Monitor Quorum health (many new KRaft metrics)
> > > * KIP-836: Expose voter lag via kafka-metadata-quorum.sh
> > > * KIP-841: Fenced replicas should not be allowed to join the ISR in KRaft
> > > * KIP-859: Add Metadata Log Processing Error Related Metrics
> > >
> > > Other major improvements include:
> > > * KIP-618: Exactly-Once Support for Source Connectors
> > > * KIP-831: Add metric for log recovery progress
> > > * KIP-827: Expose logdirs total and usable space via Kafka API
> > > * KIP-834: Add ability to Pause / Resume KafkaStreams Topologies
> > >
> > > The full release notes are available here:
> > > https://home.apache.org/~davidarthur/kafka-3.3.0-rc2/RELEASE_NOTES.html
> > >
> > > Please download, test and vote by Monday, Sep 26 at 5pm EDT
> > >
> > > Also, huge thanks to José for running the release so far. He has done
> > > the vast majority of the work to prepare this rather large 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/~davidarthur/kafka-3.3.0-rc2/
> > >
> > > * Maven artifacts to be voted upon:
> > > https://repository.apache.org/content/groups/staging/org/apache/kafka/
> > >
> > > * Javadoc: https://home.apache.org/~davidarthur/kafka-3.3.0-rc2/javadoc/
> > >
> > > * Tag to be voted upon (off 3.3 branch) is the 3.3.0 tag:
> > > https://github.com/apache/kafka/releases/tag/3.3.0-rc2
> > >
> > > * Documentation:  https://kafka.apache.org/33/documentation.html
> > >
> > > * Protocol: https://kafka.apache.org/33/protocol.html
> > >
> > >
> > >
> > >
> > > Successful Jenkins builds to follow in a future update to this email.
> > >
> > >
> > > Thanks!
> > > David Arthur
> > >

Reply via email to