cassandra-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Apache Wiki <>
Subject [Cassandra Wiki] Update of "HowToContribute" by JonathanEllis
Date Wed, 06 Jul 2011 17:20:10 GMT
Dear Wiki user,

You have subscribed to a wiki page or wiki category on "Cassandra Wiki" for change notification.

The "HowToContribute" page has been changed by JonathanEllis:

+ == Overview ==
+  1. Pick an issue to work on.  If you don't have a specific [[|itch
to scratch]], some possibilities are marked with [[|the
low-hanging fruit label]] in JIRA.
   1. Read the relevant parts of ArchitectureInternals; watching
will probably also be useful
   1. Check if someone else has already begun work on the change you have in mind in the [[|issue
   1. If not, create a ticket describing the change you're proposing in the issue tracker
@@ -98, +100 @@

  Got commit access?  Outstanding!  Here are the conventions we follow.
  Commit messages take the form of
  patch by <author>; reviewed by <committer> for CASSANDRA-<ticket>
  When committing to multiple branches, start with the most-stable and merge forwards.  For
instance, if you had a fix to apply to 0.6, 0.7, and trunk, you would first commit to 0.6.
 Then, from your 0.7 branch checkout, you would run "svn merge",
resolve any conflicts, and commit.  Then, from your trunk checkout, you would run "svn merge", again resolve conflicts,
and commit.
  See for an in-depth explanation
of why fixes should be merged forwards from more-stable branches, rather than backported from

View raw message