You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@nifi.apache.org by al...@apache.org on 2018/07/11 00:34:43 UTC

nifi-site git commit: Updated release guide, people, and security pages with minor fixes.

Repository: nifi-site
Updated Branches:
  refs/heads/master 49738f144 -> 7bb9141ae


Updated release guide, people, and security pages with minor fixes.


Project: http://git-wip-us.apache.org/repos/asf/nifi-site/repo
Commit: http://git-wip-us.apache.org/repos/asf/nifi-site/commit/7bb9141a
Tree: http://git-wip-us.apache.org/repos/asf/nifi-site/tree/7bb9141a
Diff: http://git-wip-us.apache.org/repos/asf/nifi-site/diff/7bb9141a

Branch: refs/heads/master
Commit: 7bb9141aeeca63bac74eb78b75c681b6a136dfc8
Parents: 49738f1
Author: Andy LoPresto <al...@apache.org>
Authored: Tue Jul 10 17:04:21 2018 -0700
Committer: Andy LoPresto <al...@apache.org>
Committed: Tue Jul 10 17:04:21 2018 -0700

----------------------------------------------------------------------
 src/pages/html/people.hbs           |  2 +-
 src/pages/html/security.hbs         |  2 +-
 src/pages/markdown/release-guide.md | 13 ++++++-------
 3 files changed, 8 insertions(+), 9 deletions(-)
----------------------------------------------------------------------


http://git-wip-us.apache.org/repos/asf/nifi-site/blob/7bb9141a/src/pages/html/people.hbs
----------------------------------------------------------------------
diff --git a/src/pages/html/people.hbs b/src/pages/html/people.hbs
index e68c9c4..c014ab5 100644
--- a/src/pages/html/people.hbs
+++ b/src/pages/html/people.hbs
@@ -278,7 +278,7 @@ title: Apache NiFi Team
 <div class="row">
         <div class="large-12 columns">
             <p class="description">The team is comprised of Project Management Committee Members, Committers, and Contributors.
-	    <p class="description">Committers are the group of volunteers who are responsible for the technical aspects of the Apache NiFi Project. This group has write access to the appropriate source repositories and these volunteers may cast binding votes on any technical discussion.  Membership as a Committer is by invitation only and must be approved by <a href="https://www.apache.org/foundation/glossary.html#ConsensusApproval">consensus approval</a> of the active Apache NiFi PMC members on a vote open for at least 72 hours. A Committer is considered inactive by their own declaration or by not contributing in any form to the project for over six months. An inactive member can become active again by reversing whichever condition made them inactive ( i.e. , by reversing their earlier declaration or by once again contributing toward the project's work). Membership can be revoked by a unanimous vote of all the active PMC members (except the member in question if they are a PMC member).
+	    <p class="description">Committers are the group of volunteers who are responsible for the technical aspects of the Apache NiFi Project. This group has write access to the appropriate source repositories. All committer input is valued and when technical discussions occur, committer input is treated the same as PMC member input. Committers are encouraged to vote on releases and technical discussions, but only PMC members may cast "binding" votes (see <a href="https://www.apache.org/foundation/voting.html#binding-votes" target="_blank">Apache Voting Guide</a>). Membership as a Committer is by invitation only and must be approved by <a href="https://www.apache.org/foundation/glossary.html#ConsensusApproval">consensus approval</a> of the active Apache NiFi PMC members on a vote open for at least 72 hours. A Committer is considered inactive by their own declaration or by not contributing in any form to the project for over six months. An inactive member can become active again by rev
 ersing whichever condition made them inactive ( i.e., by reversing their earlier declaration or by once again contributing toward the project's work). Membership can be revoked by a unanimous vote of all the active PMC members (except the member in question if they are a PMC member).
 	   <p class="description">Contributors improve the project through submission of patches and suggestions. The number of Contributors to the project is unbounded. Get involved today. All contributions to the project are greatly appreciated.</p>
            <p class="description">Emeritus members are those that served as PMC members or committers and who have since moved into non-active status.  Their contributions and efforts are greatly appreciated in helping the community develop.</p>
         </div>

http://git-wip-us.apache.org/repos/asf/nifi-site/blob/7bb9141a/src/pages/html/security.hbs
----------------------------------------------------------------------
diff --git a/src/pages/html/security.hbs b/src/pages/html/security.hbs
index 6b52f13..455ee11 100644
--- a/src/pages/html/security.hbs
+++ b/src/pages/html/security.hbs
@@ -52,7 +52,7 @@ title: Apache NiFi Security Reports
 </div>
 <div class="row">
     <div class="large-12 columns">
-        <p><a id="CVE-2018-1309" href="#CVE-2018-1309"><strong>CVE-2018-1309</strong></a>: Apache NiFi External XML Entity issue in SplitXML processor</p>
+        <p><a id="CVE-2018-1309" href="#CVE-2018-1309"><strong>CVE-2018-1309</strong></a>: Apache NiFi XML External Entity issue in SplitXML processor</p>
         <p>Severity: <strong>Moderate</strong></p>
         <p>Versions Affected:</p>
         <ul>

http://git-wip-us.apache.org/repos/asf/nifi-site/blob/7bb9141a/src/pages/markdown/release-guide.md
----------------------------------------------------------------------
diff --git a/src/pages/markdown/release-guide.md b/src/pages/markdown/release-guide.md
index 1a2ce1c..3278141 100644
--- a/src/pages/markdown/release-guide.md
+++ b/src/pages/markdown/release-guide.md
@@ -243,7 +243,7 @@ click on that you can inspect the various staged artifacts.
     - 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 signature for the build and hashes. [Validating GPG signatures](https://nifi.apache.org/gpg.html).
     - Validate the LICENSE/NOTICE/Headers.  
     - Validate that the README is present and provides sufficient information to build and if necessary execute.
 
@@ -275,7 +275,7 @@ click on that you can inspect the various staged artifacts.
         $ shasum -a 256 nifi-${NIFI_VERSION}-source-release.zip | cut -d" " -f1 >  nifi-${NIFI_VERSION}-source-release.zip.sha256
         $ shasum -a 256 nifi-${NIFI_VERSION}-bin.tar.gz | cut -d" " -f1 >  nifi-${NIFI_VERSION}-bin.tar.gz.sha256
         $ shasum -a 256 nifi-${NIFI_VERSION}-bin.zip | cut -d" " -f1 >  nifi-${NIFI_VERSION}-bin.zip.sha256
-        $ shasum -a 256 nifi-toolkit-${NIFI_VERSION}-bin.zip | cut -d" " -f1 >  nifi--toolkit${NIFI_VERSION}-bin.zip.sha256
+        $ shasum -a 256 nifi-toolkit-${NIFI_VERSION}-bin.zip | cut -d" " -f1 >  nifi-toolkit-${NIFI_VERSION}-bin.zip.sha256
         $ shasum -a 256 nifi-toolkit-${NIFI_VERSION}-bin.tar.gz | cut -d" " -f1 >  nifi-toolkit-${NIFI_VERSION}-bin.tar.gz.sha256
         ```
     1. Generate SHA512 hash summaries.
@@ -283,7 +283,7 @@ click on that you can inspect the various staged artifacts.
         $ shasum -a 512 nifi-${NIFI_VERSION}-source-release.zip | cut -d" " -f1 >  nifi-${NIFI_VERSION}-source-release.zip.sha512
         $ shasum -a 512 nifi-${NIFI_VERSION}-bin.tar.gz | cut -d" " -f1 >  nifi-${NIFI_VERSION}-bin.tar.gz.sha512
         $ shasum -a 512 nifi-${NIFI_VERSION}-bin.zip | cut -d" " -f1 >  nifi-${NIFI_VERSION}-bin.zip.sha512
-        $ shasum -a 512 nifi-toolkit-${NIFI_VERSION}-bin.zip | cut -d" " -f1 >  nifi--toolkit${NIFI_VERSION}-bin.zip.sha512
+        $ shasum -a 512 nifi-toolkit-${NIFI_VERSION}-bin.zip | cut -d" " -f1 >  nifi-toolkit-${NIFI_VERSION}-bin.zip.sha512
         $ shasum -a 512 nifi-toolkit-${NIFI_VERSION}-bin.tar.gz | cut -d" " -f1 >  nifi-toolkit-${NIFI_VERSION}-bin.tar.gz.sha512
         ```
 
@@ -347,7 +347,7 @@ and more positive than negative binding votes._
 
     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:
+    from source, and test. Then please vote:
 
     [ ] +1 Release this package as nifi-${NIFI_VERSION}
     [ ] +0 no opinion
@@ -411,6 +411,7 @@ and more positive than negative binding votes._
     ```    
 
 1. Developers in the community review the release candidate and reply to the vote email with their vote.
+
 1. After 72 hours if
     - at least 3 binding (PMC members) cast +1 votes, and
     - the positive binding votes out number any negative binding votes
@@ -456,7 +457,7 @@ After the vote is complete and the release is approved, these steps complete the
     ```
 
 1. Update Docker version information to point to the next release.  For instance, if the next version applied by Maven is 1.3.0-SNAPSHOT, these values should be updated to 1.3.0. This currently consists of two files:
-  * [nifi-docker/dockerhub/Dockerfile, Line 24][dockerhub-version], and
+  * [nifi-docker/dockerhub/Dockerfile, Line 25][dockerhub-version], and
   * [nifi-docker/dockerhub/DockerImage.txt, Line 16][dockerimage-version].
 
 1. Update the NiFi website to point to the new download(s).  Remove older release artifacts from download page (leave
@@ -467,8 +468,6 @@ in the archive location so no need to do anything else.
 
 1. Update the [Migration Guide][nifi-migration-guide] on the Wiki.
 
-1. Update the NiFi Web Page to indicate NEWS of the release as appropriate
-
 1. If the release is on the latest development line, update the NiFi website documentation pages to match the release.
     1. Run the NiFi ${NIFI_VERSION}
     1. Pull down the documentation by running `wget -prk http://${host}:${port}/nifi-docs/documentation`