It looks like KUDU-2870 <https://issues.apache.org/jira/browse/KUDU-2870> is a bug that should be fixed and included in the release. There are a few other small bugs that can be backported as well. I will cut a new RC and call a vote after that issue is resolved.
Thank you, Grant On Fri, Jun 14, 2019 at 5:20 PM Grant Henke <[email protected]> wrote: > Hello Kudu devs! > > The Apache Kudu team is happy to announce the first release candidate for > Apache Kudu 1.10.0. > > Apache Kudu 1.10.0 is a minor release that offers many improvements and > fixes since the prior release. > > This is a source-only release. The artifacts have been staged here: > https://dist.apache.org/repos/dist/dev/kudu/1.10.0-RC1/ > > Java convenience binaries in the form of a Maven repository are staged > here: > https://repository.apache.org/content/repositories/orgapachekudu-1035/ > > It is tagged in Git as 1.10.0-RC1 and the corresponding hash is the > following: > > https://gitbox.apache.org/repos/asf?p=kudu.git;a=commit;h=ce322bdfc979f0f3f5d3881affcdd22e0c5b6ac2 > > The WIP release notes can be found here: > > https://docs.google.com/document/d/1CnGvoOob9H8BcY5dPciYCW5RTj9J--wXPmeMDQzqH6Y/edit?usp=sharing > > 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 Wednesday, June 19th at 11:59AM PST. This is a bit > over the suggested 72 hours due to the weekend. > > Thank you, > Grant > > -- > Grant Henke > Software Engineer | Cloudera > [email protected] | twitter.com/gchenke | linkedin.com/in/granthenke > -- Grant Henke Software Engineer | Cloudera [email protected] | twitter.com/gchenke | linkedin.com/in/granthenke
