Author: danielsh
Date: Fri Aug 30 20:58:04 2019
New Revision: 1866172
URL: http://svn.apache.org/viewvc?rev=1866172&view=rev
Log:
* docs/community-guide/releasing.part.html
(#release-stabilization): Fix broken link.
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=1866172&r1=1866171&r2=1866172&view=diff
==============================================================================
--- subversion/site/staging/docs/community-guide/releasing.part.html (original)
+++ subversion/site/staging/docs/community-guide/releasing.part.html Fri Aug 30
20:58:04 2019
@@ -630,7 +630,7 @@ ASF's legal shield, whereas in backport
distinction. After all, if someone votes -1 on a change for a sound reason,
their accreditations don't matter; if their analysis is correct, the change
won't be backported. Likewise, if a change fails to receive <a
-href="release-stabilization-how-many-votes">the required number</a> of binding
+href="#release-stabilization-how-many-votes">the required number</a> of binding
+1 votes but has some non-binding +1 votes, that may help it be approved.</p>
<p>In other words, the purpose of the backport process is to ensure
