Hi Jeremiah, My personal view is that work to modularise the codebase should be tied to specific use cases. If improved testing is the purpose of this work, I think it would help to include those improved tests that you plan to support as goals for the CEP.
If on the other hand some of this work is primarily intended to enable certain features, I personally think it would be preferable to tie them to those features - perhaps with their own CEP? From: Jeremiah Jordan <jeremiah.jor...@gmail.com> Date: Friday, 22 October 2021 at 16:24 To: Cassandra DEV <dev@cassandra.apache.org> Subject: [DISCUSS] CEP-18: Improving Modularity Hi All, As has been seen with the work already started in CEP-10, increasing the modularity of our subsystems can improve their testability, and also the ability to try new implementations without breaking things. Our team has been working on doing this and CEP-18 has been created to propose adding more modularity to a few different subsystems. https://cwiki.apache.org/confluence/display/CASSANDRA/CEP-18%3A+Improving+Modularity CASSANDRA-17044 has already been created for Schema Storage changes related to this work and more JIRAs and PRs are to follow for the other subsystems proposed in the CEP. Thanks, -Jeremiah Jordan
