Author: buildbot
Date: Mon Jan 19 05:51:16 2015
New Revision: 936732
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:51:16 2015
@@ -1 +1 @@
-1652907
+1652911
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:51:16 2015
@@ -165,7 +165,8 @@ The following is a list of the sorts of
<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>Create new branch off develop named after the JIRA ticket or just use the
develop branch itself. Here we'll use a branch off of develop with
+<code>git checkout -b NIFI-123</code></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
@@ -215,8 +216,45 @@ Maven will then ask:</p>
<p><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</p>
<p><code>[INFO] * Closing staging repository with ID
"orgapachenifi-1010".</code></p>
-<p>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>
+<p>So if you browse to
<code>https://repository.apache.org/#stagingRepositories</code> login with your
Apache committer credentials and you should see
<code>orgapachenifi-1010</code>. If you click on that you can inspect the
various staged artifacts.</p>
+<p>Validate that all the various aspects of the staged artifacts appear correct
+ - Download the sources. Do they compile cleanly? If the result is a build
does it execute?
+ - Validate the hashes match.
+ - Validate that the sources contain no unexpected binaries.
+ - Validate the signature for the build and hashes.
+ - Validate the LICENSE/NOTICE/DISCLAIMER/Headers.<br />
+ - Validate that the README is present and provides sufficient information to
build and if necessary execute.</p>
+<p>If all looks good then push the branch to origin <code>git push origin
NIFI-123</code></p>
+<p>Now it's time to initiate a vote within the PPMC. The following template
can be used. Send the vote request to
<code>[email protected]</code>
+ with a subject of <code>[VOTE] Release Apache NiFi
nar-maven-plugin-0.0.2-incubating RC1</code></p>
+<blockquote>
+<p>Hello
+I am pleased to be calling this vote for the source release of Apache NiFi
+nar-maven-plugin-0.0.2-incubating.</p>
+<p>The source zip, including signatures, digests, etc can be found at:
+https://repository.apache.org/content/repositories/orgapachenifi-1010</p>
+<p>The Git tag is nar-maven-plugin-0.0.2-incubating-RC1
+The Git commit ID is 3e264c97449c921c7e0cbdec7eb94cb1d6868452
+https://git-wip-us.apache.org/repos/asf?p=incubator-nifi.git;a=commit;h=3e264c97449c921c7e0cbdec7eb94cb1d6868452</p>
+<p>Checksums of nar-maven-plugin-0.0.2-incubating-source-release.zip:
+MD5: 2728931f69fbb4503c689bd5b3f250b3
+SHA1: b32c55ad608d26987b49f6fd11fda1e1214c64fe</p>
+<p>Release artifacts are signed with the following key:
+https://people.apache.org/keys/committer/joewitt.asc</p>
+<p>KEYS file available here:
+https://dist.apache.org/repos/dist/release/incubator/nifi/KEYS</p>
+<p>Binaries have been published to Maven's staging repository, and
+are available here:</p>
+<p>https://repository.apache.org/content/repositories/orgapachenifi-1000</p>
+<p>8 issues were closed/resolved for this release:
+https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=12316020&version=12329307</p>
+<p>The vote will be open for 72 hours.
+Please download the release candidate and evaluate the necessary items
including checking hashes, signatures, build from source, and test. The please
vote:</p>
+<p>[ ] +1 Release this package as nar-maven-plugin-0.0.2-incubating
+[ ] +0 no opinion
+[ ] -1 Do not release this package because because...
+</p>
+</blockquote>
</div>
</div>
<div id="footer">
