Hi, I would like to take the opportunity to discuss as well the possibility of adding the subprojects to this release cadence. I think the entire Apache Cassandra ecosystem would benefit from that consistent and predictable release schedules, and not only the main project.
I see potential benefits from this for the subprojects other than the one discussed in this thread: - IMHO, this show consistency and care for our users. - The subprojects are also seen as first class citizens in the Apache Cassandra ecosystem. I understand that different subprojects are at different stages of releases, (aka, sidecar is under heavy development. Analytics is still fighting with some issues to release its 0.2.0 version, etc), that may (or may not) make them not suitable for the general release cadence that we all agree upon, but at least, aligning with that should be the North Star for everyone. Regards, Bernardo > On Nov 13, 2025, at 7:22 AM, Josh McKenzie <[email protected]> wrote: > >> If we decided that Dec 1 is the cutoff, how would that work? > What do you mean? I don't understand the question =/ > > To the question about user confusion, I think Jeremiah covers it. 6.0-beta1 > and 7.0-alpha1 clearly communicate the different scopes and levels of > maturity of each release cycle even were they to be made available > concurrently. > > On Wed, Nov 12, 2025, at 2:35 PM, Patrick McFadin wrote: >> Imagining how this would work. If we decided that Dec 1 is the cutoff, how >> would that work? >> >
