This is awesome Josh!! Thanks a lot for putting this all together. I love what I’ve read.
If I had to nitpick, I’d like for it to have a little bit more attention to the actual unification of builds. What about adding some details on the “Proposed Changes” section about the current building scripts and how they are going to be merged? Right now, they are basically both copy pasta from the main Cassandra build scripts. I don’t think we should fix that copy pasta on this effort by any means, but we are at least merging those two copy pastas (sidecar and analytics) into one copy pasta (ecosystem). Having it in this CEP turns the actual building process into a first class citizen, and rightfully so in my opinion. Also, I guess that while this change does take place, new features and additions will be frozen to the soon to be deprecated repositories. But, what about security fixes, bugs, etc? Do we have a plan to address them while doing this merge? (Just in case it drags in time). Other than that, eager to see the artifacts 0.6.0 released from here. :-) Thanks! Bernardo El El mar, 23 jun 2026 a las 1:10 a. m., Josh McKenzie <[email protected]> escribió: > CEP Draft: > https://cwiki.apache.org/confluence/pages/viewpage.action?pageId=435028087 > > DISCUSS ML thread on the topic that led to the CEP: > https://lists.apache.org/thread/slpn99x51yxmrhg9oncb5olq9kjqj5js > > From the CEP: > > This CEP proposes consolidating the two separate Apache Cassandra > companion repositories - cassandra-analytics > <https://github.com/apache/cassandra-analytics> and cassandra-sidecar > <https://github.com/apache/cassandra-sidecar> - into a single new > repository, *cassandra-ecosystem*, and establishing the versioning, > release, API-stability, and CI practices needed to make co-location safe > for existing production consumers. > > > We had some solid discussion and a pretty clear consensus on the > direction. The CEP contains more opinionated language and proposals around > moving from our hybrid JIRA + github project management to pure github. The > API compatibility contract and release/versioning model are also new (we > talked about them on the DISCUSS thread but new to the projects) so > definitely curious to hear what everyone thinks now that it's more fleshed > out in the CEP. > > And sorry it ended up being longer Ekaterina :); once I started digging > into the nuts and bolts of it there's a lot of ground to cover. I really > appreciate all the engagement on the previous DISCUSS thread and am looking > forward to more of that same energy here. > > ~Josh >
