> * Freeze cassandra-4.1 on may 1st >
A feature freeze on the release branch is always implied. And repeating, because it bugs me (and I just need to air it): we're talking about this because we have not achieved a stable trunk this dev cycle. The 4.0 branch has remained very close, but trunk not so. Reporting (with the help of Butler) and the Build Lead role has made significant improvements, and if you look through the tests reported as flakey in trunk, many cannot be blamed on the infrastructure problems or higher saturation levels of ci-cassandra.a.o (a higher rate of flakey still means they're flakey). I hope this helps reinforce and remind us about our efforts to get to a green CI. This includes both CI systems and all tests that run on each.
