Versions Compared

Key

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

...

This page describes a proposed Cassandra Enhancement Proposal (CEP) process for proposing a major change to Cassandra.

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.


Table of Contents

Purpose

The purpose of an CEP is to inform and involve both the user and dev communities in major improvements to Cassandra, from as early on in the development process as possible.

...

Here is the process for making a CEP:

  1. Click 

    To create your own CEP, click on 

    Create from template
    templateName96600065
    templateId96600065
    title

    CIP

    CEP-NEXT: Insert Title Here
    buttonLabelCreate

    CIP

    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. When you feel you have a finalized proposal 

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

...