With the feature freeze for 4.0 getting a little closer to its end, and after Scott's NGCC presentation on how Cassandra can be better at moving forward, I'm keen to bring up the idea of a "Cassandra Enhancement Proposal" (CEP) process.
Big changes in the past have not always been as transparent and clear as they could have been in their initial stages. For example they have been written up in jira tickets, in a way that becomes quite difficult to unpack afterwards the difference between the initial proposal and the actual agreed upon design+implementation, or a worse example, ideas that were largely fleshed out behind closed (or hidden) doors and then only implemented in public. A year ago a rough CEP (CIP) draft was put together, which was largely just a copy of what Kafka and Spark do. Now Scott has done a bit of work in formulating this into something that is higher-level and less design-document-heavy. https://cwiki.apache.org/confluence/pages/viewpage.action?pageId=95652201 Are they edits to the CEP, or its template, that folk would like to see? Are we ready for such a CEP process? Can we just take the jump and request that all new feature tickets link to a CEP? regards, Mick --------------------------------------------------------------------- To unsubscribe, e-mail: dev-unsubscr...@cassandra.apache.org For additional commands, e-mail: dev-h...@cassandra.apache.org
