Re: QA signup
Thanks for staring this thread Jon!
On Thu, Sep 6, 2018 at 5:51 AM Jonathan Haddad <jon@xxxxxxxxxxxxx> 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.
+1 to a more coordinated effort. I think we could use the Confluence that
was set up a little bit ago since it was setup for this purpose, at least
for finalized plans and results:
> 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.
+1 to this as well. I am always a fan of folks learning about a
subsystem/project through testing. It can be challenging to get folks new
to a project excited about testing first but for those that do, or for
committers who want to learn another part of the db, its a great way to
Another thing we can do here is make sure teams are writing about the
testing they are doing and their results. This will help share knowledge
about techniques and approaches that others can then apply. This knowledge
can be shared on the mailing list, a blog post, or in JIRA.
> Any thoughts? I'm happy to take the lead on this.
> Jon Haddad
> twitter: rustyrazorblade