Been thinking about this for a while and agree it's how we should approach it. BIkeshedding but seems like a nice big table would be suitable here, and I think rather than a separate confluence page per component we just create separate JIRA tickets that detail what's being tested and the approach, and discussion can be kept in JIRA.
I'm happy to volunteer for testing repair. I can also add lots of different components to the list if you're happy for me to attack the page. On Thu, 8 Nov 2018 at 08:51, sankalp kohli <kohlisank...@gmail.com> wrote: > This is good start and we should use this approach each component. Once we > have volunteers for each area, it will be important to also publish a > confluence page per component by the volunteer so we can know/discuss how > it was tested. > > On Wed, Nov 7, 2018 at 12:14 PM Joseph Lynch <joe.e.ly...@gmail.com> > wrote: > > > Following up on Jon's call > > < > > > https://lists.apache.org/thread.html/17e57d1666393d961a15502a648a1174a1b145a4bf0a8e07fd8bb760@%3Cdev.cassandra.apache.org%3E > > > > > for QA, I put together the start of a confluence page > > <https://cwiki.apache.org/confluence/display/CASSANDRA/4.0+QA+Signup>for > > people to list out important components that they think should be tested > > before 4.0 releases and hopefully committers and contributors can signup > > and present their progress to the community. I've certainly missed a ton > of > > components that need testing but I figured that it may be good to get the > > conversation started and moving forward. > > > > What do people think? Is there a more effective way to list these out or > if > > people like this maybe folks can start contributing sections and > > volunteering to shepherd or test them? > > > > Let me know, > > -Joey > > >
