> On Sep 6, 2018, at 10:27 AM, Jonathan Haddad <j...@jonhaddad.com> wrote: > > I completely agree with you, Sankalp. I didn't want to dig too deep into > the underlying testing methodology (and I still think we shouldn't just > yet) but if the goal is to have confidence in the release, our QA process > needs to be comprehensive.
I think it is critical to specify the parameters and methodology. We can start with the major areas that we'd like to test and later dig deeper into the specifics. > I believe that having focused teams for each component with a team leader > with support from committers & contributors gives us the best shot at > defining large scale functional tests that can be used to form both > progress and bug reports. (A person could / hopefully will be on more than > one team). Coming up with those comprehensive tests will be the jobs of > the teams, getting frequent bidirectional feedback on the dev ML. Bugs go > in JIRA as per usual. > > Hopefully we can continue this process after the release, giving the > project more structure, and folding more people in over time as > contributors and ideally committers / PMC. +1 Dinesh --------------------------------------------------------------------- To unsubscribe, e-mail: dev-unsubscr...@cassandra.apache.org For additional commands, e-mail: dev-h...@cassandra.apache.org
