svn commit: r1163160 - /subversion/site/publish/docs/community-guide/releasing.part.html

[st...@apache.org]

Author: stsp
Date: Tue Aug 30 10:07:56 2011
New Revision: 1163160

URL: http://svn.apache.org/viewvc?rev=1163160&view=rev
Log:
* site/publish/docs/community-guide/releasing.part.html: Properly link to
   the section which explains release stabilisation, instead of telling
   readers to look "above" (which was wrong -- the section is actually
   further below).

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

Modified: subversion/site/publish/docs/community-guide/releasing.part.html
URL: http://svn.apache.org/viewvc/subversion/site/publish/docs/community-guide/releasing.part.html?rev=1163160&r1=1163159&r2=1163160&view=diff
==============================================================================
--- subversion/site/publish/docs/community-guide/releasing.part.html (original)
+++ subversion/site/publish/docs/community-guide/releasing.part.html Tue Aug 30 10:07:56 2011
@@ -131,8 +131,8 @@ building directly from the repository.</
 </h4>
 
 <p>When we want new features to get wide testing before we enter the
-formal stabilization period described above, we'll sometimes release
-alpha and beta tarballs.  There is no requirement to
+formal <a href="#release-stabilization">stabilization period</a>,
+we'll sometimes release alpha and beta tarballs.  There is no requirement to
 do any beta releases even if there were "alpha1", "alpha2", etc
 releases; we could just jump straight to "rc1".  However, there are
 circumstances where a beta can be useful: for example, if we're unsure