It typically doesn't block a release but we should get it into the next one now that we've noticed...
Patrick On Tue, Feb 9, 2016 at 3:58 AM, Flavio Junqueira <f...@apache.org> wrote: > I've been able to build, run tests successfully, and build it with Apache > Kafka. I've also checked signature, digests, and the release notes. The only > small thing that needs to be updated is the NOTICE file. It needs to say 2016 > rather than 2015. Should we do another RC because of this small issue? I'd > like to know what others think before casting my vote. > > -Flavio > > >> On 06 Feb 2016, at 04: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 >
