Thank you all for the voting on the RC2 for 1.7.0 That concludes the voting.

Voting for the release has passed with:
3 binding +1
4 non binding +1

no 0 or -1 votes.

As the next step, I'll publish the release, images and update the website.
After that is done I will send an announcement email.

Thank you,
Peter

On Sat, Jul 26, 2025 at 4:06 PM Ryan Huang <ryanker...@gmail.com> wrote:

> +1 (non-binding)
>
> 1. built on Mac M1 chip
> 2. Verified signature and checksums
> 3. Installed locally on kind cluster
> 4. Ran tests/e2e tests
>
> Thanks,
> Hsien-Cheng(Ryan) Huang
>
>
> On Fri, Jul 25, 2025 at 20:48 Michael Chu <kousei47...@gmail.com> wrote:
>
> > +1 (non-binding)
> >
> > 1. Verified signature and checksum.
> > 2. Built images with go 1.23.6 on Mac (arm64).
> > 3. Deployed on kind 1.32.2.
> > 4. E2E tests passed.
> > 5. Unit tests passed.
> >
> > Thanks,
> > Michael Chu
> >
> > On Mon, Jul 21, 2025 at 8:58 PM Peter Bacsko <bacs...@gmail.com> wrote:
> >
> > > Hello everyone,
> > >
> > > I would like to call a vote for releasing Apache YuniKorn 1.7.0 RC2.
> > >
> > > The release artifacts have been uploaded here:
> > > https://dist.apache.org/repos/dist/dev/yunikorn/1.7.0-RC2/
> > >
> > > My public key is located in the KEYS file:
> > > https://dist.apache.org/repos/dist/release/yunikorn/KEYS
> > >
> > > JIRA issues that have been resolved in this release:
> > > https://issues.apache.org/jira/issues/?filter=12353609
> > >
> > > Git tags for each component are as follows:
> > > * yunikorn-scheduler-interface: v1.7.0-0
> > > * yunikorn-core: v1.7.0-2
> > > * yunikorn-k8shim: v1.7.0-3
> > > * yunikorn-web: v1.7.0-0
> > > * yunikorn-release: v1.7.0-1
> > >
> > > Once the release is voted on and approved, all repos will be tagged
> > > v1.7.0 for consistency.
> > >
> > > Please review and vote. The vote will be open for at least 72 hours
> > > and will be open until at least Thursday 24 Jul 2025 18:00 CEST.
> > >
> > > [ ] +1 Approve
> > > [ ] +0 No opinion
> > > [ ] -1 Disapprove (and the reason why)
> > >
> > > Thank you,
> > > Peter
> > >
> >
>

Reply via email to