Author: danielsh
Date: Tue Jun 28 16:25:53 2011
New Revision: 1140709
URL: http://svn.apache.org/viewvc?rev=1140709&view=rev
Log:
* docs/community-guide/releasing.part.html
(custom-releases): Mention our branching policy.
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=1140709&r1=1140708&r2=1140709&view=diff
==============================================================================
--- subversion/site/publish/docs/community-guide/releasing.part.html (original)
+++ subversion/site/publish/docs/community-guide/releasing.part.html Tue Jun 28
16:25:53 2011
@@ -320,7 +320,9 @@ confusion caused by your custom release.
<p>Second, consider creating a branch in the public Subversion
repository to track your changes and to potentially allow your custom
-changes to be merged into mainline Subversion.</p>
+changes to be merged into mainline Subversion. (If you do not have it
+already, <a href="<!--#echo var="GUIDE_ROLES_PAGE" -->#lightweight-branches"
+>ask for commit access</a>.)</p>
<p>Third, if your custom release is likely to generate bug reports
that would not be relevant to mainline Subversion, please stay in
