Author: buildbot
Date: Mon Mar 16 15:21:25 2015
New Revision: 943982
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 Mar 16 15:21:25 2015
@@ -1 +1 @@
-1667006
+1667037
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 Mar
16 15:21:25 2015
@@ -204,6 +204,7 @@ when evaluating a release for a vote.</p
</pre></div>
+<p>Validate that any new test resources added since the last release. This is
important because we have a broad exlusion for the RAT licensing/header checks
for test resources. The broad exclusion is validly because we have lots of
test resources which intentionally do not have apache license headers as we're
testing the objects as they would be in the wild. However, in every case we
can have the header we should have the header. So it is necessary to check and
ensure items aren't put in there which could cause problems for the source
release.</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-270 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>
