Re: 4.0 Testing Signup

Tommy, thank you! I’ve added your name as a contributor toward upgrade testing. Thanks also for all of the work you’ve done toward this already, filing CASSANDRA-{14820, 14836, 14841, 14842, 14848}. The testing you’ve done so far, patches contributed, and issues reported are all great finds. To

Re: 4.0 Testing Signup

Hi, I like to add myself as contributor under Cluster Upgrade but I could not edit the page, could you please help. I have already done some testing in this are lately and created a few jiras, two remains open CASSANDRA-14842 and CASSANDRA-14848. Thanks, Tommy On 2018-11-08 23:30, Joseph Lync

Re: 4.0 Testing Signup

Joey, thanks for starting this document! I’ve updated it to add several leads/contributors, and will probably have a few minor updates to add soon. On November 8, 2018 at 2:49:52 PM, Joseph Lynch (joe.e.ly...@gmail.com) wrote: On Thu, Nov 8, 2018 at 1:42 PM kurt

Re: 4.0 Testing Signup

On Thu, Nov 8, 2018 at 1:42 PM kurt greaves wrote: > 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 J

Re: 4.0 Testing Signup

On Thu, Nov 8, 2018 at 11:04 AM Romain Hardouin wrote: > > Hi, > I'm volunteer to be contributor on Metrics or Tooling component. Are we > supposed/allowed to edit Confluence page directly?Btw I think that tooling > should be split, maybe one ticket per tool? > Awesome! Yes feel free to add your

Re: 4.0 Testing Signup

Thanks Romain! Let's keep a top level ticket for the/a component, but add child tasks as needed. I think child tickets are a little easier to manage than using a tag or similar. On Thu, Nov 8, 2018 at 11:04 AM Romain Hardouin wrote: > > > Hi, > I'm volunteer to be contributor on Metrics or Toolin

Re: 4.0 Testing Signup

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,

Re: 4.0 Testing Signup

Hi, I'm volunteer to be contributor on Metrics or Tooling component. Are we supposed/allowed to edit Confluence page directly?Btw I think that tooling should be split, maybe one ticket per tool? Thanks, RomainLe mercredi 7 novembre 2018 à 22:51:30 UTC+1, sankalp kohli a écrit : This

Re: 4.0 Testing Signup

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 wrote: > Followin

4.0 Testing Signup

Following up on Jon's call for QA, I put together the start of a confluence page for people to list out