The "Process" field in the following tables documents what development model is accepted by that project, either Review-Then-Commit or Commit-Then-Review. For RTC model the changes are first proposed in the
STATUS.txt file in the root of the project and have to gain at least 3 "
+1" votes before being applied. The project members have agreed on several exceptions from the RTC rule (documented below).
- Tomcat 3.0.x
- Tomcat 3.1.x
- Tomcat 3.2.x
- Tomcat 3.3.x
- Tomcat 4.0.x
- Tomcat 4.1.x
- Tomcat 5.0.x
- Tomcat 5.5.x
The following are exceptions to the Review-Than-Commit rule.
- Changes to the documentation (including Javadoc) are C-T-R.
- Allow C-T-R for trivial fixes to English messages that are in resource files and those that are inline in the code. This includes typos and rephrasing, but does not include adding/removing message parameters.
- Allow C-T-R for any fixes for non-English resource files. The files must use 7-bit characters only. Other symbols must be escaped with \u, as does native2ascii.
- Require some indication in the commit message for code that usually is covered by RTC, that this commit was done using C-T-R rule.
- The versions that were moved to the archive are C-T-R.