+1 (binding)

- verified packages checksum and signatures.

- the source package is built and runs successfully.

- The binary package runs well.


On Thu, Jul 3, 2025 at 5:46 AM Andrey Yegorov
<andrey.yego...@datastax.com.invalid> wrote:

> +1 (binding)
>
> Built and ran tests on Mac
>
> On Tue, Jun 24, 2025 at 6:42 PM lushiji(apache) <lush...@apache.org>
> wrote:
>
> > Hi everyone,
> > Please review and vote on the release candidate #0 for the version
> 4.16.7,
> > as follows:
> > [ ] +1, Approve the release
> > [ ] -1, Do not approve the release (please provide specific comments)
> >
> > The complete staging area is available for your review, which includes:
> > * Release notes [1]
> > * The official Apache source and binary distributions to be deployed to
> > dist.apache.org [2]
> > * All artifacts to be deployed to the Maven Central Repository [3]
> > * Source code tag "release-4.16.7" [4] with git sha
> > 27de09989a6920b939e29dcf625720f437269b38
> >
> > BookKeeper's KEYS file contains PGP keys we used to sign this release:
> > https://dist.apache.org/repos/dist/release/bookkeeper/KEYS
> >
> > Please download these packages and review this release candidate:
> >
> > - Review release notes
> > - Download the source package (verify shasum, and asc) and follow the
> > instructions to build and run the bookkeeper service.
> > - Download the binary package (verify shasum, and asc) and follow the
> > instructions to run the bookkeeper service.
> > - Review maven repo, release tag, licenses, and any other things you
> think
> > it is important to a release.
> >
> > The vote will be open for at least 72 hours. It is adopted by majority
> > approval, with at least 3 PMC affirmative votes.
> >
> > Thanks,
> > Release Manager
> > [1] https://github.com/apache/bookkeeper/pull/4621
> > [2]
> > https://dist.apache.org/repos/dist/dev/bookkeeper/bookkeeper-4.16.7-rc0/
> > [3]
> >
> >
> https://repository.apache.org/content/repositories/orgapachebookkeeper-1099/
> > [4] https://github.com/apache/bookkeeper/tree/v4.16.7-rc0
> >
>
>
> --
> Andrey Yegorov
>

Reply via email to