+1 * verify checksum and signatures * build from source (Ubuntu 20.04 x86_64) * verify artifacts on Windows (`pulsar.dll` and `pulsarWithDeps.a` for both x86 and x64 architectures) * verify rpm, deb, apk packages in x86_64 architecture (`libpulsar.so` and `libpulsar.a`)
In addition, I created a repo to quickly set up the pre-built binaries on various operation compilers and systems, including MSVC on Windows, GCC on CentOS, Ubuntu and Alpine Linux. I believe it could save the time to verify these artifacts. https://github.com/BewareMyPower/pulsar-client-cpp-demo Thanks, Yunze On Thu, Nov 24, 2022 at 4:16 PM Zike Yang <z...@apache.org> wrote: > > This is the first release candidate for Apache Pulsar Client C++, version > 3.1.0. > > It fixes the following issues: > https://github.com/apache/pulsar-client-cpp/milestone/2?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.1.0-candidate-1/ > > SHA-512 checksums: > 617035c5a419fd058262f7e66f42cb8b4da711e2e191dc6d4428110804f7528c35d96b86f668e56072c2ef88f24a0ad078d578320e78ff63cd1209f44a191aa1 > ./apache-pulsar-client-cpp-3.1.0.tar.gz > > > The tag to be voted upon: > v3.1.0-candidate-1 (3b5aff7f7630295de6749bacfff53c2ebc63449c) > https://github.com/apache/pulsar-client-cpp/releases/tag/v3.1.0-candidate-1 > > Pulsar's KEYS file containing PGP keys you use to sign the release: > https://dist.apache.org/repos/dist/dev/pulsar/KEYS > > Please download the source package, and follow the README to compile and test. > > Thanks > Zike Yang
