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

[buildbot]

Author: buildbot
Date: Mon Jan 19 04:11:09 2015
New Revision: 936719

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:11:09 2015
@@ -1 +1 @@
-1652896
+1652898

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:11:09 2015
@@ -162,7 +162,23 @@ The following is a list of the sorts of
 </pre></div>
 
 
-<p>Create a new branch based on a JIRA ticket for the release task</p>
+<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.
+  - 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>
+<ul>
+<li>Ensure your settings.xml has been updated as shown below.  There are other 
ways to ensure your key is available for signing as well</li>
+</ul>
+<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>
         </div>
       </div>
         <div id="footer">