Hi all,

I found two more regressions introduced in 3.8.0:
- https://github.com/apache/pulsar-client-cpp/issues/516
- https://github.com/apache/pulsar-client-cpp/issues/513

I will start the 4th candidate after addressing these issues, as well
as the APK incorrect format issue above.

Thanks,
Yunze

On Mon, Oct 20, 2025 at 3:39 PM Yunze Xu <[email protected]> wrote:
>
> Hi all,
>
> I found the new APK package is incorrect, after the installation, the
> library was installed at `/include` and `/lib` rather than the
> subdirectories of `/usr`, I'm cancelling this vote and will fix it in
> the next candidate.
>
> Thanks,
> Yunze
>
> On Fri, Oct 17, 2025 at 8:12 PM Yunze Xu <[email protected]> wrote:
> >
> > This is the 3rd release candidate for Apache Pulsar Client C++, version 
> > 3.8.0.
> >
> > It fixes the following issues:
> > https://github.com/apache/pulsar-client-cpp/milestone/10?closed=1
> >
> > *** Please download, test and vote on this release. This vote will stay open
> > for at least 72 hours ***
> >
> > Note that we are voting upon the source (tag), binaries are provided for
> > convenience.
> >
> > Source and binary files:
> > https://dist.apache.org/repos/dist/dev/pulsar/pulsar-client-cpp/pulsar-client-cpp-3.8.0-candidate-3/
> >
> > SHA-512 checksums:
> > 19a9f0fbeabfd6d657b0c5cfab0dc14f5d6cb98bb1cf8be37accc9ef837204bef7140060542adfb4ddd3fc63a4ca9003650d0c5aab3dcf33d83c74f8d58db7dd
> >  apache-pulsar-client-cpp-3.8.0.tar.gz
> >
> > The tag to be voted upon:
> > v3.8.0-candidate-3 (bf7acb29fdee844aed694668c93a95e399b8bf9b)
> > https://github.com/apache/pulsar-client-cpp/releases/tag/v3.8.0-candidate-3
> >
> > Pulsar's KEYS file containing PGP keys you use to sign the release:
> > https://downloads.apache.org/pulsar/KEYS
> >
> > Please download the source package, and follow
> > https://github.com/apache/pulsar-client-cpp/wiki/Verify-the-candidate-release-in-your-local-env
> > to compile and test.
> >
> > Note: If you're going to run the unit tests locally, please make sure
> > the proxy is disabled.

Reply via email to