I have a clarification question about the RC. To build the RC, I had to enable crypto.policy unlimited in the jre (I'm using build 1.8.0_152-b16). I'm wondering if this is going to be an issue for some users as this option is related to import/export regulation. Has anyone looked into it and could clarify it to me, please?
Thanks, -Flavio > On 25 Apr 2019, at 15:10, Andor Molnar <[email protected]> wrote: > > This is the first stable release of 3.5 branch: 3.5.5. It resolves 117 > issues, including Maven migration, Quorum TLS, TTL nodes and lots of other > performance and stability improvements. > > The full release notes is available at: > > https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=12310801&version=12343268 > > *** Please download, test and vote by May 3rd 2019, 23:59 UTC+0. *** > > Source files: > https://dist.apache.org/repos/dist/dev/zookeeper/zookeeper-3.5.5-rc5/ > > Maven staging repos: > https://repository.apache.org/content/groups/staging/org/apache/zookeeper/parent/3.5.5/ > https://repository.apache.org/content/groups/staging/org/apache/zookeeper/zookeeper-jute/3.5.5/ > https://repository.apache.org/content/groups/staging/org/apache/zookeeper/zookeeper/3.5.5/ > > The release candidate tag in git to be voted upon: release-3.5.5-rc5 > > ZooKeeper's KEYS file containing PGP keys we use to sign the release: > http://www.apache.org/dist/zookeeper/KEYS > > Should we release this candidate? >
