You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@nifi.apache.org by bu...@apache.org on 2015/01/19 05:14:16 UTC
svn commit: r936721 - in /websites/staging/nifi/trunk/content: ./
development/release-guide.html
Author: buildbot
Date: Mon Jan 19 04:14:16 2015
New Revision: 936721
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:14:16 2015
@@ -1 +1 @@
-1652899
+1652900
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:14:16 2015
@@ -165,12 +165,10 @@ 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.
- - Verify that Maven has sufficient heap space to perform the build tasks. Some of them consume a surprising large amount of space.
+<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>
-<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>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><profile>
<id>signed_release</id>
<properties>