Author: buildbot
Date: Mon Jan 19 05:15:43 2015
New Revision: 936728
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 05:15:43 2015
@@ -1 +1 @@
-1652904
+1652906
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 05:15:43 2015
@@ -162,13 +162,15 @@ The following is a list of the sorts of
</pre></div>
-<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 a JIRA ticket for the release tasks and use that ticket number for
the commit messages. For example we'll consider NIFI-123 as our ticket. Also
+have in mind the release version you are planning for. For example we'll
consider '0.0.1-incubating'.</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>Change directory into that of the project you wish to release. For example
either <code>cd nifi</code> or <code>cd nar-maven-plugin</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>Ensure your settings.xml has been updated as shown below. There are other
ways to ensure your PGP key is available for signing as well</p>
<blockquote>
<div class="codehilite"><pre> ...
<span class="nt"><profile></span>
@@ -192,6 +194,29 @@ work <code>MAVEN_OPTS="-Xms1024m -Xmx307
</blockquote>
+<p>Ensure the the full application build and tests all work by executing
+<code>mvn -T 2.5C clean install</code> for a parallel build. Once that
completes you can
+startup and test the application by <code>cd assembly/target' then
run</code>bin/nifi.sh start<code>in the nifi build.
+The application should be up and running in a few seconds
at</code>http://localhost:8080/nifi`</p>
+<p>Evaluate and ensure the appropriate license headers are present on all
source files. Ensure LICENSE and NOTICE files are complete and accurate.<br />
+Developers should always be keeping these up to date as they go along adding
source and modifying dependencies to keep this burden manageable.<br />
+This command <code>mvn install -Pcheck-licenses</code> should be run as well
to help validate. If that doesn't complete cleanly it must be addressed.</p>
+<p>Now its time to have maven prepare the release so execute <code>mvn
release:prepare -Psigned_release -DscmCommentPrefix="NIFI-123 "
-Darguments="-DskipTests"</code>.
+Maven will ask:
+<code>What is the release version for "Apache NiFi NAR Plugin"?
(org.apache.nifi:nar-maven-plugin) 0.0.1-incubating: :</code>
+Just hit enter to accept the default.
+Maven will then ask:
+<code>What is SCM release tag or label for "Apache NiFi NAR Plugin"?
(org.apache.nifi:nar-maven-plugin) nar-maven-plugin-0.0.1-incubating: :</code>
+Enter <code>nar-maven-plugin-0.0.1-incubating-RC1</code> or whatever the
appropriate release candidate (RC) number is.
+Maven will then ask:
+<code>What is the new development version for "Apache NiFi NAR Plugin"?
(org.apache.nifi:nar-maven-plugin) 0.0.2-incubating-SNAPSHOT: :</code>
+Just hit enter to accept the default.</p>
+<p>Now that preparation went perfectly it is time to perform the release and
deploy artifacts to staging. To do that execute
+<code>mvn release:perform -Psigned_release -DscmCommentPrefix="NIFI-123 "
-Darguments="-DskipTests"</code></p>
+<p>That will complete successfully and this means the artifacts have been
released to the Apache Nexus staging repository. You will see something like
+<code>[INFO] * Closing staging repository with ID "orgapachenifi-1010".</code>
+So if you go in a browser to
<code>https://repository.apache.org/#stagingRepositories</code> you should see
<code>orgapachenifi-1010</code>. If you click on that you
+can inspect the various staged artifacts.</p>
</div>
</div>
<div id="footer">
