That’s how I understand the process, yes. Voting to accept the CEP just indicates that the broad strokes painted by the CEP are acceptable to the community, and a patch can be brought forward with the expectation that it will be accepted once it meets the other criteria for acceptance.
From: Benjamin Lerer <ble...@apache.org> Date: Thursday, 8 July 2021 at 10:59 To: dev@cassandra.apache.org <dev@cassandra.apache.org> Subject: [DISCUSS] Clarifying the CEP process Hi everybody, CEPs are now a required step for important changes to the Cassandra code base. Nevertheless, this process is new for all of us and beyond creating a CEP it seems a bit unclear what needs to be done to get the CEP approved. I will take as an example the CEP-9: Make SSLContext creation pluggable <https://cwiki.apache.org/confluence/display/CASSANDRA/CEP-9%3A+Make+SSLContext+creation+pluggable> that has been provided with a JIRA ticket ( CASSANDRA-16666 <https://issues.apache.org/jira/browse/CASSANDRA-16666> ) and a PR. Sumanth and Stefan both raised some high level concerns on the JIRA ticket. My understanding is that they should have been raised on the DISCUSSION thread. Once those concerns are addressed or discussed, I believe that if nobody raised more concerns we should trigger a VOTE. Is my understanding correct? What criteria should be met before we trigger VOTE? One other point of confusion is the agreement on the CEPs versus the agreement on the patch. Agreeing on the CEP in my opinion does not mean that we agree on the patch. As patch is not required before we agree on the CEP. Am I correct? Thanks in advance for your feedback.
