-1, because commit 038c3eb has messed up deadline-based waiting on macOS. I don't know the full extent of the breakage but Will and Alexey reported seeing abnormally high CPU usage in Kudu servers.
I published a fix in http://gerrit.cloudera.org:8080/9695 and, once it is merged to master, I suggest we backport it to 1.7 and respin a new RC. On Fri, Mar 16, 2018 at 12:42 PM, Grant Henke <[email protected]> wrote: > Hi, > > The Apache Kudu team is happy to announce the first release candidate for > Apache Kudu 1.7.0. > > Apache Kudu 1.7.0 is a minor release that offers many improvements and > fixes since the prior release. > > The is a source-only release. The artifacts have been staged here: > https://dist.apache.org/repos/dist/dev/kudu/1.7.0-RC1/ > > Java convenience binaries in the form of a Maven repository are staged here: > https://repository.apache.org/content/repositories/orgapachekudu-1018/ > > It is tagged in Git as 1.7.0-RC1 and the corresponding git hash is the > following: > https://git-wip-us.apache.org/repos/asf?p=kudu.git;a=commit;h=6c247238d98f96ede9475b479e148f6393d29b97 > > The release notes can be found here: > https://github.com/apache/kudu/blob/1.7.0-RC1/docs/release_notes.adoc > > The KEYS file to verify the artifact signatures can be found here: > https://dist.apache.org/repos/dist/release/kudu/KEYS > > I'd suggest going through the README and the release notes, building Kudu, > and running the unit tests. Testing out the Maven repo would also be > appreciated. > > The vote will run until Tuesday, March 6th at 11PM PDT. We'd normally > run a vote for 3 full days but since we're headed into the weekend now > let's do 4 days instead. > > Thank you, > Grant > -- > Grant Henke > Software Engineer | Cloudera > [email protected] | twitter.com/gchenke | linkedin.com/in/granthenke
