+1 On Ubuntu 18.04 I built RELEASE with NO_TESTS=1 and verified that there were no numa or memkind dependencies or symbols in any binaries. I also grepped for numa and memkind across the codebase and didn't see any unexpected dependencies.
I did see memkind erroneously listed in thirdparty/LICENSE.txt, but given that it was always legally OK to ship memkind (as it's under a BSD license), I don't think this oversight merits a new RC. FWIW I published a patch to correct this on master: http://gerrit.cloudera.org:8080/14703. Also on Ubuntu 18.04 I built DEBUG and verified that all tests passed in slow mode. On Tue, Nov 12, 2019 at 5:15 PM Greg Solovyev <gsolov...@cloudera.com.invalid> wrote: > > +1. > I tested KuduTestHarness on Mac OS 10.14.4 by pointing pom.xml to staged > repos and verified that KUDU-2994 is fixed. > Greg > > On Wed, Nov 13, 2019 at 9:24 AM Alexey Serbin <ale...@apache.org> wrote: > > > Hello Kudu devs! > > > > The Apache Kudu team is happy to announce the first release candidate (RC1) > > for Apache Kudu 1.11.1. > > > > Apache Kudu 1.11.1 is a bug-fix release which fixes one critical licensing > > and few other issues in Kudu 1.11.0. > > > > This is a source-only release. The artifacts have been staged here: > > https://dist.apache.org/repos/dist/dev/kudu/1.11.1-RC1/ > > > > Java convenience binaries in the form of a Maven repository are staged > > here: > > https://repository.apache.org/content/repositories/orgapachekudu-1048 > > > > Linux and macOS kudu-binary JAR artifacts are staged here correspondingly: > > https://repository.apache.org/content/repositories/orgapachekudu-1049 > > https://repository.apache.org/content/repositories/orgapachekudu-1052 > > > > It is tagged in Git as 1.11.1-RC1 and the corresponding hash is the > > following: > > > > > > https://gitbox.apache.org/repos/asf?p=kudu.git;a=commit;h=c42b88906a6261c4c1de281eab8afc82674ecafd > > > > The release notes can be found here: > > > > https://github.com/apache/kudu/blob/branch-1.11.x/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. > > Also, it's worth running Kudu Java tests against kudu-binary JAR artifact > > as described in the commit message here: > > > > > > https://gitbox.apache.org/repos/asf?p=kudu.git;a=commit;h=8a6faaa93f3e206ac75e8087731daccaf7ab646a > > > > The vote will run until Fri Nov 15 18:00:00 PST 2019. > > This is a bit over 72 hours from the time of sending out this e-mail > > message. > > > > > > Thanks, > > > > Alexey > >
