On Mon, Sep 18, 2017 at 11:49 AM, Misty Stanley-Jones <[email protected]> wrote:
> I keep feeling like we need a checklist for all the different things that > should be tested when people vote on a release candidate. Not everyone > needs to do all the checks, but probably at least someone should be doing > each of the following (and maybe things I am forgetting): > > - Binary .tar.gz and .zip extract > - Source .tar.gz and .zip extract > - All md5sums match > - The source .tar.gz matches the hash on the Git repo > - Everything is signed correctly > - The source compiles into exactly the binary > - The source compiles with both OpenJDK and Oracle JDK (?) > - The binaries from the binary .tar.gz and .zip run as expected > - The binaries built from the source .tar.gz and .zip run as expected > - The standard tests all run and pass, with the exception of known flakies > - LTT and PE tools run and look good > > > Would it be helpful to have some kind of dashboard where people could "sign > up" to test different things on that checklist, and maybe to require that > all the checks have been done by at least someone before the RC can be > released? Maybe it could be something silly like a Google Form, even. Or a > spreadsheet. > > I think it might also be less intimidating for newbies who have never voted > on an RC before (and we really really want as many people as possible to > participate in the voting process). > > What do y'all think? > > Misty > Sounds great. St.Ack P.S.Here is a link to an old email that points at a LarsH doc. which cribs from an old Dave Wang wiki page that tried to do similar: http://search-hadoop.com/m/HBase/YGbb22RVtnt76g?subj=Re+Releases+tests+
