svn commit: r936722 - in /websites/staging/nifi/trunk/content: ./ development/release-guide.html

[buildbot]

Author: buildbot
Date: Mon Jan 19 04:16:26 2015
New Revision: 936722

Log:
Staging update by buildbot for nifi

Modified:
    websites/staging/nifi/trunk/content/   (props changed)
    websites/staging/nifi/trunk/content/development/release-guide.html

Propchange: websites/staging/nifi/trunk/content/
------------------------------------------------------------------------------
--- cms:source-revision (original)
+++ cms:source-revision Mon Jan 19 04:16:26 2015
@@ -1 +1 @@
-1652900
+1652901

Modified: websites/staging/nifi/trunk/content/development/release-guide.html
==============================================================================
--- websites/staging/nifi/trunk/content/development/release-guide.html 
(original)
+++ websites/staging/nifi/trunk/content/development/release-guide.html Mon Jan 
19 04:16:26 2015
@@ -96,7 +96,7 @@
 
       <div class="jumbotron">
         <div id="content">
-          <h1 id="wzxhzdk1-apache-nifi-release-guide"><img alt="NiFi logo" 
style="float: right" src="/images/niFi-logo-horizontal.png" /> Apache NiFi 
Release Guide</h1>
+          <h1 id="wzxhzdk2-apache-nifi-release-guide"><img alt="NiFi logo" 
style="float: right" src="/images/niFi-logo-horizontal.png" /> Apache NiFi 
Release Guide</h1>
 <p>The purpose of this document is to capture and describe the steps involved 
in producing 
 an official release of Apache NiFi.  It is written specifically to someone 
acting in the
 capacity of a <a 
href="http://www.apache.org/dev/release-publishing.html#release_manager";>Release
 Manager</a> (RM).  </p>
@@ -165,18 +165,23 @@ The following is a list of the sorts of
 <p>Create a JIRA ticket for the release tasks and use that for the commit 
messages.  For example we'll consider NIFI-XYZ as our ticket.</p>
 <p>Create the next version in JIRA if necessary so develop work can continue 
towards that release.</p>
 <p>Create new branch off develop named after the JIRA ticket or just use the 
develop branch itself</p>
-<p>Ensure your maven settings have been updated.</p>
-<p>Verify that Maven has sufficient heap space to perform the build tasks.  
Some of them consume a surprising large amount of space.
-    These settings have been shown to work <code>MAVEN_OPTS="-Xms1024m 
-Xmx3076m -XX:MaxPermSize=256m"</code></p>
+<p>Verify that Maven has sufficient heap space to perform the build tasks.  
Some plugins and parts of the build 
+consumes a surprisingly large amount of space.  These settings have been shown 
to 
+work <code>MAVEN_OPTS="-Xms1024m -Xmx3076m -XX:MaxPermSize=256m"</code></p>
 <p>Ensure your settings.xml has been updated as shown below.  There are other 
ways to ensure your key is available for signing as well</p>
-<p><code>&lt;profile&gt;
-            &lt;id&gt;signed_release&lt;/id&gt;
-            &lt;properties&gt;
-                &lt;mavenExecutorId&gt;forked-path&lt;/mavenExecutorId&gt;
-                &lt;gpg.keyname&gt;YOUR GPG KEY ID HERE&lt;/gpg.keyname&gt;
-                &lt;gpg.passphrase&gt;YOUR GPG PASSPHRASE 
HERE&lt;/gpg.passphrase&gt;
-            &lt;/properties&gt;
-        &lt;/profile&gt;</code></p>
+<blockquote>
+<div class="codehilite"><pre>     <span class="nt">&lt;profile&gt;</span>
+        <span class="nt">&lt;id&gt;</span>signed_release<span 
class="nt">&lt;/id&gt;</span>
+        <span class="nt">&lt;properties&gt;</span>
+            <span class="nt">&lt;mavenExecutorId&gt;</span>forked-path<span 
class="nt">&lt;/mavenExecutorId&gt;</span>
+            <span class="nt">&lt;gpg.keyname&gt;</span>YOUR GPG KEY ID 
HERE<span class="nt">&lt;/gpg.keyname&gt;</span>
+            <span class="nt">&lt;gpg.passphrase&gt;</span>YOUR GPG PASSPHRASE 
HERE<span class="nt">&lt;/gpg.passphrase&gt;</span>
+        <span class="nt">&lt;/properties&gt;</span>
+    <span class="nt">&lt;/profile&gt;</span>
+</pre></div>
+
+
+</blockquote>
         </div>
       </div>
         <div id="footer">