Re: [DISCUSS] Revisiting the quality testing epic scope

2021-01-25 Thread Alexander DEJANOVSKI
that RC gut check. If there's a remaining issue that would prevent you > from running trunk in a prod environment, please file it and raise > attention - it'll help us finish polishing the release. And if there isn't > - deploy it! > > We still need to finish the remaini

Re: [DISCUSS] Revisiting the quality testing epic scope

2021-01-21 Thread Scott Andreas
ugs in scope and get tests reliably green. But it feels good to be this close. – Scott ____________________ From: Benjamin Lerer Sent: Tuesday, January 19, 2021 1:54 AM To: dev@cassandra.apache.org Subject: Re: [DISCUSS] Revisiting the quality testing epic scope Thank you

Re: [DISCUSS] Revisiting the quality testing epic scope

2021-01-19 Thread Benjamin Lerer
Thank you for your reply, Scott. My understanding is that Alexander is moving forward on CASSANDRA-15580 (Repair) and that Andres is focussing with Caleb on the tickets of CASSANDRA-15579 (Distributed Read/Write Path). The biggest unknown here seems to be CASSANDRA-16262 as you mentioned. Regard

Re: [DISCUSS] Revisiting the quality testing epic scope

2021-01-16 Thread Scott Andreas
Thanks for raising the question, Benjamin! Notes on a few tickets inline below. Non-Blocking: – CASSANDRA-15537 Local Read/Write Path: Upgrade and Diff Test I think it’s reasonable to consider this ticket complete. Yifan and others have worked to execute several dozen diff tests and while I’m sur