Author: danielsh
Date: Fri Apr 12 13:47:28 2013
New Revision: 1467269
URL: http://svn.apache.org/r1467269
Log:
* docs/community-guide/releasing.part.html
(#release-branches): Add two steps.
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=1467269&r1=1467268&r2=1467269&view=diff
==============================================================================
--- subversion/site/publish/docs/community-guide/releasing.part.html (original)
+++ subversion/site/publish/docs/community-guide/releasing.part.html Fri Apr 12
13:47:28 2013
@@ -1124,6 +1124,18 @@ Release Manager creates it with the foll
A.B with the version you're preparing, eg. 1.3, or 2.0):</p>
<ul>
+<li><p>Review the <a href="/roadmap">Roadmap</a>. Should any of the
outstanding
+ items be addressed before branching?</p></li>
+<li><p>Do any tree-wide, mechanical changes. (Non-mechanical changes should
+ have happened earlier to allow for review.) This eases merging later.
+ Examples include
+ <a href="http://svn.apache.org/r1467191";>stripping trailing
whitespace</a>
+ and
+ <a href="http://svn.apache.org/r1460176";>code search and replace</a>.
+ (This is also a good time to do other periodical housekeeping tasks
+ such as
+ <a
href="http://www.red-bean.com/svnproject/contribulyzer/detail/http%253A%252F%252Fscan.coverity.com%252F.html";>static</a>
+ <a href="http://svn.apache.org/r1467261";>analysis</a>.)</p></li>
<li><p>Create the new release branch with a server-side copy:</p>
<pre>
svn cp ^/subversion/trunk \
