Hi Matthias,
Thanks for running the release.

I did the following:
  - Browsed the javadoc
  - Browsed the protocol documentation
  - Ran the quickstart with ZK

+1 (non-binding)

Thanks,
Andrew
________________________________________
From: Luke Chen <show...@gmail.com>
Sent: 06 December 2024 07:22
To: d...@kafka.apache.org <d...@kafka.apache.org>
Cc: users@kafka.apache.org <users@kafka.apache.org>; kafka-clients 
<kafka-clie...@googlegroups.com>
Subject: Re: [VOTE] 3.7.2 RC1

Hi Matthias,

Thanks for running the release.

I did the following steps:

   - Validated the checksums and keys
   - Browsed the javadocs
   - Browsed the documentation
   - Ran all the quickstart using KRaft with kafka_2.13-3.7.2.tgz
   - Ran basic quickstart using 3.7.2-rc1 docker image

+1 binding from me.

Thanks.
Luke

On Fri, Dec 6, 2024 at 12:06 PM Matthias J. Sax
<matth...@confluent.io.invalid> wrote:

> Thanks Josep. Great idea.
>
> Here is the draft PR link for docs updates:
> https://github.com/apache/kafka-site/pull/652
>
>
>
> Thanks Divij for talking a look and voting.
>
> If we need a new RC, happy to include the two tickets you mentioned. Too
> bad that you did miss my original email proposing 3.7.2, in which I did
> ask people to call out missing fixes for cherry-picking.
>
>
> -Matthias
>
>
> On 12/5/24 11:28 AM, Divij Vaidya wrote:
> > ## Validations (on AArch64 machine)
> >
> > 1. Built from source
> > 2. Ran all tests (successful amongst multiple runs)
> > 3. Verified basic produce/consume
> > 4. Verified that the maven artifacts contain 3.7.2 bits
> >
> > ## Problems
> >
> > 1. While checking the commits on the branch, I found one commit which is
> > not captured in release notes (
> > https://issues.apache.org/jira/browse/KAFKA-17190). I have updated the
> JIRA
> > with the correct tag now. This does not require a new RC.
> >
> > 2. Do we want to backport changes to 3.7 such as
> > https://issues.apache.org/jira/browse/KAFKA-18051 and
> > https://issues.apache.org/jira/browse/KAFKA-17062? The former is a
> > good-to-have validation and the latter impacts data stored by Tiered
> > Storage which is not GA in 3.7. Hence, we do not need a new RC, but if we
> > do end up creating one for a different reason, let's backport these.
> >
> > ## Vote
> >
> > + 1 (binding)
> >
> > --
> > Divij Vaidya
> >
> >
> >
> > On Thu, Dec 5, 2024 at 7:16 PM Josep Prat <josep.p...@aiven.io.invalid>
> > wrote:
> >
> >> Hi Matthias,
> >>
> >> For 3.8.1 I pointed to the PR that makes the update to the new patch
> >> version.
> >>
> >> Best,
> >>
> >> ------------------
> >> Josep Prat
> >> Open Source Engineering Director, Aiven
> >> josep.p...@aiven.io   |   +491715557497 | aiven.io
> >> Aiven Deutschland GmbH
> >> Alexanderufer 3-7, 10117 Berlin
> >> Geschäftsführer: Oskari Saarenmaa, Hannu Valtonen,
> >> Anna Richardson, Kenneth Chen
> >> Amtsgericht Charlottenburg, HRB 209739 B
> >>
> >> On Thu, Dec 5, 2024, 18:46 Matthias J. Sax
> <matth...@confluent.io.invalid>
> >> wrote:
> >>
> >>> Thanks for taking a look Bill!
> >>>
> >>> Yes, for minor release we stage the new docs in a "hidden" folder (eg
> >>> `/40/` for upcoming 4.0.0 release), but we don't do this for bug-fix
> >>> releases IIRC -- there is no `/370/` or `/371/` folders. We could
> create
> >>> a `/372/` but would need to delete it afterward. Pushing into `/37/`
> >>> folder would overwrite the current `3.7.1` docs so we cannot do this.
> >>>
> >>> Hence, I just skipped pushing the docs to `asf-site` -- I think this is
> >>> what we did in the past, too?
> >>>
> >>>
> >>> -Matthias
> >>>
> >>>
> >>>
> >>> On 12/4/24 3:53 PM, Bill Bejeck wrote:
> >>>> Matthias,
> >>>>
> >>>> Thanks for running the release.
> >>>>
> >>>> I did the following steps:
> >>>>
> >>>>      - Validated the checksums and keys
> >>>>      - Built from source
> >>>>      - Ran all the unit tests
> >>>>      - Spot checked the javadocs
> >>>>      - Spot checked the documentation
> >>>>      - Ran the KRaft quickstart
> >>>>      - Pulled and started the docker image
> >>>>      - Ran the Kafka Streams quickstart
> >>>>
> >>>> When I looked over the documentation, I noticed the quickstart (main
> >> page
> >>>> and Kafka Streams) still reference the previous release 3.7.1, but
> this
> >>>> isn't enough to block the release, we can do a PR against the
> >> kafka-site
> >>>> repo.
> >>>>
> >>>> +1(binding)
> >>>>
> >>>> Regards,
> >>>> Bill
> >>>>
> >>>> On Wed, Dec 4, 2024 at 3:15 PM Matthias J. Sax
> >>>> <matth...@confluent.io.invalid> wrote:
> >>>>
> >>>>> Hello Kafka users, developers and client-developers,
> >>>>>
> >>>>>
> >>>>> This is the second candidate for release of Apache Kafka 3.7.2. This
> >> is
> >>>>> a bug-fix release, closing 21 Jira tickets.
> >>>>>
> >>>>>
> >>>>>
> >>>>> Release notes for the 3.7.2 release:
> >>>>>
> >>>
> >>
> https://dist.apache.org/repos/dist/dev/kafka/3.7.2-rc1/RELEASE_NOTES.html
> >>>>>
> >>>>> Please download, test and vote by Tuesday, Dec 10, 9am PST.
> >>>>>
> >>>>> 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://dist.apache.org/repos/dist/dev/kafka/3.7.2-rc1/
> >>>>>
> >>>>>
> >>>>> * Docker release artifacts to be voted upon:
> >>>>>
> >>>>>
> >>>
> >>
> https://hub.docker.com/layers/apache/kafka/3.7.2-rc1/images/sha256-e81f67cd3ca9c018d9b6a2d2354dc6067a5a25908c642383c652f0c6b3e8c4a4?context=explore
> >>>>>
> >>>>>
> >>>>> * Maven artifacts to be voted upon:
> >>>>>
> >> https://repository.apache.org/content/groups/staging/org/apache/kafka/
> >>>>>
> >>>>>
> >>>>> * Javadoc:
> >>>>> https://dist.apache.org/repos/dist/dev/kafka/3.7.2-rc1/javadoc/
> >>>>>
> >>>>>
> >>>>> * Tag to be voted upon (off 3.7 branch) is the 3.7.2 tag:
> >>>>> https://github.com/apache/kafka/releases/tag/3.7.2-rc1
> >>>>>
> >>>>>
> >>>>> * Documentation:
> >>>>> https://kafka.apache.org/37/documentation.html
> >>>>>
> >>>>>
> >>>>> * Protocol:
> >>>>> https://kafka.apache.org/37/protocol.html
> >>>>>
> >>>>>
> >>>>> * Successful CI builds for the 3.7 branch:
> >>>>> Unit/integration tests:
> >>>>> https://ci-builds.apache.org/job/Kafka/job/kafka/job/3.7/
> >>>>>
> >>>>> Builds are flaky, but considering the last runs combined, each test
> >>>>> passed at least once.
> >>>>>
> >>>>> System tests:
> >>>>>
> >>>>>
> >>>>>
> >>>
> >>
> https://confluent-open-source-kafka-system-test-results.s3-us-west-2.amazonaws.com/3.7/2024-12-02--001.ce908c58-d9cf-48db-b95f-08ccd8274a3a--1733218470--confluentinc--3.7--89dd7938f3/report.html
> >>>>>
> >>>>>
> >>>>>
> >>>
> >>
> https://confluent-open-source-kafka-system-test-results.s3-us-west-2.amazonaws.com/3.7/2024-11-29--001.5041d078-e977-4cf1-8d8d-76f0feea7ee0--1732947843--confluentinc--3.7--89dd7938f3/report.html
> >>>>>
> >>>>> One test is flaky, but we got two different runs that make everything
> >>>>> passing.
> >>>>>
> >>>>>
> >>>>> * Successful Docker Image Github Actions Pipeline for 3.7 branch:
> >>>>>
> >>>>> Docker Build Test Pipeline (JVM):
> >>>>>     - https://github.com/apache/kafka/actions/runs/12167195510
> >>>>>
> >>>>> Build and Push Release Candidate Docker Image Pipeline (JVM):
> >>>>>     - https://github.com/apache/kafka/actions/runs/12167268398
> >>>>>
> >>>>>
> >>>>>
> >>>>> Thanks,
> >>>>>     -Matthias
> >>>>>
> >>>>
> >>>
> >>>
> >>
> >
>
>

Reply via email to