THIS IS A TEST INSTANCE. ALL YOUR CHANGES WILL BE LOST!!!!
...
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.org
and 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 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.
...
CEPs under discussion
CEP | Comment | ||
---|---|---|---|
CEP-2: Kubernetes Operator | Emails periodically sent to dev list. SIG meetings held periodically. | ||
Sent email to Dev discussion group. Created slack channel: cassandra-sai | |||
CEP-9: Make SSLContext creation pluggable | Accepted, PR in review | CEP-11: Pluggable memtable implementations | Accepted |
CEP-15: General Purpose Transactions | |||
CEP-16: Auth Plugin Support for CQLSH | |||
CEP-17: Add support for PEM based key material for SSL | Under discussion |
CEPs in draft
gdoc link | Comment |
---|---|
CEP-3: Guardrails | Not discussed yet |
CEP-4: EXPLAIN | Not discussed yet |
CEP-5: JOINs | Not discussed yet |
CEP-6: Change Data Capture v2 | Not discussed yet |
CEP-8: Drivers Donation | Initial ML discussion |
CEP-13: Denylisting partitions | Initial ML discussion |
...