Clone URL (Committers only):
https://cms.apache.org/redirect?new=anonymous;action=diff;uri=http://openoffice.apache.org/orientation%2Fdecision-making.mdtext
Bonnie Kim
Index: trunk/content/orientation/decision-making.mdtext
===================================================================
--- trunk/content/orientation/decision-making.mdtext (revision 1525182)
+++ trunk/content/orientation/decision-making.mdtext (working copy)
@@ -31,13 +31,13 @@
unnecessary and unproductive. We have a "time machine" called Subversion
that allows us to undo any changes to the product or website. So if a
Committer believes that a
change would be uncontroversial, and the change is reversible, then the
default approach is to go ahead make the change.
- 1. Terms that you might related to the above are:
[JFDI](http://www.urbandictionary.com/define.php?term=JFDI) and "assuming lazy
consensus".
+ 1. Terms that you might need to know related to the above are:
[JFDI](http://www.urbandictionary.com/define.php?term=JFDI) and "assuming lazy
consensus".
1. However, there are times where CTR is not appropriate and RTC is used.
This happens, for example, at the end of a release cycle, when we want to
carefully review
changes made to the product, in order to control the final quality before
the release. When we're in RTC mode, no changes are made to the code unless
first discussed and approved
on the mailing list.
- 1. A Committer can also voluntarily invocate a RTC on their own changes.
For example the Committer might be considering a change that of greater
significance. Maybe he would
+ 1. A Committer can also voluntarily invocate a RTC on their own changes.
For example the Committer might be considering a change that is of greater
significance. Maybe he would
value additional input, or technical review. Maybe the change is
controversial or require coordination. If CTR is not appropriate then one can
make a proposal and send it to
the dev mailing list.
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
