Versions Compared

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

...

  1. To create your own CEP, click on 

    Create from template
    templateName96600065
    templateId96600065
    titleCEP-NEXT: Insert Title Here
    buttonLabelCreate CEP
    .
    If you don't have permission, please send an email with your Wiki ID to dev@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".

  2. Fill in the sections as described above.

  3. 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.

  4. As the CEP nears completion, consider adding any additional design documentation (see below) to the CEP, especially where it summaries working group discussions.

  5. 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.

  6. 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

CEPComment

CEP-1: Apache Cassandra Management Process(es)

Sent emails to Dev discussion group.

CEP-2: Kubernetes OperatorEmails periodically sent to dev list. SIG meetings held periodically.

CEP-7: Storage Attached Index (gdoc)

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 implementationsAccepted
CEP-15: General Purpose Transactions
CEP-16: Auth Plugin Support for CQLSH
CEP-17: Add support for PEM based key material for SSLUnder discussion

CEPs in draft

...