THIS IS A TEST INSTANCE. ALL YOUR CHANGES WILL BE LOST!!!!
...
A CEP needs to attract a Shepherd, a PMC member Cassandra Committer committed to guiding the proposal through the process. Although a shepherd may delegate or work with other committers, they are ultimately responsible for the success or failure of a CEP. Responsibilities include, but are not limited to:
...
Here is the process for making a CEP:
(Optional): For work that is highly fluid and not yet ready for hardening in a wiki article nor broad dev list announcement, create a gdoc with the CEP template and add a link under the "CEP's in draft". This area is recommended for things that are nascent but with a high degree of certainty of eventual dev list proposal of a CEP.
To create your own CEP, click on
.Create from template templateName 96600065 templateId 96600065 title CEP-NEXT: Insert Title Here buttonLabel Create CEP
If you don't have permission, please send an email with your Wiki ID todev@cassandra.apache.organd request permission. Also add an entry to the table CEPs under discussion.Take the next available CEP number and give your proposal a descriptive heading. e.g. "CEP 1: Proposing an Apache Cassandra Management process".- Fill in the sections as described above.
- Start a [DISCUSS] thread on the Apache mailing list. Please ensure that the subject of the thread is of the format [DISCUSS] CEP-{your CEP number} {your CEP heading} The discussion should happen on the mailing list not on the wiki since the wiki comment system doesn't work well for larger discussions. In the process of the discussion you may update the proposal. You should let people know the changes you are making.
- As the CEP nears completion, consider adding any additional design documentation (see below) to the CEP, especially where it summaries working group discussions.
- Once the proposal is finalized call a [VOTE] to have the proposal adopted. These proposals are more serious than code changes and more serious even than release votes. The criteria for acceptance is lazy is consensus (3 binding +1 votes and no binding vetoes). The vote should remain open for 72 hours.
- Please update the CEP wiki page, and the index below, to reflect the current stage of the CEP after a vote. This acts as the permanent record indicating the result of the CEP (e.g., Accepted or Rejected). Also report the result of the CEP vote to the voting thread on the mailing list so the conclusion is clear.
...
List of CEPs
Adopted CEPs
CEPs under discussion
| CEP | Comment |
|---|---|
| CEP-2: Kubernetes Operator | Emails periodically sent to dev list. SIG meetings held periodically. |
| CEP-12: Diagnostic Events in virtual tables | Sent emails to Dev discussion group. | Work tracked under CASSANDRA-14395.
...
| CEP-24: Password validation and generation | Sent emails to Dev discussion group. |
CEPs in draft
| gdoc link | Comment |
|---|---|
| CEP-4: EXPLAIN | Not discussed yet |
| CEP-5: JOINs (copy of gdoc w/permissions changed) | Not discussed yet |
| CEP-6: Change Data Capture v2 | Not discussed yet |
| CEP-27: Generic API for Internal Data Collections Exposure | dev-list: Discussion |
Dormant / Inactive CEPs
| CEP | Comment |
|---|---|
Discarded CEPs
| CEP | Comment |
|---|---|
| CEP-18: Improving Modularity | CEP withdrawn, discussion ended up with wanted to consider each ticket on their own, rather than considering them as a whole in a CEP. See email thread on dev@ discussion group. |
| CEP-23: Enhancement for Sparse Data Serialization | CEP withdrawn, discussion indicated that CEP was not the proper form for the change. Change can not be made within the confines of the the outlined CEP. |