On 3/8/2010 2:00 PM, Konstantin Kolinko wrote:
I propose to relax our RTC policy and use CTR for the types of changes
listed below:
2010/3/8 Konstantin Kolinko<knst.koli...@gmail.com>:
1. We already have Commit-Then-Review for any documentation, including
JavaDoc and code comments.
Already decided. No need to vote.
+1 (Correct docs/javadocs require no RTC) Still saying +1
2. I think that we can have C-T-R for any svn metadata (svn:
properties), as those are not the code. I am +1.
Allow C-T-R for changes to svn properties:
[X] +1
[ ] 0
[ ] -1
3.
Allow C-T-R for any whitespace changes:
[X] +1
[ ] 0
[ ] -1
4.
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.
[X] +1
[ ] 0
[ ] -1
5. Any fixes for any translations.
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.
[X] +1
[ ] 0
[ ] -1
6.
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.
[ ] +1
[X] 0
[ ] -1
Other comments
I'm not worrying about this. If someone has the time and energy to fix
typos, docs - that is awesome.
-Tim
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscr...@tomcat.apache.org
For additional commands, e-mail: dev-h...@tomcat.apache.org
