I have built the Zookeeper 3.4.8 RC0 from the source,
updated the HBase 1.2.0RC3 (HBase latest release RC) pom to use the new
zookeeper version,
built HBase and ran HBase mvn test suite twice. All are successful.

+1

Jerry

On Tue, Feb 16, 2016 at 7:17 AM, Flavio P JUNQUEIRA <f...@apache.org> wrote:

> I wanted to add that it is very important that all users test the release
> candidate, not only committers or PMC members.  That's the way to gain
> confidence that the RC is good for everyone.
>
> If you have a chance to check it out, especially if you have an app to test
> it against, please do it this week. The community appreciates it.
>
> -Flavio
> On 16 Feb 2016 4:20 am, "Raúl Gutiérrez Segalés" <r...@itevenworks.net>
> wrote:
>
> > Hi,
> >
> > Quick reminder that the vote closes up on the 20th, it would be great to
> > have more votes and feedback this week. Thanks!
> >
> >
> > -rgs
> >
> > On 5 February 2016 at 20:00, Raúl Gutiérrez Segalés <r...@itevenworks.net
> >
> > wrote:
> >
> > > This is a bugfix release candidate for 3.4.8. It fixes 9 issues, most
> > > notably a deadlock when shutting down ZooKeeper.
> > >
> > > The full release notes is available at:
> > >
> > >
> > >
> >
> https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=12310801&version=12326517
> > >
> > > *** Please download, test and vote by February 20th 2016, 23:59 UTC+0.
> > ***
> > >
> > > Source files:
> > > http://people.apache.org/~rgs/zookeeper-3-4-8-rc0/
> > >
> > > Maven staging repo:
> > >
> > >
> >
> https://repository.apache.org/content/groups/staging/org/apache/zookeeper/zookeeper/3.4.8/
> > >
> > > The tag to be voted upon:
> > > https://svn.apache.org/repos/asf/zookeeper/tags/release-3.4.8-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?
> > >
> > > Note that the approval is by lazy majority according to the bylaws and
> > > only PMC votes are binding.
> > >
> > >
> > > -rgs
> > >
> >
>

Reply via email to