+1 (non binding) Tested Majordodo (http://majordodo.org) and BlazingCache (http://blazingcache.org) against 3.5.2-alpha.
My tests also include running Apache BookKeeper 4.4.0 using the 3.5.2-alpha java client. All is fine but dependencies changed a lot, many legacy deps like jline, jms and sun jmx disappeared and this is very good, but this new dependency showed up: net.java.dev.javacc:javacc:jar:5.0 If I exclude javacc all of my tests continue to run fine, my tests cover both java client and embedded single server. Maybe it would be useful to hide the dependency in future release but it is not a showstopper for my projects. 2016-06-28 19:52 GMT+02:00 Abraham Fine <a...@abrahamfine.com>: > +1 tested SSL support, everything appears to be working as expected. > > On Fri, Jun 24, 2016, at 03:19 PM, Patrick Hunt wrote: >> +1. sig/xsum are valid, RAT ran clean and no other discrepancies noticed. >> I >> ran it through a number of manual tests (including starting a 23 server >> ensemble) - no issues found. >> >> Patrick >> >> On Thu, Jun 23, 2016 at 10:33 PM, Chris Nauroth >> <cnaur...@hortonworks.com> >> wrote: >> >> > This is a release candidate for 3.5.2-alpha. The full release notes are >> > available at: >> > >> > https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=12310801&v >> > ersion=12331981 >> > >> > *** Please download, test and vote by July 1st 2016, 23:59 UTC+0. *** >> > >> > Source files: >> > http://people.apache.org/~cnauroth/zookeeper-3.5.2-alpha-candidate-0/ >> > >> > Maven staging repo: >> > https://repository.apache.org/content/groups/staging/org/apache/zookeeper/z >> > ookeeper/3.5.2-alpha/ >> > >> > The tag to be voted upon: >> > https://svn.apache.org/repos/asf/zookeeper/tags/release-3.5.2-rc0/ >> > >> > 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? >> > >> > >> > --Chris Nauroth >> > >> >
