This is a release candidate for 3.6.0. It is a major release and it introduces a lot of new features, most notably: - Built-in data consistency check inside ZooKeeper - Allow Followers to host Observers - A new feature proposal to ZooKeeper: authentication enforcement - Pluggable metrics system for ZooKeeper (and Prometheus.io integration) - TLS Port unification - Audit logging in ZooKeeper servers - Improve resilience to network (advertise multiple addresses for members of a Zookeeper cluster) - Persistent Recursive Watches - add an API and the corresponding CLI to get total count of recursive sub nodes under a specific path
The full release notes is available at: https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=12310801&version=12346617 *** Please download, test and vote by January 19th 2020, 23:59 UTC+0. *** Source files: https://people.apache.org/~eolivelli/zookeeper-3.6.0-candidate-0/ Maven staging repo: https://repository.apache.org/content/repositories/orgapachezookeeper-1045/ The release candidate tag in git to be voted upon: release-3.6.0-0 https://github.com/apache/zookeeper/tree/release-3.6.0-0 ZooKeeper's KEYS file containing PGP keys we use to sign the release: https://www.apache.org/dist/zookeeper/KEYS Please note that this new major release introduces these change in the staging area: - the source artifacts package is in zip format - we are releasing a new binary package with the C client (with OpenSSL support) - website preview We are also adding a new JAR: zookeeper-metrics-providers The staging version of the website is: https://people.apache.org/~eolivelli/zookeeper-3.6.0-candidate-0/website/ Should we release this candidate? Enrico Olivelli