Hi Sankalp, Thanks for bringing this up. At the very minimum, I hope we have regression tests for the specific issues we have fixed.
I personally think, the project should focus on building a comprehensive test suite. However, some of these issues can only be detected at scale. We need users to test* C* in their environment for their use-cases. Ideally these folks stand up large clusters and tee their traffic to the new cluster and report issues. If we had an automated test suite that everyone can run at a large scale that would be even better. Thanks, Dinesh * test != starting C* in a few nodes and looking at logs. > On May 6, 2020, at 10:11 AM, sankalp kohli <kohlisank...@gmail.com> wrote: > > Hi, > I want to share some of the serious issues that were found and fixed in > 3.0.x. I have created this list from JIRA to help us identify areas for > validating 4.0. This will also give an insight to the dev community. > > Let us know if anyone has suggestions on how to better use this data in > validating 4.0. Also this list might be missing some issues identified > early on in 3.0.x or some latest ones. > > Link: https://tinyurl.com/30seriousissues > > Thanks, > Sankalp --------------------------------------------------------------------- To unsubscribe, e-mail: dev-unsubscr...@cassandra.apache.org For additional commands, e-mail: dev-h...@cassandra.apache.org
