Author: buildbot
Date: Fri Mar 7 17:05:47 2014
New Revision: 900471
Log:
Staging update by buildbot for accumulo
Modified:
websites/staging/accumulo/trunk/content/ (props changed)
websites/staging/accumulo/trunk/content/releasing.html
Propchange: websites/staging/accumulo/trunk/content/
------------------------------------------------------------------------------
--- cms:source-revision (original)
+++ cms:source-revision Fri Mar 7 17:05:47 2014
@@ -1 +1 @@
-1575316
+1575325
Modified: websites/staging/accumulo/trunk/content/releasing.html
==============================================================================
--- websites/staging/accumulo/trunk/content/releasing.html (original)
+++ websites/staging/accumulo/trunk/content/releasing.html Fri Mar 7 17:05:47
2014
@@ -155,9 +155,27 @@ out to all of the mirrors.</p>
<h2 id="update-the-website">Update the Website</h2>
<p>After a successful vote, this website needs to be updated with the new
artifacts. The downloads page should
be updated with the new information. A new minor release should replace the
previous minor release in the major
-version. The Javadocs should be updated, with special care being taken to
ensure that Javadocs are <a
href="http://www.kb.cert.org/vuls/id/225657";>patched</a> <strong>before</strong>
+version. The user manual should also be updated if changes were made to it.</p>
+<h3 id="javadocs">Javadocs</h3>
+<p>Javadocs are a little convoluted to update. First off, be sure that the
javadocs are <a href="http://www.kb.cert.org/vuls/id/225657";>patched</a>
<strong>before</strong>
uploading as long as Java 6 is the version targeted by Accumulo (with greater
than Java 7u21 being used once we
-switch to Java 7). The user manual should also be updated if changes were made
to it.</p>
+switch to Java 7). Despite the javadocs not appearing in the CMS SVN
repository, this is
+where they need to be committed using <a
href="http://www.apache.org/dev/cmsref#extpaths";>extpaths</a>. You can follow
the steps below to update
+the javadocs.</p>
+<ol>
+<li>Extract javadocs from binary tarball from the release</li>
+<li>Run the vulnerability-check tool</li>
+<li>Checkout the <a
href="https://svn.apache.org/repos/asf/accumulo/site/trunk";>Accumulo CMS
repository</a></li>
+<li>Copy the entire apidocs folder in the appropriate version folder in the
CMS repository (e.g. content/1.5/apidocs for a 1.5 release)</li>
+<li>Remove the appropriate entry from content/extpaths.txt (e.g. 1.5/apidocs
for 1.5 release)</li>
+<li>Commit the changes</li>
+<li>Wait for the staging build to complete, and then publish the changes to
the production site.</li>
+<li>Remove the apidocs folder you created from the CMS repository (e.g.
content/1.5/apidocs)</li>
+<li>Re-add the entry in extpaths.txt that you previously removed.</li>
+<li>Commit the changes</li>
+<li>Wait for the staging build to complete, and then publish the changes to
the production site again.</li>
+<li>Verify that javadocs have been updated on the production site</li>
+</ol>
<h2 id="references">References</h2>
<p>Some good references that explain a few things:</p>
<ul>
