Hi Tom,

I merged and cherry-picked the fix.

Ismael

On Thu, Apr 28, 2022 at 12:33 AM Tom Bentley <tbent...@redhat.com> wrote:

> Hi Dongjoon,
>
> I apologise, I should have been a bit more communicative. I was waiting for
> a better fix to the issue previously highlighted by David. Ismael has
> kindly provided a patch [1], so I will roll RC1 once this is merged and
> cherry-picked.
>
> Kind regards,
>
> Tom
>
> [1]: https://github.com/apache/kafka/pull/12096
>
>
> On Thu, 28 Apr 2022 at 04:38, Luke Chen <show...@gmail.com> wrote:
>
> > Hi Dongjoon,
> >
> > The Apache Kafka community doesn't recommend users to use which version
> of
> > Kafka.
> > The 2 releases v3.1.1 and v3.2.0 are running in parallel, and we don't
> > guarantee which version will be released earlier.
> >
> > Thank you.
> > Luke
> >
> >
> >
> >
> > On Thu, Apr 28, 2022 at 4:54 AM Dongjoon Hyun <dongj...@apache.org>
> wrote:
> >
> > > Hi, All.
> > >
> > > It seems that Apache Kafka 3.2.0 RC0 vote started already instead of
> > > Apache Kafka 3.1.1 release.
> > >
> > > Does Apache Kafka community recommend to use Apache Kafka 3.2.0 instead
> > of
> > > Apache Kafka 3.1.1?
> > >
> > > Dongjoon.
> > >
> > > On 2022/04/14 01:00:40 Ismael Juma wrote:
> > > > I added a comment to that PR. Let's figure out if we need an
> additional
> > > > change before doing the next RC.
> > > >
> > > > Ismael
> > > >
> > > > On Tue, Apr 12, 2022 at 7:47 PM Luke Chen <show...@gmail.com> wrote:
> > > >
> > > > > Thanks for pointing that out, David.
> > > > > +1 to include this PR since we've already included the first fix
> for
> > > > > KAFKA-13794, and this is a follow up fix for it.
> > > > >
> > > > > Thank you.
> > > > > Luke
> > > > >
> > > > > On Wed, Apr 13, 2022 at 2:31 AM David Jacot
> > > <dja...@confluent.io.invalid>
> > > > > wrote:
> > > > >
> > > > > > Hi Tom,
> > > > > >
> > > > > > Thanks for running the release. I wonder if we should include:
> > > > > >
> > > > > >
> > > > >
> > >
> >
> https://github.com/apache/kafka/commit/134c432d6452de1bfb99d0f6b455a58c16bc626a
> > > > > > .
> > > > > >
> > > > > > This is a follow up of KAFKA-13794. What do you think?
> > > > > >
> > > > > > Best,
> > > > > > David
> > > > > >
> > > > > > On Fri, Apr 8, 2022 at 6:18 PM 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 29 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-rc0/RELEASE_NOTES.html
> > > > > > >
> > > > > > > *** Please download, test and vote by Friday 15 April, 12:00
> UTC
> > > > > > >
> > > > > > > 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-rc0/
> > > > > > >
> > > > > > > * 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-rc0/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-rc0
> > > > > > >
> > > > > > > * 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