Author: joewitt
Date: Mon Jan 19 04:11:05 2015
New Revision: 1652898
URL: http://svn.apache.org/r1652898
Log:
review
Modified:
incubator/nifi/site/trunk/content/development/release-guide.md
Modified: incubator/nifi/site/trunk/content/development/release-guide.md
URL:
http://svn.apache.org/viewvc/incubator/nifi/site/trunk/content/development/release-guide.md?rev=1652898&r1=1652897&r2=1652898&view=diff
==============================================================================
--- incubator/nifi/site/trunk/content/development/release-guide.md (original)
+++ incubator/nifi/site/trunk/content/development/release-guide.md Mon Jan 19
04:11:05 2015
@@ -75,7 +75,30 @@ Follow the steps outlined in the [Quicks
At this point you're on the latest 'develop' branch and are able to build
the entire application
-Create a new branch based on a JIRA ticket for the release task
+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.
+
+Create the next version in JIRA if necessary so develop work can continue
towards that release.
+
+Create new branch off develop named after the JIRA ticket or just use the
develop branch itself
+
+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 `MAVEN_OPTS="-Xms1024m -Xmx3076m
-XX:MaxPermSize=256m"`
+
+ - Ensure your settings.xml has been updated as shown below. There are other
ways to ensure your key is available for signing as well
+
+```
+ <profile>
+ <id>signed_release</id>
+ <properties>
+ <mavenExecutorId>forked-path</mavenExecutorId>
+ <gpg.keyname>YOUR GPG KEY ID HERE</gpg.keyname>
+ <gpg.passphrase>YOUR GPG PASSPHRASE HERE</gpg.passphrase>
+ </properties>
+ </profile>
+```
+
+
[quickstart-guide]:
http://nifi.incubator.apache.org/development/quickstart.html
