svn commit: r899879 - in /websites/staging/accumulo/trunk/content: ./ releasing.html

[bu...@apache.org]

Author: buildbot
Date: Mon Mar  3 16:48:08 2014
New Revision: 899879

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 Mon Mar  3 16:48:08 2014
@@ -1 +1 @@
-1572413
+1573608

Modified: websites/staging/accumulo/trunk/content/releasing.html
==============================================================================
--- websites/staging/accumulo/trunk/content/releasing.html (original)
+++ websites/staging/accumulo/trunk/content/releasing.html Mon Mar  3 16:48:08 2014
@@ -95,8 +95,8 @@
 <h2 id="setup">Setup</h2>
 <p>There are number of things that are required before attempting to build a release.</p>
 <ol>
-<li>Use gpg-agent, be sure to increase the gpg-agent cache timeout (via .gnupg/gpg-agent.conf) to ensure that the agent doesn't require re-authentication mid-build as it will cause things to fail. For example, you can add <code>default-cache-ttl 6000</code> to increase the timeout from the default of 10 minutes to over an hour. If you do not have a GPG key, reference the very thorough <a href="https://www.apache.org/dev/release-signing">ASF release signing documentation</a></li>
-<li>Make sure the system you're using is able to creation RPMs and DEBs.</li>
+<li>Use gpg-agent, and be sure to increase the gpg-agent cache timeout (via .gnupg/gpg-agent.conf) to ensure that the agent doesn't require re-authentication mid-build, as it will cause things to fail. For example, you can add <code>default-cache-ttl 6000</code> to increase the timeout from the default of 10 minutes to over an hour. If you do not have a GPG key, reference the very thorough <a href="https://www.apache.org/dev/release-signing">ASF release signing documentation</a>.</li>
+<li>Make sure the system you're using is able to create RPMs and DEBs.</li>
 <li>Ensure that you're using the correct major release of Java (check javadoc too).</li>
 <li>Ensure that you're building Apache Accumulo with a username that has the same name as your Apache ID (this is due to
    the maven-release-plugin and staging the release candidate).</li>
@@ -117,26 +117,26 @@ it was agreed upon to omit issues from p
 <p>You should use the provided script assemble/build.sh to create the release candidate. This script is
 desirable as it activates all necessary maven profiles in addition to verifying that certain preconditions
 are met, like RPM signing availablilty and the ability to sign files using GPG. The --test option can 
-be used as a dry-run to creating a release candidate. The --create-release-candidate option should be 
-provided to create the actual release candidate.</p>
+be used as a dry run for creating a release candidate. The --create-release-candidate option should be 
+used to create the actual release candidate.</p>
 <p>When invoking build.sh with the --create-release-candidate option, the majority of the work will be performed
-by the maven-release-plugin, invoking release:clean, release:prepare, and release:perform. These will
+by the maven-release-plugin, invoking <em>release:clean</em>, <em>release:prepare</em>, and <em>release:perform</em>. These will
 guide you through choosing the correct versions. The default options provided should be what you choose.
-It is highly recommended that an 'RC' suffix is <em>not</em> appended to the release version the the plugin prompts
-you for as that will result in that version string being placed into the poms which then would require 
+It is highly recommended that an 'RC' suffix is <em>not</em> appended to the release version the plugin prompts
+you for, as that will result in that version string being placed into the poms, which then would require 
 voting to occur on artifacts that cannot be directly promoted. After the build.sh script finishes (this will 
 likely take at least 15 minutes, even on recent hardware), your current branch will be on the "next" version 
 that you provided to the release plugin.</p>
-<p>Likely, this process will actually fail because the maven-release-plugin is not configured to push to the 
-remote repository automatically, and thus, will fail; however, this is (semi-)expected. At this point, you
-should have a local git-tag for the release that you're creating. At this point, you should create a branch
+<p>This process is likely to fail because the maven-release-plugin is not configured to push to the 
+remote repository automatically; however, this is (semi-)expected. At this point, you
+should have a local git tag for the release that you're creating. You should create a branch
 from the tag that was made by the release plugin which includes the <em>-rcN</em> suffix. This way, the branch name 
-will correctly identify which release-candidate this is, while the contents of that tag will have the correct 
+will correctly identify which release candidate this is, while the contents of that tag will have the correct 
 versions in the pom.xml files. This also ensure that the <em>release:perform</em> goal of the release plugin will
 work as intended.</p>
-<p>One unwanted side-effect of this approach is that after creating this branch, but <em>before invoking <em>release:perform</em></em>,
+<p>One unwanted side-effect of this approach is that after creating this branch, but <em>before invoking release:perform</em>,
 you must edit the release.properties to add the <em>-rcN</em> suffix to the value of scm.tag. Otherwise, the release
-plugin will complain that it cannot find the branch for the release. A successful invocation of <em>mvn release:perform</em>,
+plugin will complain that it cannot find the branch for the release. With a successful invocation of <em>mvn release:perform</em>,
 a staging repository will be made for you on the <a href="https://repository.apache.org/index.html">ASF Nexus server</a> which you can log into with your ASF 
 credentials.</p>
 <p>After you log into Nexus, click on <em>Staging Repositories</em> in the <em>Build Promotion</em> toolbar on the left side of
@@ -145,19 +145,19 @@ you. At this point, you should inspect t
 them to be. When you're ready to present those artifacts for voting, you need to close that repository which
 will make it publicly available for other members to inspect.</p>
 <h2 id="vote">Vote</h2>
-<p>At this point, you should have a closed repository that's ready to vote on. Send a message to the <a href="mailto:dev@accumulo.apache.org">the dev
+<p>At this point, you should have a closed repository that's ready to vote on. Send a message to <a href="mailto:dev@accumulo.apache.org">the dev
 list</a> and get the ball rolling. If the vote ultimately fails, you delete
 the staged repository, clean up the branch you created (or wait until the release ultimately passes if you
 choose), and fix what needs fixing.</p>
 <p>If the vote passes, huzzah, you're almost done. All you need to do is to promote that stage repository
-using Nexus which you can do with the click of a button. These will trigger a process to get the release
+using Nexus which you can do with the click of a button. This will trigger a process to get the release
 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>
 uploading as long as Java 6 is the version targeted by Accumulo (with greater than Java 7u21 being used once we
-switch to Java7). The user manual should also be updated if changes were made to it.</p>
+switch to Java 7). The user manual should also be updated if changes were made to it.</p>
 <h2 id="references">References</h2>
 <p>Some good references that explain a few things:</p>
 <ul>