+1 (binding) - Verified all checksums. - Verified all signatures. - Built from source, including native code on Linux. - Tests passed. - Ran several small samples successfully.
I'm seeing failures in the cppunit tests in zookeeper-client-c. The same failures reproduce on version 3.5.9 though, so it's not related to this release. I assume this is a configuration issue I need to diagnose in my environment. Chris Nauroth On Thu, May 19, 2022 at 2:31 AM Szalay-Bekő Máté <szalay.beko.m...@gmail.com> wrote: > This is a bugfix release candidate for 3.5.10. It fixes 43 issues, > including CVE fixes, log4j1 removal (by default using reload4j from now) > and various other bug fixes (thread leaks, data corruption, snapshotting > and SASL related fixes). > > Please note, we announced 3.5 to be EOL from June 1st 2022, so most likely > this will be our > last 3.5 release. > > The full release notes is available at: > > https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=12310801&version=12349434 > > *** Please download, test and vote by May 27th 2022, 23:59 UTC+0. *** > > > Source files: > https://people.apache.org/~symat/zookeeper-3.5.10-rc0/ > > Maven staging repo: > > https://repository.apache.org/content/groups/staging/org/apache/zookeeper/zookeeper/3.5.10/ > > The release candidate tag in git to be voted upon: release-3.5.10-rc0 > > ZooKeeper's KEYS file containing PGP keys we use to sign the release: > https://www.apache.org/dist/zookeeper/KEYS > > The staging version of the website is: > https://people.apache.org/~symat/zookeeper-3.5.10-rc0/website/ > > > Should we release this candidate? > > > Best regards, > Máté >
