+1 I personally would like to contribute. On Thu, Sep 6, 2018 at 8:51 PM Jonathan Haddad <j...@jonhaddad.com> wrote:
> For 4.0, I'm thinking it would be a good idea to put together a list of the > things that need testing and see if people are willing to help test / break > those things. My goal here is to get as much coverage as possible, and let > folks focus on really hammering on specific things rather than just firing > up a cluster and rubber stamping it. If we're going to be able to > confidently deploy 4.0 quickly after it's release we're going to need a > high attention to detail. > > In addition to a signup sheet, I think providing some guidance on how to QA > each thing that's being tested would go a long way. Throwing "hey please > test sstable streaming" over the wall will only get quality feedback from > folks that are already heavily involved in the development process. It > would be nice to bring some new faces into the project by providing a > little guidance. > > We could help facilitate this even further by considering the people > signing up to test a particular feature as a team, with seasoned Cassandra > veterans acting as team leads. > > Any thoughts? I'm happy to take the lead on this. > -- > Jon Haddad > http://www.rustyrazorblade.com > twitter: rustyrazorblade >
