The Netty and JDK upgrades are enticing however given we have Accord, stabilizing this release and avoiding compounding variables. By freezing underlying libraries we ensure consensus issue are (relatively) easier to diagnose. EOL concerns are equally valid - could library upgrades follow quickly in next minor release vs waiting for major release?
On Sun, Oct 25, 2026 at 3:54 PM Dmitry Konstantinov <[email protected]> wrote: > I suppose we need to fix the serialization compatibility - > https://issues.apache.org/jira/browse/CASSANDRA-21811 > We also have https://issues.apache.org/jira/browse/CASSANDRA-21728 > with 6.0-alpha3 as a fixed version... > > I have the following things which I would like to be included to 6.0 (if > 6.0-beta1 means only bug fixing): > https://issues.apache.org/jira/browse/CASSANDRA-21175 - Upgrade to Netty > 4.2; taking in account that July 1st, 2027 as EoL announced for Netty 4.1 > https://issues.apache.org/jira/browse/CASSANDRA-21171 - JDK25 support; > because JDK21 is already quite old + a switch after 6.0 release would be > much more expensive to implement > https://issues.apache.org/jira/browse/CASSANDRA-21460 - Support BTI for > cursor compaction > https://issues.apache.org/jira/browse/CASSANDRA-20333 - Reduce > DecayingEstimatedHistogramReservoir update cost; optionally but it gives a > nice performance improvement > > > > On Sun, 25 Oct 2026 at 16:10, Mick <[email protected]> wrote: > >> >> >> On Thu, 22 Oct 2026, at 5:55 PM, Ekaterina Dimitrova wrote: >> > 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. >> >> >> Yup, if you have any critical tickets that need to go in before our first >> beta remember to add `6.0-alpha` to their fixVersion, with regards to our >> establish release guidelines Ekaterina points out. >> >> This usage is also described under its version description: >> https://issues.apache.org/jira/projects/CASSANDRA?selectedItem=com.atlassian.jira.jira-projects-plugin%3Arelease-page&status=unreleased >> >> "Placeholder for blockers to 6.0-beta1 (unresolved tickets only)" >> >> Currently we two tickets blocking any 6.0-beta1 >> >> I'm keen to cut 6.0-alpha3 and 5.0.10 asap. >> >> > > -- > Dmitry Konstantinov >
