Operators Developers Contributors Reference
Sidebar updates per section — preview limitation
Apache Cassandra

Patches and Review

This section covers the full lifecycle of a code contribution to Apache Cassandra: from finding something to work on through patch submission, code review, and committing.

In This Section

Contributing Code Changes

The contribution workflow — choosing what to work on, creating a patch, and submitting it for review.

Code Style

Java coding conventions, import ordering, exception handling, and license compliance.

Review Checklist

What reviewers look for when evaluating patches.

How to Commit

For committers: the merge workflow across release branches, including submodule handling.

Quick Reference

  1. Find or create a JIRA ticket

  2. If you have not used ASF JIRA before, start with the JIRA quickstart.

  3. Fork apache/cassandra and create a feature branch

  4. Make your changes following the code style guidelines

  5. Write tests (see Testing)

  6. Submit a GitHub pull request, or attach a patch to the JIRA ticket if the workflow calls for it

  7. In JIRA, click Submit Patch so the ticket moves to Patch Available and reviewers know the patch is ready

  8. Address review feedback and iterate until the patch receives a +1

See Contributing Code Changes for the full workflow.