The issue is filed as https://issues.apache.org/jira/browse/CASSANDRA-21893 - it's tagged against 6.0-alpha
I'll get the patch up in a few hours - it adds a footer to the existing serialization for partition update blobs. It should fall back gracefully to the current format even for people who are running existing alphas (when I posted originally I wasn't certain I would include that, but I think it is worth it). I would like to get it in before cutting a beta, but it could be in the first beta. Jon On Mon, Nov 16, 2026 at 9:29 AM Bernardo Botella < [email protected]> wrote: > Hi all! > > I don’t think we landed on any actual decision here right? > > > After taking a look at the issues tagged on the link posted by Stefan, I > see how we can either decide on a new alpha or a new beta. > > I’d like to make the case for 6.0-beta1, along the lines of what Patrick > said earlier. We’re mostly finding bugs at this point, and a beta is what > gets people to run 6.0 against real workloads. > > Here’s where the tickets tagged 6.0-alpha stand: > > - CASSANDRA-21855 (CMS deadlock) and CASSANDRA-21340 (GROUP BY > returning incomplete results) have patches available > - CASSANDRA-21755 (STARTUP options exposed before auth) is in progress > - CASSANDRA-21811 (ClusterMetadata backward compatibility) and > CASSANDRA-21728 (Accord INSERT with a default TTL) are still open; per the > comment on 21811, Benedict has a fix > > Jon, I don’t see the Paxos serialization issue you described on that list > yet. If it needs to go in before beta, could you tag it 6.0-alpha so it’s > tracked with the rest? On the format concern itself, the lifecycle doc > still allows format changes during beta “if necessary to resolve issues > identified during testing”. So I don’t think it has to keep us in alpha, as > long as the fix can still read data written by beta1. Does that seem doable > for this one? > > My main concern with another alpha is pushing a potential 6.0 release for > yet another quarter and keeping alive the feeling that Cassandra releases > just take forever. > > Thoughts? > > Bernardo > > > ------------------------------ > *From: *Štefan Miklošovič via dev <[email protected]> > *Date: *Wednesday, 4 November 2026 at 09:31 > *To: *[email protected] <[email protected]> > *Cc: *Štefan Miklošovič <[email protected]> > *Subject: *Re: [DISCUSS] Next quarterly release of 6.0 - alpha3 or beta1? > > Please mark your tickets to-be-delivered by 6.0-alpha as already > suggested, currently it looks like this: > > https://issues.apache.org/jira/projects/CASSANDRA/versions/12356863 > > On Tue, Nov 3, 2026 at 7:17 PM Jon Haddad <[email protected]> wrote: > > > > Also in favor of another Alpha. > > > > I think cursor bti should be merged soon, and there's a handful of > follow ups for counters, cleanup, repair, and reads. > > > > Jon > > > > On Fri, Oct 30, 2026 at 10:13 AM Jon Meredith <[email protected]> > wrote: > >> > >> I have a couple of TCM related bugs I need to file JIRAS for. > >> > >> First is related to a deserialization exception for state stored in > system.paxos when using PaxosV2 that requires an extension to the > serialiation format. If the system.paxos entry gets reserialized under the > new PartitionUpdate format with the same ballot it rewrites with the same > USING TIMESTAMP and can cause a tear between the version column and the > serializer used for the mutation blob. > >> > >> Second is a deadlock that can occur on the cms node responsible for > creating cms snapshots. > >> > >> I'll try and get them filed in the next few days. > >> > >> Given the serialization change I'd prefer another alpha as the change > affects a common format used by Paxos v1 and v2. > >> > >> Jon > >> > >> > >> On Thu, Oct 29, 2026 at 7:32 PM Brandon Williams <[email protected]> > wrote: > >>> > >>> On Thu, Oct 29, 2026 at 7:31 PM Tejal Joshi Chakeres <[email protected]> > wrote: > >>> > > >>> > could library upgrades follow quickly in next minor release vs > waiting for major release? > >>> > >>> There have been upgrades in roughly half of the 4.x and 5.x minor > >>> releases so I would expect that to continue. > >>> > >>> Kind Regards, > >>> Brandon > >>> > >>> > >>> > >>> > > >>> > 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 >
