Great discussion to have, thanks Stefan! Alpha vs Beta - we need to look into our currently 6.0 open tickets probably against our requirements outlined here - https://cwiki.apache.org/confluence/plugins/servlet/mobile?contentId=132320437#content/view/132320437
In the meantime, I encourage everyone knowing about something not yet in a ticket - please open one so the community gets the right visibility. Best regards, Ekaterina On Thu, 22 Oct 2026 at 10:13, Patrick McFadin <[email protected]> wrote: > I feel like we are ready for a beta 1 since we are just bug-finding now. > It's an improved signal to the community to look more earnestly at > production workloads. > > For me, I have one data loss bug and a couple of TCM bug fixes found in > testing. Working on merging those soon. > > Patrick > > On Thu, Oct 22, 2026 at 4:36 AM Štefan Miklošovič <[email protected]> > wrote: > >> I would like to know what is the plan for the next quarterly release >> of Cassandra 6.0. >> >> We are after two alphas, the next release, naturally, is either yet >> one more alpha (6.0-alpha3) or beta1 (6.0-beta1). >> >> 6.0-alpha2 was released on 7th August 2026, so the next one should be >> around mid November. >> >> From my side, I am working on the stabilisation of Zstd dicts, adding >> fuzz tests and so on, we also identified some small issues with >> constraints de/ser in TCM, all of this should be done until then. >> >> Other than that, I think there are still some improvements in BTI >> cursor compactions to be added (right? genuinely not sure, correct me >> if I am wrong). >> >> Are other areas of the code-based beta-ready or does it warrant yet >> one more alpha? >> >> How do you feel about this? alpha3 or beta1? >> >> Regards >> >
