Author: dsahlberg
Date: Mon Feb 23 06:54:19 2026
New Revision: 1931998

Log:
In site/staging:

Followup to 1931988, remove number of votes required for backports to regular
releases, since we don't use that type of release anymore.

* staging/docs/community-guide/releasing.part.html
  (#release-stabilization-how-many-votes): As above

Modified:
   subversion/site/staging/docs/community-guide/releasing.part.html

Modified: subversion/site/staging/docs/community-guide/releasing.part.html
==============================================================================
--- subversion/site/staging/docs/community-guide/releasing.part.html    Mon Feb 
23 06:45:02 2026        (r1931997)
+++ subversion/site/staging/docs/community-guide/releasing.part.html    Mon Feb 
23 06:54:19 2026        (r1931998)
@@ -678,15 +678,10 @@ it.</p>
     title="Link to this section">&para;</a>
 </h4>
 
-<p>For a <b>non-LTS ("regular") release line</b>,
-a change is approved if it receives <b>two +1s</b> and no vetoes.  (Only
+<p>A change is approved if it receives <b>three +1s</b> and no vetoes.  (Only
 binding votes count; see above.)</p>
 
-<p>For an <b>LTS release line</b>,
-a change is approved if it receives <b>three +1s</b> and no vetoes.  (Only
-binding votes count; see above.)</p>
-
-<p>Notwithstanding the above, for any release line, a change that
+<p>A change that
 affects only areas that are <b>not core code</b> (for example,
 tools/, packages/, bindings/, test scripts, etc.),
 and that does <b>not affect the build system</b>,

Reply via email to