This page is definitely in-progress.
C-T-R mode is short for "Commit-then-Review". This is the standard development mode that we are in. It means that developers may commit patches to the development tree without the code/rules/etc being reviewed by other developers first. Typically HEAD/trunk is in C-T-R mode until a new release is approaching. We then switch to R-T-C mode (see below) for the final development up to release.
R-T-C mode is short for "Review-then-Commit". Non-trivial patches (see below) must be reviewed by developers before being committed into the development tree. This is typically done by opening a Bugzilla ticket, setting the Target Milestone to the correct release of the tree, then attaching the suggested patch to the ticket via the web interface. The patch is then [http://incubator.apache.org/learn/voting.html voted] upon, and if it is not vetoed, can be applied to the tree. Votes should generally be permitted to run for at least 24 hours to provide an opportunity for all concerned persons to participate regardless of their geographic locations.
Non-trivial patches include:
- documentation
- finishing off pre-existing T_ tests
- non-controversial non-semantic style changes (fixing indentation, adding comments, but not actual code)
- very simple, non-controversial, and absolutely safe bug fixes (i.e.: removing repetitive my() enclosing sections)
(TheoVanDinter)