[svn.haxx.se] · SVN Dev · SVN Users · SVN Org · TSVN Dev · TSVN Users · Subclipse Dev · Subclipse Users · this month's index

Re: Change to Subversion PMC rule for approving backports

From: Julian Foad <julianfoad_at_apache.org>
Date: Tue, 3 Sep 2019 12:37:25 +0100

The proposed change now looks like this:

old:
  http://subversion.apache.org/docs/community-guide/releasing.html#release-stabilization-how-many-votes

new:
  http://subversion-staging.apache.org/docs/community-guide/releasing.html#release-stabilization-how-many-votes

[[[
-<p>A change is approved if it receives three +1s and no vetoes. (Only
-binding votes count; see above.)</p>
+<p>For a non-LTS ("regular") release line, a change is approved if it
+receives one binding +1 vote and no vetoes.</p>
 
-<p>Notwithstanding the above, a change that affects only areas that are not
+<p>For an LTS release line, a change that affects core code or the build
+system is approved if it receives three binding +1s and no vetoes.
+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
]]]

committed:
  http://svn.apache.org/r1866313

- Julian
Received on 2019-09-03 13:37:27 CEST

This is an archived mail posted to the Subversion Dev mailing list.

This site is subject to the Apache Privacy Policy and the Apache Public Forum Archive Policy.