This doesn't change my vote but relevant to release testing. I just wrote a basic upgrade test (WIP posted to Gerrit @ https://gerrit.cloudera.org/4424 ). All it does is run a simple variant of LinkedListTest, loading / verifying with one version and then re-verifying with another version of the software. Posted as a WIP because it needs a bit more cmake tinkering.
I ran it on two release builds, upgrading from 0.10.0 to 1.0.0 RC1, and the test passed. Mike On Wed, Sep 14, 2016 at 2:40 PM, Mike Percy <mpe...@apache.org> wrote: > +1 > > * Sigs and checksums match > * RAT passes > * Built in DEBUG mode on xenial following the steps in the README then ran > the tests; unit tests passed. > > Mike > > On Tue, Sep 13, 2016 at 12:39 AM, Todd Lipcon <t...@apache.org> wrote: > >> Hi, >> >> The Apache Kudu team is happy to announce the first release candidate for >> Apache Kudu 1.0.0. >> >> After approximately a year of beta releases, Apache Kudu has reached >> version 1.0. >> This version number signifies that the development team feels that Kudu is >> stable >> enough for usage in production environments. >> >> The is a source-only release. The artifacts were staged here: >> https://dist.apache.org/repos/dist/dev/kudu/1.0.0-RC1/ >> >> Java convenience binaries in the form of a Maven repository are staged >> here: >> https://repository.apache.org/content/repositories/orgapachekudu-1001/ >> >> It was built from this tag: >> https://git-wip-us.apache.org/repos/asf?p=kudu.git;a=commit; >> h=6f6e49ca98c3e3be7d81f88ab8a0f9173959b191 >> >> The release notes can be found here (some links from this document will >> only work when this version is released): >> https://github.com/apache/kudu/blob/branch-1.0.x/docs/release_notes.adoc >> >> KEYS file: >> http://www.apache.org/dist/kudu/KEYS >> >> I'd suggest going through the README, building Kudu, and running the >> unit tests. Testing out the Maven repo would also be appreciated. >> >> Please try the release and vote; the vote will end in 72 hours (on >> 9/16/2016 at 12:30am PDT). >> >> Thanks, >> Todd >> > >
