I think this is a good idea. Having a list documented itself is big plus.
Explicitly listing Required/ Mandatory checks and Optional checks for
release type (e.g. alpha, beta etc) will help too.
On Mon, Sep 18, 2017 at 1:10 PM, Andrew Purtell wrote:
> I also think it's fair
One thing that I've seen in successful other communities is that when folks
run the long running tests they also document the specifics of the
configuration that they used. Things like your java version, operating
system, EC2 instance type. Then this all gets fed into a table published
with the
I also think it's fair to make allowances for folks who want to test the RC
but might be short on personal time. So there should be a list of essential
items (like sigs, sums, shas/tags) and then a list of optional items (ltt,
pe, itbll, etc.)
On Mon, Sep 18, 2017 at 12:52 PM, Stack
On Mon, Sep 18, 2017 at 11:49 AM, Misty Stanley-Jones
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
Big +1. I opened HBASE-16559 to start working on this last year, but then
life happened.
-Dima
On Mon, Sep 18, 2017 at 11:53 AM, Ted Yu wrote:
> bq. have some kind of dashboard where people could "sign up" to test
> different things on that checklist
>
> This makes sense.
bq. have some kind of dashboard where people could "sign up" to test
different things on that checklist
This makes sense.
+1
On Mon, Sep 18, 2017 at 11:49 AM, Misty Stanley-Jones
wrote:
> I keep feeling like we need a checklist for all the different things that
> should be
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