Author: danielsh
Date: Fri Aug 30 22:01:09 2019
New Revision: 1866174
URL: http://svn.apache.org/viewvc?rev=1866174&view=rev
Log:
* docs/community-guide/releasing.part.html
(#release-stabilization-how-many-votes): Simplify.
Modified:
subversion/site/staging/docs/community-guide/releasing.part.html
Modified: subversion/site/staging/docs/community-guide/releasing.part.html
URL:
http://svn.apache.org/viewvc/subversion/site/staging/docs/community-guide/releasing.part.html?rev=1866174&r1=1866173&r2=1866174&view=diff
==============================================================================
--- subversion/site/staging/docs/community-guide/releasing.part.html (original)
+++ subversion/site/staging/docs/community-guide/releasing.part.html Fri Aug 30
22:01:09 2019
@@ -688,14 +688,12 @@ it.</p>
<p>A change is approved if it receives three +1s and no vetoes. (Only
binding votes count; see above.)</p>
-<p>There is a somewhat looser voting system for areas that are not
-core code, and that may have fewer experts available to review changes
-(for example, tools/, packages/, bindings/, test scripts, etc.). A
-change in these areas can go in with a +1 from a full committer or a
+<p>Notwithstanding the above, a change that affects only areas that are not
+core code (for example, tools/, packages/, bindings/, test scripts, etc.),
+and that does <em>not</em> affect the build system,
+can go in with a +1 from a full committer or a
partial committer for that area, at least one +0 or "concept +1" from
-any other committer, and no vetoes. (If a change affects the build
-system, however, it is considered a core change, and needs three
-+1's.)</p>
+any other committer, and no vetoes.</p>
<p>The goal is to get at least two
pairs of eyes on the change, without demanding that every reviewer
