+1 (non-binding). I used the Scala 2.13 binaries and staged Maven artifacts
and ran various tests with them. Thanks for doing the release.

Jakub

On Fri, Apr 29, 2022 at 8:16 PM Mickael Maison <mimai...@apache.org> wrote:

> Hi Tom,
>
> Thanks for running this release!
>
> I've done the following:
> - Checked signatures and checksums
> - Checked javadocs/maven artifacts
> - Built from source and run all tests with Java 11
> - Ran quickstart on Scala 2.13 artifact with Java 11
>
> It looks like the website has not been updated yet, I still only see
> 3.1.0. When you'll add 3.1.1, let's make sure we mention reload4j in
> the notable changes section.
>
> +1 (binding)
>
> Thanks,
> Mickael
>
>
>
> On Fri, Apr 29, 2022 at 11:12 AM Tom Bentley <tbent...@redhat.com> wrote:
> >
> > Hello Kafka users, developers and client-developers,
> >
> > This is the first candidate for release of Apache Kafka 3.1.1.
> >
> > Apache Kafka 3.1.1 is a bugfix release and 30 issues have been fixed
> > since 3.1.0.
> >
> > Release notes for the 3.1.1 release:
> > https://home.apache.org/~tombentley/kafka-3.1.1-rc1/RELEASE_NOTES.html
> >
> > *** Please download, test and vote by 09:00 UTC, Friday 6th May
> >
> > 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/~tombentley/kafka-3.1.1-rc1/
> >
> > * Maven artifacts to be voted upon:
> > https://repository.apache.org/content/groups/staging/org/apache/kafka/
> >
> > * Javadoc:
> > https://home.apache.org/~tombentley/kafka-3.1.1-rc1/javadoc/
> >
> > * Tag to be voted upon (off 3.1 branch) is the 3.1.1 tag:
> > https://github.com/apache/kafka/releases/tag/3.1.1-rc1
> >
> > * Documentation:
> > https://kafka.apache.org/31/documentation.html
> >
> > * Protocol:
> > https://kafka.apache.org/31/protocol.html
> >
> > * Successful Jenkins builds for the 3.1 branch:
> > I will share a link one the build is complete.
> >
> > /**************************************
> >
> > Thanks,
> > Tom
>

Reply via email to