Yes, I forgot to mention that I did some backward compatible verification as well. I was using 3.4.10 client to connect to a 3.5.3 ensemble and it works as expected.
On Tue, Mar 28, 2017 at 2:40 PM, Patrick Hunt <[email protected]> wrote: > fwiw I also tried running a 3 and 23 node cluster and it worked fine. 3.4.9 > client accessing 3.4.10 rc1 ensemble worked fine as well. > > Patrick > > On Mon, Mar 27, 2017 at 5:04 PM, Patrick Hunt <[email protected]> wrote: > > > +1 - xsum/sig verified, RAT ran clean, was able to build and run the > tests > > successfully (mac). > > > > Patrick > > > > On Thu, Mar 23, 2017 at 5:40 AM, Rakesh Radhakrishnan < > [email protected]> > > wrote: > > > >> This is the second release candidate for 3.4.10. This candidate fixed > the > >> MiniKDC authentication test case failures reported in the previous > >> candidate. > >> > >> This is a bug fix release candidate for 3.4.10. It fixes 43 issues, > >> including > >> security feature QuorumPeer mutual authentication via SASL and other > >> potential bugs. > >> > >> The full release notes are available at: > >> > >> https://issues.apache.org/jira/secure/ReleaseNote.jspa?proje > >> ctId=12310801&version=12338036 > >> > >> *** Please download, test and vote by March 29th 2017, 23:59 UTC+0. *** > >> > >> Source files: > >> http://people.apache.org/~rakeshr/zookeeper-3.4.10-candidate-1/ > >> > >> Maven staging repo: > >> https://repository.apache.org/content/groups/staging/org/apa > >> che/zookeeper/zookeeper/3.4.10/ > >> > >> The release candidate tag in git to be voted upon: release-3.4.10-rc1 > >> https://github.com/apache/zookeeper/tree/release-3.4.10-rc1 > >> > >> 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? > >> > >> > >> Rakesh > >> > > > > > -- Cheers Michael.
