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 2016/12/27 21:08:07 UTC
nifi-site git commit: NIFI-3258 Updating links to HTTPS
Repository: nifi-site
Updated Branches:
refs/heads/master 9fb9da1e4 -> eaca9b5ab
NIFI-3258 Updating links to HTTPS
This closes #9.
Signed-off-by: Aldrin Piri <al...@gmail.com>
Project: http://git-wip-us.apache.org/repos/asf/nifi-site/repo
Commit: http://git-wip-us.apache.org/repos/asf/nifi-site/commit/eaca9b5a
Tree: http://git-wip-us.apache.org/repos/asf/nifi-site/tree/eaca9b5a
Diff: http://git-wip-us.apache.org/repos/asf/nifi-site/diff/eaca9b5a
Branch: refs/heads/master
Commit: eaca9b5ab8692b77a6d7020243599f2922c356cf
Parents: 9fb9da1
Author: Joseph Percivall <JP...@apache.org>
Authored: Tue Dec 27 12:56:04 2016 -0500
Committer: Aldrin Piri <al...@gmail.com>
Committed: Tue Dec 27 16:07:52 2016 -0500
----------------------------------------------------------------------
src/includes/disclaimer.hbs | 4 +-
src/includes/minifi/minifi-topbar.hbs | 10 +-
src/includes/topbar.hbs | 10 +-
src/pages/html/download.hbs | 2 +-
src/pages/html/mailing_lists.hbs | 16 +-
src/pages/html/minifi/download.hbs | 2 +-
src/pages/html/people.hbs | 2 +-
src/pages/markdown/licensing-guide.md | 40 +--
src/pages/markdown/minifi/minifi-toolkit.md | 16 +-
src/pages/markdown/minifi/system-admin-guide.md | 2 +-
src/pages/markdown/quickstart.md | 14 +-
src/pages/markdown/release-guide.md | 242 +++++++++----------
12 files changed, 180 insertions(+), 180 deletions(-)
----------------------------------------------------------------------
http://git-wip-us.apache.org/repos/asf/nifi-site/blob/eaca9b5a/src/includes/disclaimer.hbs
----------------------------------------------------------------------
diff --git a/src/includes/disclaimer.hbs b/src/includes/disclaimer.hbs
index 0e64218..6aa0717 100644
--- a/src/includes/disclaimer.hbs
+++ b/src/includes/disclaimer.hbs
@@ -1,11 +1,11 @@
<div class="row">
<div class="large-12 columns footer">
- <a href="http://www.apache.org">
+ <a href="https://www.apache.org">
<img id="asf-logo" alt="Apache Software Foundation" src="{{assets}}/images/feather-small.gif">
</a>
<div id="copyright">
<p>Copyright © 2015 The Apache Software Foundation, Licensed under the <a
- href="http://www.apache.org/licenses/LICENSE-2.0">Apache License, Version 2.0</a>.<br/>Apache, the
+ href="https://www.apache.org/licenses/LICENSE-2.0">Apache License, Version 2.0</a>.<br/>Apache, the
Apache feather logo, NiFi, Apache NiFi and the project logo are trademarks of The Apache Software
Foundation.</p>
</div>
http://git-wip-us.apache.org/repos/asf/nifi-site/blob/eaca9b5a/src/includes/minifi/minifi-topbar.hbs
----------------------------------------------------------------------
diff --git a/src/includes/minifi/minifi-topbar.hbs b/src/includes/minifi/minifi-topbar.hbs
index 0eb9f44..6578dd9 100644
--- a/src/includes/minifi/minifi-topbar.hbs
+++ b/src/includes/minifi/minifi-topbar.hbs
@@ -20,7 +20,7 @@
<ul class="dropdown">
<li><a href="index.html">Home</a></li>
<li><a href="https://blogs.apache.org/nifi/"><i class="fa fa-external-link external-link"></i>Apache NiFi Blog</a></li>
- <li><a href="http://www.apache.org/licenses/LICENSE-2.0"><i class="fa fa-external-link external-link"></i>License</a></li>
+ <li><a href="https://www.apache.org/licenses/LICENSE-2.0"><i class="fa fa-external-link external-link"></i>License</a></li>
</ul>
</li>
<li class="has-dropdown">
@@ -62,10 +62,10 @@
<li class="has-dropdown">
<a href="#">ASF Links</a>
<ul class="dropdown">
- <li><a href="http://www.apache.org"><i class="fa fa-external-link external-link"></i>Apache Software Foundation</a></li>
- <li><a href="http://www.apache.org/foundation/sponsorship.html"><i class="fa fa-external-link external-link"></i>Sponsorship</a></li>
- <li><a href="http://www.apache.org/security/"><i class="fa fa-external-link external-link"></i>Security</a></li>
- <li><a href="http://www.apache.org/foundation/thanks.html"><i class="fa fa-external-link external-link"></i>Thanks</a></li>
+ <li><a href="https://www.apache.org"><i class="fa fa-external-link external-link"></i>Apache Software Foundation</a></li>
+ <li><a href="https://www.apache.org/foundation/sponsorship.html"><i class="fa fa-external-link external-link"></i>Sponsorship</a></li>
+ <li><a href="https://www.apache.org/security/"><i class="fa fa-external-link external-link"></i>Security</a></li>
+ <li><a href="https://www.apache.org/foundation/thanks.html"><i class="fa fa-external-link external-link"></i>Thanks</a></li>
</ul>
</li>
<li>
http://git-wip-us.apache.org/repos/asf/nifi-site/blob/eaca9b5a/src/includes/topbar.hbs
----------------------------------------------------------------------
diff --git a/src/includes/topbar.hbs b/src/includes/topbar.hbs
index 49aab04..8af05fd 100644
--- a/src/includes/topbar.hbs
+++ b/src/includes/topbar.hbs
@@ -20,7 +20,7 @@
<ul class="dropdown">
<li><a href="index.html">Home</a></li>
<li><a href="https://blogs.apache.org/nifi/"><i class="fa fa-external-link external-link"></i>Apache NiFi Blog</a></li>
- <li><a href="http://www.apache.org/licenses/LICENSE-2.0"><i class="fa fa-external-link external-link"></i>License</a></li>
+ <li><a href="https://www.apache.org/licenses/LICENSE-2.0"><i class="fa fa-external-link external-link"></i>License</a></li>
</ul>
</li>
<li class="has-dropdown">
@@ -62,10 +62,10 @@
<li class="has-dropdown">
<a href="#">ASF Links</a>
<ul class="dropdown">
- <li><a href="http://www.apache.org"><i class="fa fa-external-link external-link"></i>Apache Software Foundation</a></li>
- <li><a href="http://www.apache.org/foundation/sponsorship.html"><i class="fa fa-external-link external-link"></i>Sponsorship</a></li>
- <li><a href="http://www.apache.org/security/"><i class="fa fa-external-link external-link"></i>Security</a></li>
- <li><a href="http://www.apache.org/foundation/thanks.html"><i class="fa fa-external-link external-link"></i>Thanks</a></li>
+ <li><a href="https://www.apache.org"><i class="fa fa-external-link external-link"></i>Apache Software Foundation</a></li>
+ <li><a href="https://www.apache.org/foundation/sponsorship.html"><i class="fa fa-external-link external-link"></i>Sponsorship</a></li>
+ <li><a href="https://www.apache.org/security/"><i class="fa fa-external-link external-link"></i>Security</a></li>
+ <li><a href="https://www.apache.org/foundation/thanks.html"><i class="fa fa-external-link external-link"></i>Thanks</a></li>
</ul>
</li>
<li>
http://git-wip-us.apache.org/repos/asf/nifi-site/blob/eaca9b5a/src/pages/html/download.hbs
----------------------------------------------------------------------
diff --git a/src/pages/html/download.hbs b/src/pages/html/download.hbs
index caad665..389b53d 100644
--- a/src/pages/html/download.hbs
+++ b/src/pages/html/download.hbs
@@ -14,7 +14,7 @@ title: Apache NiFi Downloads
</div>
<div class="row">
<div class="large-12 columns">
- <p>To verify the downloads please follow these <a href="http://www.apache.org/info/verification.html">procedures</a>
+ <p>To verify the downloads please follow these <a href="https://www.apache.org/info/verification.html">procedures</a>
using these <a href="https://dist.apache.org/repos/dist/release/nifi/KEYS">KEYS</a></p>
<p>If a download is not found please allow up to 24 hours for the mirrors to sync.</p>
</div>
http://git-wip-us.apache.org/repos/asf/nifi-site/blob/eaca9b5a/src/pages/html/mailing_lists.hbs
----------------------------------------------------------------------
diff --git a/src/pages/html/mailing_lists.hbs b/src/pages/html/mailing_lists.hbs
index a964fce..c0959f3 100644
--- a/src/pages/html/mailing_lists.hbs
+++ b/src/pages/html/mailing_lists.hbs
@@ -36,8 +36,8 @@ title: Apache NiFi Mailing Lists
<td><a class="externalLink" href="mailto:users-subscribe@nifi.apache.org">Subscribe</a></td>
<td><a class="externalLink" href="mailto:users-unsubscribe@nifi.apache.org">Unsubscribe</a></td>
<td><a class="externalLink" href="mailto:users@nifi.apache.org">Post</a></td>
- <td><a class="externalLink" href="http://lists.apache.org/list.html?users@nifi.apache.org">users@nifi.apache.org</a></td>
- <td><a class="externalLink" href="http://mail-archives.apache.org/mod_mbox/nifi-users/">mail-archives.apache.org</a></td>
+ <td><a class="externalLink" href="https://lists.apache.org/list.html?users@nifi.apache.org">users@nifi.apache.org</a></td>
+ <td><a class="externalLink" href="https://mail-archives.apache.org/mod_mbox/nifi-users/">mail-archives.apache.org</a></td>
<td>For nifi users to get help, ask questions, report bugs</td>
</tr>
<tr>
@@ -45,8 +45,8 @@ title: Apache NiFi Mailing Lists
<td><a class="externalLink" href="mailto:dev-subscribe@nifi.apache.org">Subscribe</a></td>
<td><a class="externalLink" href="mailto:dev-unsubscribe@nifi.apache.org">Unsubscribe</a></td>
<td><a class="externalLink" href="mailto:dev@nifi.apache.org">Post</a></td>
- <td><a class="externalLink" href="http://lists.apache.org/list.html?dev@nifi.apache.org">dev@nifi.apache.org</a></td>
- <td><a class="externalLink" href="http://mail-archives.apache.org/mod_mbox/nifi-dev/">mail-archives.apache.org</a></td>
+ <td><a class="externalLink" href="https://lists.apache.org/list.html?dev@nifi.apache.org">dev@nifi.apache.org</a></td>
+ <td><a class="externalLink" href="https://mail-archives.apache.org/mod_mbox/nifi-dev/">mail-archives.apache.org</a></td>
<td>For developers to discuss features, bugs, share ideas</td>
</tr>
<tr>
@@ -54,8 +54,8 @@ title: Apache NiFi Mailing Lists
<td><a class="externalLink" href="mailto:commits-subscribe@nifi.apache.org">Subscribe</a></td>
<td><a class="externalLink" href="mailto:commits-unsubscribe@nifi.apache.org">Unsubscribe</a></td>
<td><a class="externalLink" href="mailto:commits@nifi.apache.org">Post</a></td>
- <td><a class="externalLink" href="http://lists.apache.org/list.html?commits@nifi.apache.org">commits@nifi.apache.org</a></td>
- <td><a class="externalLink" href="http://mail-archives.apache.org/mod_mbox/nifi-commits/">mail-archives.apache.org</a></td>
+ <td><a class="externalLink" href="https://lists.apache.org/list.html?commits@nifi.apache.org">commits@nifi.apache.org</a></td>
+ <td><a class="externalLink" href="https://mail-archives.apache.org/mod_mbox/nifi-commits/">mail-archives.apache.org</a></td>
<td>Automated e-mails each time code commits occur</td>
</tr>
<tr>
@@ -63,8 +63,8 @@ title: Apache NiFi Mailing Lists
<td><a class="externalLink" href="mailto:issues-subscribe@nifi.apache.org">Subscribe</a></td>
<td><a class="externalLink" href="mailto:issues-unsubscribe@nifi.apache.org">Unsubscribe</a></td>
<td><a class="externalLink" href="mailto:issues@nifi.apache.org">Post</a></td>
- <td><a class="externalLink" href="http://lists.apache.org/list.html?issues@nifi.apache.org">issues@nifi.apache.org</a></td>
- <td><a class="externalLink" href="http://mail-archives.apache.org/mod_mbox/nifi-issues/">mail-archives.apache.org</a></td>
+ <td><a class="externalLink" href="https://lists.apache.org/list.html?issues@nifi.apache.org">issues@nifi.apache.org</a></td>
+ <td><a class="externalLink" href="https://mail-archives.apache.org/mod_mbox/nifi-issues/">mail-archives.apache.org</a></td>
<td>Automated e-mails each time comments are made in JIRA or Github</td>
</tr>
</table>
http://git-wip-us.apache.org/repos/asf/nifi-site/blob/eaca9b5a/src/pages/html/minifi/download.hbs
----------------------------------------------------------------------
diff --git a/src/pages/html/minifi/download.hbs b/src/pages/html/minifi/download.hbs
index c0df04f..0c818d1 100644
--- a/src/pages/html/minifi/download.hbs
+++ b/src/pages/html/minifi/download.hbs
@@ -14,7 +14,7 @@ title: Apache NiFi - MiNiFi Downloads
</div>
<div class="row">
<div class="large-12 columns">
- <p>To verify the downloads please follow these <a href="http://www.apache.org/info/verification.html">procedures</a>
+ <p>To verify the downloads please follow these <a href="https://www.apache.org/info/verification.html">procedures</a>
using these <a href="https://dist.apache.org/repos/dist/release/nifi/KEYS">KEYS</a></p>
<p>If a download is not found please allow up to 24 hours for the mirrors to sync.</p>
</div>
http://git-wip-us.apache.org/repos/asf/nifi-site/blob/eaca9b5a/src/pages/html/people.hbs
----------------------------------------------------------------------
diff --git a/src/pages/html/people.hbs b/src/pages/html/people.hbs
index 1aa8ccd..c8e940c 100644
--- a/src/pages/html/people.hbs
+++ b/src/pages/html/people.hbs
@@ -212,7 +212,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="http://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 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">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/eaca9b5a/src/pages/markdown/licensing-guide.md
----------------------------------------------------------------------
diff --git a/src/pages/markdown/licensing-guide.md b/src/pages/markdown/licensing-guide.md
index 9c928b1..8da9d33 100644
--- a/src/pages/markdown/licensing-guide.md
+++ b/src/pages/markdown/licensing-guide.md
@@ -12,24 +12,24 @@ This document is not written by lawyers. The guidance in this document is meant
## Background Material
-- [ASLv2](http://apache.org/licenses/LICENSE-2.0)
-- [ASF License Apply](http://www.apache.org/dev/apply-license.html)
-- [ASF Licensing How-To](http://www.apache.org/dev/licensing-howto.html)
-- [ASF Legal Resolved](http://www.apache.org/legal/resolved.html)
-- [ASF Release Policy](http://www.apache.org/dev/release.html)
+- [ASLv2](https://www.apache.org/licenses/LICENSE-2.0)
+- [ASF License Apply](https://www.apache.org/dev/apply-license.html)
+- [ASF Licensing How-To](https://www.apache.org/dev/licensing-howto.html)
+- [ASF Legal Resolved](https://www.apache.org/legal/resolved.html)
+- [ASF Release Policy](https://www.apache.org/dev/release.html)
## How to consistently apply licensing/legal notice information for Apache NiFi
### Apply the source header to each source file
-Every source file for works submitted directly to the ASF must follow: http://apache.org/legal/src-headers.html#headers
+Every source file for works submitted directly to the ASF must follow: https://www.apache.org/legal/src-headers.html#headers
Question: Every source file? What about test files and so on?
Answer: There are a few exceptions. Test files can be argued to have no degree of creativity. We also need our test materials at times to be exactly as they will be found in the wild. We should ensure test files have the license when possible but not to the point that it requires altering the test itself.
- http://apache.org/legal/src-headers.html#faq-exceptions
+ https://www.apache.org/legal/src-headers.html#faq-exceptions
Question: Do items which are generated from source during the build process require the header?
-Answer: Taken directly from http://incubator.apache.org/guides/releasemanagement.html#notes-license-headers it reads:
+Answer: Taken directly from https://incubator.apache.org/guides/releasemanagement.html#notes-license-headers it reads:
"Copyright may not subsist in a document which is generated by an transformation from an original. In which case, the license header may be unnecessary. License headers should always be present in the original. Where it is reasonable to do so, the templates should also add the license header to the generated documents."
### Apply the proper NOTICE / LICENSE Information
@@ -77,43 +77,43 @@ local and accurate LICENSE/NOTICE for that artifact.
### How to go about working with the LICENSE/NOTICE modifications
If the dependency is a source dependency (ie you copied in javascript, css, java source files from a website) then you
- must ensure it is from [Category-A](http://www.apache.org/legal/resolved.html#category-a) licenses.
+ must ensure it is from [Category-A](https://www.apache.org/legal/resolved.html#category-a) licenses.
If the dependency is a binary dependency (ie maven pulled in a jar file) then you must ensure it is either from
-[Category-A](http://www.apache.org/legal/resolved.html#category-a) or
-[Category-B](http://www.apache.org/legal/resolved.html#category-b).
+[Category-A](https://www.apache.org/legal/resolved.html#category-a) or
+[Category-B](https://www.apache.org/legal/resolved.html#category-b).
The key guides for how to apply the LICENSE/NOTICE is found in the following:
- - [Source Headers](http://apache.org/legal/src-headers.html#3party)
- - [Third Party Notices](http://apache.org/legal/resolved.html#required-third-party-notices.)
- - [How to modify the NOTICE](http://www.apache.org/dev/licensing-howto.html#mod-notice)
+ - [Source Headers](https://www.apache.org/legal/src-headers.html#3party)
+ - [Third Party Notices](https://www.apache.org/legal/resolved.html#required-third-party-notices.)
+ - [How to modify the NOTICE](https://www.apache.org/dev/licensing-howto.html#mod-notice)
Specific guidance for handling LICENSE/NOTICE application for typical MIT/BSD licenses is
-described [here](http://www.apache.org/dev/licensing-howto.html#permissive-deps). For understanding what to put in the
+described [here](https://www.apache.org/dev/licensing-howto.html#permissive-deps). For understanding what to put in the
LICENSE file look at the license of the 3rd party work. BSD licenses for instance have this statement "Redistributions
in binary form must reproduce the above copyright notice, this list of conditions and the following disclaimer in the
documentation and/or other materials provided with the distribution." In the event you cannot find the actual
Copyright statement for a dependency then place a link to the license text they claim and indicate no copyright marks
found and provide a link to the project website.
-Specific guidance for handling Apache Licensed dependencies is describe [here](http://www.apache.org/dev/licensing-howto.html#alv2-dep).
+Specific guidance for handling Apache Licensed dependencies is describe [here](https://www.apache.org/dev/licensing-howto.html#alv2-dep).
"If the dependency supplies a NOTICE file, its contents must be analyzed and the relevant portions bubbled up into the top-level NOTICE file."
-Specific guidance for handling other ASF projects is found [here](http://www.apache.org/dev/licensing-howto.html#bundle-asf-product).
+Specific guidance for handling other ASF projects is found [here](https://www.apache.org/dev/licensing-howto.html#bundle-asf-product).
"It is not necessary to duplicate the line "This product includes software developed at the Apache Software
Foundation...", though the ASF copyright line and any other portions of NOTICE must be considered for propagation."
-Specific guidance for handling LICENSE/NOTICE information for category-B licensed works is [here](http://apache.org/legal/resolved.html#category-b).
+Specific guidance for handling LICENSE/NOTICE information for category-B licensed works is [here](https://www.apache.org/legal/resolved.html#category-b).
Place an entry in the notice indicating the work is included in binary distribution. Provide a link to the
homepage of the work. Indicate it's license. Group like licensed items together. "By attaching a prominent label to
the distribution and requiring an explicit action by the user to get the reciprocally-licensed source, users are less
likely to be unaware of restrictions significantly different from those of the Apache License. Please include the URL
to the product's homepage in the prominent label." You should not modify the LICENSE file to include the LICENSE
-information of the 3rd party work in this case. That is explained nicely in http://opensource.org/faq#copyleft as
+information of the 3rd party work in this case. That is explained nicely in https://opensource.org/faq#copyleft as
stated "Copyleft provisions apply only to actual derivatives, that is, cases where an existing copylefted work was
modified. Merely distributing a copyleft work alongside a non-copyleft work does not cause the latter to fall under
the copyleft terms."
-Specific guidance for handling works in the public domain is [here](http://apache.org/legal/resolved.html#can-works-placed-in-the-public-domain-be-included-in-apache-products)
+Specific guidance for handling works in the public domain is [here](https://www.apache.org/legal/resolved.html#can-works-placed-in-the-public-domain-be-included-in-apache-products)
http://git-wip-us.apache.org/repos/asf/nifi-site/blob/eaca9b5a/src/pages/markdown/minifi/minifi-toolkit.md
----------------------------------------------------------------------
diff --git a/src/pages/markdown/minifi/minifi-toolkit.md b/src/pages/markdown/minifi/minifi-toolkit.md
index 89af2f6..94d4881 100644
--- a/src/pages/markdown/minifi/minifi-toolkit.md
+++ b/src/pages/markdown/minifi/minifi-toolkit.md
@@ -34,7 +34,7 @@ MiNiFi is a child project effort of Apache NiFi. The MiNiFi toolkit aids in cre
## Getting Started
-The latest version of the MiNiFi Toolkit Converter can be found at http://nifi.apache.org/minifi/download.html under the `MiNiFi Toolkit Binaries` section.
+The latest version of the MiNiFi Toolkit Converter can be found at https://nifi.apache.org/minifi/download.html under the `MiNiFi Toolkit Binaries` section.
After downloading the binary and extracting it, to run the MiNiFi Toolkit Converter:
- Change directory to the location where you installed MiNiFi Toolkit and run it and view usage information
@@ -56,24 +56,24 @@ After downloading the binary and extracting it, to run the MiNiFi Toolkit Conver
## Getting Help
If you have questions, you can reach out to our mailing list: dev@nifi.apache.org
-([archive](http://mail-archives.apache.org/mod_mbox/nifi-dev)).
+([archive](https://mail-archives.apache.org/mod_mbox/nifi-dev)).
We're also often available in IRC: #nifi on
-[irc.freenode.net](http://webchat.freenode.net/?channels=#nifi).
+[irc.freenode.net](https://webchat.freenode.net/?channels=#nifi).
## Documentation
-See http://nifi.apache.org/minifi and https://cwiki.apache.org/confluence/display/NIFI/MiNiFi for the latest documentation.
+See https://nifi.apache.org/minifi and https://cwiki.apache.org/confluence/display/NIFI/MiNiFi for the latest documentation.
## License
Except as otherwise noted this software is licensed under the
-[Apache License, Version 2.0](http://www.apache.org/licenses/LICENSE-2.0.html)
+[Apache License, Version 2.0](https://www.apache.org/licenses/LICENSE-2.0.html)
Licensed under the Apache License, Version 2.0 (the "License");
you may not use this file except in compliance with the License.
You may obtain a copy of the License at
- http://www.apache.org/licenses/LICENSE-2.0
+ https://www.apache.org/licenses/LICENSE-2.0
Unless required by applicable law or agreed to in writing, software
distributed under the License is distributed on an "AS IS" BASIS,
@@ -105,8 +105,8 @@ The following provides more details on the included cryptographic software:
Apache NiFi - MiNiFi uses BouncyCastle, Jasypt, JCraft Inc., and the built-in
java cryptography libraries for SSL, SSH, and the protection
of sensitive configuration parameters. See
-http://bouncycastle.org/about.html
+https://bouncycastle.org/about.html
http://www.jasypt.org/faq.html
http://jcraft.com/c-info.html
-http://www.oracle.com/us/products/export/export-regulations-345813.html
+https://www.oracle.com/us/products/export/export-regulations-345813.html
for more details on each of these libraries cryptography features.
http://git-wip-us.apache.org/repos/asf/nifi-site/blob/eaca9b5a/src/pages/markdown/minifi/system-admin-guide.md
----------------------------------------------------------------------
diff --git a/src/pages/markdown/minifi/system-admin-guide.md b/src/pages/markdown/minifi/system-admin-guide.md
index e408770..907d09b 100644
--- a/src/pages/markdown/minifi/system-admin-guide.md
+++ b/src/pages/markdown/minifi/system-admin-guide.md
@@ -6,7 +6,7 @@ title: Apache NiFi MiNiFi System Administrator's Guide
[Apache NiFi Team](dev@nifi.apache.org>)
-[NiFi Homepage](http://nifi.apache.org)
+[NiFi Homepage](https://nifi.apache.org)
# FlowStatus Query Options
http://git-wip-us.apache.org/repos/asf/nifi-site/blob/eaca9b5a/src/pages/markdown/quickstart.md
----------------------------------------------------------------------
diff --git a/src/pages/markdown/quickstart.md b/src/pages/markdown/quickstart.md
index e11f4ef..12cfd52 100644
--- a/src/pages/markdown/quickstart.md
+++ b/src/pages/markdown/quickstart.md
@@ -36,7 +36,7 @@ git config --global core.autocrlf false
To check out the code:
```
-git clone http://git-wip-us.apache.org/repos/asf/nifi.git
+git clone https://git-wip-us.apache.org/repos/asf/nifi.git
```
<br/>
Then checkout the 'master' branch (which should be the default)
@@ -164,13 +164,13 @@ is ready for use:
2014-12-09 00:42:03,540 INFO [main] org.apache.nifi.web.server.JettyServer NiFi has started. The UI is available at the following URLs:
[adminguide]: https://nifi.apache.org/docs/nifi-docs/html/administration-guide.html
-[maven]: http://maven.apache.org/
+[maven]: https://maven.apache.org/
[jira]: https://issues.apache.org/jira/browse/NIFI
-[git]: http://git-scm.com/
+[git]: https://git-scm.com/
[gitbrowse]: https://git-wip-us.apache.org/repos/asf?p=nifi.git;a=summary
[gitbrowsenifisite]: https://git-wip-us.apache.org/repos/asf?p=nifi-site.git;a=summary
[gitbrowsenifimaven]: https://git-wip-us.apache.org/repos/asf?p=nifi-maven.git;a=summary
-[gitrepo]: http://git-wip-us.apache.org/repos/asf/nifi.git
-[gitreponifisite]: http://git-wip-us.apache.org/repos/asf/nifi-site.git
-[gitreponifimaven]: http://git-wip-us.apache.org/repos/asf/nifi-maven.git
-[githubrepo]: https://github.com/apache/nifi
+[gitrepo]: https://git-wip-us.apache.org/repos/asf/nifi.git
+[gitreponifisite]: https://git-wip-us.apache.org/repos/asf/nifi-site.git
+[gitreponifimaven]: https://git-wip-us.apache.org/repos/asf/nifi-maven.git
+[githubrepo]: https://github.com/apache/nifihttps://git-wip-us.apache.org/repos/asf/nifi-maven.git
http://git-wip-us.apache.org/repos/asf/nifi-site/blob/eaca9b5a/src/pages/markdown/release-guide.md
----------------------------------------------------------------------
diff --git a/src/pages/markdown/release-guide.md b/src/pages/markdown/release-guide.md
index bac1928..1cb033b 100644
--- a/src/pages/markdown/release-guide.md
+++ b/src/pages/markdown/release-guide.md
@@ -4,7 +4,7 @@ title: Apache NiFi Release Guidelines
# Apache NiFi Release Guidelines
-The purpose of this document is to capture and describe the steps involved in producing
+The purpose of this document is to capture and describe the steps involved in producing
an official release of Apache NiFi. It is written specifically to someone acting in the
capacity of a [Release Manager][apache-release-manager] (RM).
@@ -31,35 +31,35 @@ Our aim is to produce an official Apache release from an existing release branch
## Terms
- * **Release Manager** (RM) - the Apache NiFi PMC Member or Committer acting as [Release Manager][apache-release-manager]
+ * **Release Manager** (RM) - the Apache NiFi PMC Member or Committer acting as [Release Manager][apache-release-manager]
for a particular release of Apache NiFi.
* **Release Candidate** (RC) - an iteration of the release process that is proposed for a vote by the Apache NiFi
Community.
* **Community** - the [community][apache-glossary-community] of people with an interest
in the improvement and advancement of Apache NiFi, including end-users, developers, evangelists, and advisers.
* **PMC** - within the Apache NiFi community, members of the [PMC][apache-glossary-pmc] oversee the ongoing project.
- * **Committer** - with the Apache NiFi community, [committers][apache-glossary-committer]
+ * **Committer** - with the Apache NiFi community, [committers][apache-glossary-committer]
have gain the privilege to commit changes to the Apache NiFi codebase.
-
+
## High level flow of a release
- The Apache NiFi community is constantly contributing to JIRA tickets assigned to the next release.
- At some point the number of tickets open/remaining for the next release begins to approach zero.
- A member of the community suggests a release and initiates a discussion.
- - Someone volunteers to perform the Release Manager (RM) role for the release. (This can be a committer but Apache
+ - Someone volunteers to perform the Release Manager (RM) role for the release. (This can be a committer but Apache
guides indicate a preference for a PMC member.)
- - The RM validate the proposed release and stages the source code, Maven artifacts, and distributable files for a
+ - The RM validate the proposed release and stages the source code, Maven artifacts, and distributable files for a
Release Candidate (RC).
- The RM initiates a vote on the RC by the NiFi community.
- If the NiFi community rejects the RC, the issues noted are resolved and another RC is generated.
- If the NiFi community accepts the RC, the staged source code, artifacts, and distribution files are moved to the
appropriately locations for public release.
-
+
## Variable reference substitutions
-Throughout this guide, references must be made to names and values that will vary from release to release. For clarity
-those variable values have been written like Bash variable references. When a term like
-"```/tmp/src/nifi-${NIFI_VERSION}```" is seen in an instruction or email template it should be replaced with
+Throughout this guide, references must be made to names and values that will vary from release to release. For clarity
+those variable values have been written like Bash variable references. When a term like
+"```/tmp/src/nifi-${NIFI_VERSION}```" is seen in an instruction or email template it should be replaced with
"```/tmp/src/nifi-0.7.0```" when working the release of "Apache NiFi 0.7.0".
* Subtitutions used in tasks and email templates
@@ -75,10 +75,10 @@ those variable values have been written like Bash variable references. When a t
${STAGING_REPO_ID} orgapachenifi-1088 the temporate repository ID where staged artifacts have been placed.
${RM_USERID} johndoe the Apache account ID of Release Manager.
${RELEASE_TAG} rel/nifi-0.7.0 the Git repository tag for the source code as released.
- ${VOTE_THREAD_URL} <a href="https://lists.apache.org/thread.html/8b111ce611238af8b71b95039c299ae0a1ec063ea77f83aa34e6a2bd@%3Cdev.nifi.apache.org%3E">0.7.0 vote thread</a> the URL for the Apache Pony Mail archive of the release vote thread.
+ ${VOTE_THREAD_URL} [0.7.0 vote thread][070-rc2-vote] the URL for the Apache Pony Mail archive of the release vote thread.
</pre>
-
- _To be practical but avoid confusion with future release details, these example values reflect the previous release
+
+ _To be practical but avoid confusion with future release details, these example values reflect the previous release
NiFi 0.7.0 RC2 release details._
## What to validate and how to validate a release
@@ -87,7 +87,7 @@ The following is a list of the sorts of things that will be validated and are th
when evaluating a release for a vote.
- Are the LICENSE and NOTICE files present in the source root and complete?
- - Specifically look in the ```nifi-${NIFI_VERSION}-sources-release.zip``` artifact and ensure these files are
+ - Specifically look in the ```nifi-${NIFI_VERSION}-sources-release.zip``` artifact and ensure these files are
present at the root of the archive.
- Evaluate the sources and dependencies.
- Does the overall LICENSE and NOTICE appear correct?
@@ -109,57 +109,57 @@ when evaluating a release for a vote.
- The only thing we'd expect would be potentially test resources files.
- Does the app (if appropriate) execute and function as expected?
-This list is reflected in the Release Vote and Release Helper Guide emails that are sent once the release has been
+This list is reflected in the Release Vote and Release Helper Guide emails that are sent once the release has been
staged in the Git and Nexus repositories.
-## The Release Process
+## The Release Process
-The release process includes steps to be performed by the Release Manager as well as the
-Apache NiFi developer community.
+The release process includes steps to be performed by the Release Manager as well as the
+Apache NiFi developer community.
### Step 1. Configure the build environment (RM and community)
-
+
1. Follow the steps outlined in the [Quickstart Guide][nifi-quickstart-guide] to prepare the development system.
-1. Confirm that the local Git workspace is configured with an origin remote pointing to the RM's personal fork of the
+1. Confirm that the local Git workspace is configured with an origin remote pointing to the RM's personal fork of the
NiFi source and an "ASF" remote pointing to the Apache Git Repository for NiFi.
```
$ git remote -v
- asf http://git-wip-us.apache.org/repos/asf/nifi.git (fetch)
- asf http://git-wip-us.apache.org/repos/asf/nifi.git (push)
+ asf https://git-wip-us.apache.org/repos/asf/nifi.git (fetch)
+ asf https://git-wip-us.apache.org/repos/asf/nifi.git (push)
origin https://github.com/${RM_USERID}/nifi.git (fetch)
origin https://github.com/${RM_USERID}/nifi.git (push)
```
- Additional remotes will not cause a problem if these two are correct. Other configurations are perfectly
- acceptable but the appropriate adjustments to the steps in this guide must be made by the release manager.
+ Additional remotes will not cause a problem if these two are correct. Other configurations are perfectly
+ acceptable but the appropriate adjustments to the steps in this guide must be made by the release manager.
1. Confirm that source code can be checked out for the branch being released.
```
git checkout ${BRANCH}
```
1. Confirm that the entire application builds correctly in the build environment.
-
+
### Step 2. Prepare and stage the release (RM)
1. Create a JIRA ticket for the release tasks for version ${NIFI_VERSION}.
___The resulting JIRA ticket number is referred to as__ ${JIRA\_TICKET} __in this guide.___
1. Create the next version in JIRA, if it doesn't already exist, so work can continue towards that release.
-1. Create meaningful release notes for this version if not already created. [Enter them here][nifi-release-notes] on
-the NiFi wiki.
+1. Create meaningful release notes for this version if not already created. [Enter them here][nifi-release-notes] on
+the NiFi wiki.
1. Create a new branch off 'master' named after the JIRA ticket.
```bash
$ git checkout -b NIFI-${JIRA_TICKET}-RC${RC} ${BRANCH}
```
-1. Verify that Maven has sufficient heap space to perform the build tasks. Some plugins and parts of the build
+1. 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 for Java 8 for NiFi version 1.x and later.
```bash
$ export MAVEN_OPTS="-Xms1024m -Xmx3076m"
```
- - And these work for Java 7 for NiFi version 0.x.
+ - And these work for Java 7 for NiFi version 0.x.
```
$ export MAVEN_OPTS="-Xms1024m -Xmx3076m -XX:MaxPermSize=256m"
```
-1. Ensure your settings.xml has been updated to include a `signed_release` profile and a `<server>` entry for
-"repository.apache.org" as shown below. [Steps to configure and encrypt Maven passwords][sonatype-maven-password].
+1. Ensure your settings.xml has been updated to include a `signed_release` profile and a `<server>` entry for
+"repository.apache.org" as shown below. [Steps to configure and encrypt Maven passwords][sonatype-maven-password].
There are other ways to ensure your PGP key is available for signing as well.
```XML
<profile>
@@ -183,21 +183,21 @@ There are other ways to ensure your PGP key is available for signing as well.
```
$ mvn -T 2.5C clean install
```
-1. Startup and test the application with from the root source folder. After a few seconds, NiFi should be up and
+1. Startup and test the application with from the root source folder. After a few seconds, NiFi should be up and
running at [http://localhost:8080/nifi](http://localhost:8080/nifi).
```
$ cd nifi-assembly/target/nifi-${NIFI_VERSION}-bin/nifi-${NIFI_VERSION}
$ bin/nifi.sh start
```
1. Evaluate and ensure the appropriate license headers are present on all source files.
-1. Ensure LICENSE and NOTICE files are complete and accurate. (Developers should always be keeping these up to date as
+1. Ensure LICENSE and NOTICE files are complete and accurate. (Developers should always be keeping these up to date as
they go along adding source and modifying dependencies to keep this burden manageable.)
-1. Build the project with the `contrib-check` profile enabled to validate contribution expectations and find any
+1. Build the project with the `contrib-check` profile enabled to validate contribution expectations and find any
problems that must be addressed before proceeding.
```
$ mvn install -Pcontrib-check
```
-
+
### Step 3. Perform the release (RM)
1. Now its time to have maven prepare the release with this command.
@@ -210,12 +210,12 @@ problems that must be addressed before proceeding.
-DdevelopmentVersion="${NEXT_VERSION}" \
-Darguments="-DskipTests"
```
-1. Review the release preparation results. If problems are found `$ mvn release:rollback` will reset the changes, or
+1. Review the release preparation results. If problems are found `$ mvn release:rollback` will reset the changes, or
it may be necessary to run `$ mvn release:clean` to get the project to a state where it can be rebuilt.
1. If the preparation without problems, it is time to perform the release and deploy artifacts to staging.
```
- $ mvn release:perform
+ $ mvn release:perform
-Psigned_release \
-DscmCommentPrefix="${JIRA_TICKET}-RC${RC}"
-Darguments="-DskipTests"
@@ -229,7 +229,7 @@ it may be necessary to run `$ mvn release:clean` to get the project to a state w
___This staging repository ID is referred to by ${STAGING_REPO_ID} in this release guide.___
1. Browse to the Apache [Staging Repository][apache-staging-repositories] and
-login with your Apache committer credentials and you should see the newly created staging repository listed. If you
+login with your Apache committer credentials and you should see the newly created staging repository listed. If you
click on that you can inspect the various staged artifacts.
1. Validate that all the various aspects of the staged artifacts appear correct
@@ -239,16 +239,16 @@ click on that you can inspect the various staged artifacts.
- Validate the signature for the build and hashes.
- Validate the LICENSE/NOTICE/Headers.
- Validate that the README is present and provides sufficient information to build and if necessary execute.
-
+
1. The validated artifacts all look good then push the branch to origin release branch to the ASF repository.
```
$ git push asf NIFI-${JIRA_TICKET}-RC${RC}
```
1. Create the signature and hashes for the source release and convenience binary files.
- 1. ASCII armored GPG signatures (`--digest-algo=SHA512` select the SHA512 hash algorithm). [Configure GPG to always prefer stronger hashes](https://www.apache.org/dev/openpgp.html#key-gen-avoid-sha1).
+ 1. ASCII armored GPG signatures (`--digest-algo=SHA512` select the SHA512 hash algorithm). [Configure GPG to always prefer stronger hashes](https://www.apache.org/dev/openpgp.html#key-gen-avoid-sha1).
```
- $ gpg -a -b --digest-algo=SHA512 nifi-${NIFI_VERSION}-source-release.zip # produces nifi-${NIFI_VERSION}-source-release.zip.asc
+ $ gpg -a -b --digest-algo=SHA512 nifi-${NIFI_VERSION}-source-release.zip # produces nifi-${NIFI_VERSION}-source-release.zip.asc
$ gpg -a -b --digest-algo=SHA512 nifi-${NIFI_VERSION}-bin.tar.gz # produces nifi-${NIFI_VERSION}-bin.tar.gz.asc
$ gpg -a -b --digest-algo=SHA512 nifi-${NIFI_VERSION}-bin.zip # produces nifi-${NIFI_VERSION}-bin.zip.asc
```
@@ -271,67 +271,67 @@ click on that you can inspect the various staged artifacts.
$ shasum -a 256 nifi-${NIFI_VERSION}-bin.zip | cut -d" " -f1 > nifi-${NIFI_VERSION}-bin.zip.sha256
```
-1. For reviewing of the release candidate, commit the source release and convenience binaries files along with their
+1. For reviewing of the release candidate, commit the source release and convenience binaries files along with their
hashes and signatures to `https://dist.apache.org/repos/dist/dev/nifi-${NIFI_VERSION}`.
### Step 4. Error recovery (RM)
-If anything isn't correct about the staged artifacts you can drop the staged repo from repository.apache.org and delete
-the local tag in git. If you also delete the local branch and clear your local maven repository under org/apache/nifi
-then it is as if the release never happened. Before doing that though try to figure out what went wrong so the Release
+If anything isn't correct about the staged artifacts you can drop the staged repo from repository.apache.org and delete
+the local tag in git. If you also delete the local branch and clear your local maven repository under org/apache/nifi
+then it is as if the release never happened. Before doing that though try to figure out what went wrong so the Release
Guide can be updated or corrected if necessary.
-
-So, as has been described here you can test the release process until you get it right. The `mvn versions:set` and
-`mvn versions:commit` commands can come in handy to help do this so you can set versions to something clearly release
+
+So, as has been described here you can test the release process until you get it right. The `mvn versions:set` and
+`mvn versions:commit` commands can come in handy to help do this so you can set versions to something clearly release
test related.
### Step 5. Release Vote (RM and community)
-After the release source and artifacts are staged in the repositories it's time for the RM to send a release vote to the
+After the release source and artifacts are staged in the repositories it's time for the RM to send a release vote to the
NiFi community.
-Once the release vote is called for, members of the NiFi developer community have 72 hours to evaluate the RC and
+Once the release vote is called for, members of the NiFi developer community have 72 hours to evaluate the RC and
cast their vote by replying to the "[VOTE] Release ..." email sent by the RM.
-
-_NOTE: The release vote is majority rule vote that must include at least 3 binding +1 votes Apache NiFi PMC members
-and more positive than negative binding votes._
+
+_NOTE: The release vote is majority rule vote that must include at least 3 binding +1 votes Apache NiFi PMC members
+and more positive than negative binding votes._
1. RM sends a vote request email to the NiFi Developers Mailing List.
- TO: `dev@nifi.apache.org`
- FROM: `${RM_USERID}@apache.org`
- SUBJECT: `[VOTE] Release Apache NiFi ${NIFI_VERSION}`
```
- Hello,
-
+ Hello,
+
I am pleased to be calling this vote for the source release of Apache NiFi nifi-${NIFI_VERSION}.
-
+
The source zip, including signatures, digests, etc. can be found at:
https://repository.apache.org/content/repositories/orgapachenifi-nnnn
-
+
The Git tag is nifi-${NIFI_VERSION}-RC${RC}
The Git commit ID is <40-BYTE-COMMIT-HASH>
https://git-wip-us.apache.org/repos/asf?p=nifi.git;a=commit;h=<40-BYTE-COMMIT-HASH>
-
+
Checksums of nifi-x.y.z-source-release.zip:
MD5: <32-BYTE-MD5SUM-HASH>
SHA1: <40-BYTE-SHA1SUM-HASH>
-
+
Release artifacts are signed with the following key:
https://people.apache.org/keys/committer/${RM_USERID}.asc
-
+
KEYS file available here:
https://dist.apache.org/repos/dist/release/nifi/KEYS
-
+
8 issues were closed/resolved for this release:
https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=12316020&version=12329307
-
+
Release note highlights can be found here:
https://cwiki.apache.org/confluence/display/NIFI/Release+Notes#ReleaseNotes-Version${NIFI_VERSION}
-
+
The vote will be open for 72 hours.
- Please download the release candidate and evaluate the necessary items including checking hashes, signatures, build
+ Please download the release candidate and evaluate the necessary items including checking hashes, signatures, build
from source, and test. The please vote:
-
+
[ ] +1 Release this package as nifi-${NIFI_VERSION}
[ ] +0 no opinion
[ ] -1 Do not release this package because because...
@@ -343,62 +343,62 @@ and more positive than negative binding votes._
- SUBJECT: `Apache NiFi ${NIFI_VERSION} RC${RC} Release Helper Guide`
```
Hello Apache NiFi community,
-
+
Please find the associated guidance to help those interested in validating/verifying the release so they can vote.
-
+
# Download latest KEYS file:
https://dist.apache.org/repos/dist/dev/nifi/KEYS
-
+
# Import keys file:
gpg --import KEYS
-
+
# [optional] Clear out local maven artifact repository
-
+
# Pull down nifi-${NIFI_VERSION} source release artifacts for review:
-
+
wget https://dist.apache.org/repos/dist/dev/nifi/nifi-${NIFI_VERSION}/nifi-${NIFI_VERSION}-source-release.zip
wget https://dist.apache.org/repos/dist/dev/nifi/nifi-${NIFI_VERSION}/nifi-${NIFI_VERSION}-source-release.zip.asc
wget https://dist.apache.org/repos/dist/dev/nifi/nifi-${NIFI_VERSION}/nifi-${NIFI_VERSION}-source-release.zip.md5
wget https://dist.apache.org/repos/dist/dev/nifi/nifi-${NIFI_VERSION}/nifi-${NIFI_VERSION}-source-release.zip.sha1
wget https://dist.apache.org/repos/dist/dev/nifi/nifi-${NIFI_VERSION}/nifi-${NIFI_VERSION}-source-release.zip.sha256
-
+
# Verify the signature
gpg --verify nifi-${NIFI_VERSION}-source-release.zip.asc
-
+
# Verify the hashes (md5, sha1, sha256) match the source and what was provided in the vote email thread
md5sum nifi-${NIFI_VERSION}-source-release.zip
sha1sum nifi-${NIFI_VERSION}-source-release.zip
sha256sum nifi-${NIFI_VERSION}-source-release.zip
-
+
# Unzip nifi-${NIFI_VERSION}-source-release.zip
-
+
# Verify the build works including release audit tool (RAT) checks
cd nifi-${NIFI_VERSION}
mvn clean install -Pcontrib-check
-
+
# Verify the contents contain a good README, NOTICE, and LICENSE.
-
+
# Verify the git commit ID is correct
-
+
# Verify the RC was branched off the correct git commit ID
-
+
# Look at the resulting convenience binary as found in nifi-assembly/target
-
+
# Make sure the README, NOTICE, and LICENSE are present and correct
-
+
# Run the resulting convenience binary and make sure it works as expected
-
+
# Send a response to the vote thread indicating a +1, 0, -1 based on your findings.
-
+
Thank you for your time and effort to validate the release!
```
1. Developers in the community review the release candiate 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
-
- the vote passes and the release candidate is officially released. If the vote does not pass, corrections are made
+ - the positive binding votes out number any negative binding votes
+
+ the vote passes and the release candidate is officially released. If the vote does not pass, corrections are made
on the release branch and a new release candidate is put forward for a new vote.
1. RM sends vote result email.
@@ -407,15 +407,15 @@ and more positive than negative binding votes._
- SUBJECT: `[RESULT][VOTE] Release Apache NiFi ${NIFI_VERSION}`
```
Apache NiFi Community,
-
+
I am pleased to announce that the ${NIFI_VERSION} release of Apache NiFi passes with
X +1 (binding) votes
Y -1 (binding) votes
0 0 votes
0 -1 votes
-
+
Thanks to all who helped make this release possible.
-
+
Here is the PMC vote thread: ${VOTE_THREAD_URL}
```
@@ -435,10 +435,10 @@ After the vote is complete and the release is approved, these steps complete the
```
$ git push asf NIFI-${JIRA_TICKET}
```
-1. Update the NiFi website to point to the new download(s). Remove older release artifacts from download page (leave
-the current release and the previous one). For the release just previous to this new one change the links to point to
-the archive location. See current page as an example of the needed URL changes. In addition to updating the download
-page as described delete artifacts other than the current/new release from the dist/nifi SVN storage. They are already
+1. Update the NiFi website to point to the new download(s). Remove older release artifacts from download page (leave
+the current release and the previous one). For the release just previous to this new one change the links to point to
+the archive location. See current page as an example of the needed URL changes. In addition to updating the download
+page as described delete artifacts other than the current/new release from the dist/nifi SVN storage. They are already
in the archive location so no need to do anything else.
1. Update the [Migration Guide][nifi-migration-guide] on the Wiki.
@@ -459,7 +459,7 @@ in the archive location so no need to do anything else.
$ git tag -s rel/nifi-${NIFI_VERSION} -m "${JIRA_TICKET} signed release tag for approved release of NiFi ${NIFI_VERSION}" ${RC_TAG_COMMIT_ID}
```
For instructions on setting up to sign your tag see [here][git-sign-tag-instructs].
-
+
1. Push the release tag to the official ASF repository.
```
$ git push asf rel/nifi-${NIFI_VERSION} rel/nifi-${NIFI_VERSION}
@@ -475,58 +475,58 @@ in the archive location so no need to do anything else.
- FROM: ${RM_USERID}@apache.org
+ The subject should include `[ANNOUNCE] Apache NiFi x.y.z release`.
+ The text should on the template included below.
- +
-
+ +
+
```
Hello
-
+
The Apache NiFi team would like to announce the release of Apache NiFi ${NIFI_VERSION}.
-
- Apache NiFi is an easy to use, powerful, and reliable system to process and distribute
- data. Apache NiFi was made for dataflow. It supports highly configurable directed graphs
+
+ Apache NiFi is an easy to use, powerful, and reliable system to process and distribute
+ data. Apache NiFi was made for dataflow. It supports highly configurable directed graphs
of data routing, transformation, and system mediation logic.
-
+
More details on Apache NiFi can be found here:
- http://nifi.apache.org/
-
+ https://nifi.apache.org/
+
The release artifacts can be downloaded from here:
- http://nifi.apache.org/download.html
-
+ https://nifi.apache.org/download.html
+
Maven artifacts have been made available here:
https://repository.apache.org/content/repositories/releases/org/apache/nifi/
-
+
Issues closed/resolved for this list can be found here:
https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=12316020&version=12329373
-
+
Release note highlights can be found here:
https://cwiki.apache.org/confluence/display/NIFI/Release+Notes#ReleaseNotes-Version${NIFI_VERSION}
-
+
Thank you
The Apache NiFi team
```
-[nifi-quickstart-guide]: http://nifi.apache.org/quickstart.html
+[nifi-quickstart-guide]: https://nifi.apache.org/quickstart.html
[nifi-release-notes]: https://cwiki.apache.org/confluence/display/NIFI/Release+Notes
[nifi-migration-guide]: https://cwiki.apache.org/confluence/display/NIFI/Migration+Guidance
-[apache-encryption]: http://www.apache.org/licenses/exports/
+[apache-encryption]: https://www.apache.org/licenses/exports/
[apache-glossary-committer]: https://www.apache.org/foundation/glossary.html#Committer
[apache-glossary-community]: https://www.apache.org/foundation/glossary.html#Community
[apache-glossary-pmc]: https://www.apache.org/foundation/glossary.html#PMC
-[apache-guide-publish-maven]: http://www.apache.org/dev/publishing-maven-artifacts.html
-[apache-legal-resolve]: http://www.apache.org/legal/resolved.html
-[apache-license]: http://apache.org/licenses/LICENSE-2.0
-[apache-license-apply]: http://www.apache.org/dev/apply-license.html
-[apache-pgp]: http://www.apache.org/dev/openpgp.html
-[apache-release-announce]: http://www.apache.org/dev/release.html#release-announcements
-[apache-release-guide]: http://www.apache.org/dev/release-publishing
-[apache-release-manager]: http://www.apache.org/dev/release-publishing.html#release_manager
-[apache-release-policy]: http://www.apache.org/dev/release.html
+[apache-guide-publish-maven]: https://www.apache.org/dev/publishing-maven-artifacts.html
+[apache-legal-resolve]: https://www.apache.org/legal/resolved.html
+[apache-license]: https://apache.org/licenses/LICENSE-2.0
+[apache-license-apply]: https://www.apache.org/dev/apply-license.html
+[apache-pgp]: https://www.apache.org/dev/openpgp.html
+[apache-release-announce]: https://www.apache.org/dev/release.html#release-announcements
+[apache-release-guide]: https://www.apache.org/dev/release-publishing
+[apache-release-manager]: https://www.apache.org/dev/release-publishing.html#release_manager
+[apache-release-policy]: https://www.apache.org/dev/release.html
[apache-release-signing]: http://www.apache.org/dev/release-signing.html
-[apache-signature-verify]: http://www.apache.org/dev/release-signing.html#verifying-signature
+[apache-signature-verify]: https://www.apache.org/dev/release-signing.html#verifying-signature
[apache-staging-repositories]: https://repository.apache.org/#stagingRepositories
[git-sign-tag-instructs]: http://gitready.com/advanced/2014/11/02/gpg-sign-releases.html
[sonatype-maven-password]: http://blog.sonatype.com/2009/10/maven-tips-and-tricks-encrypting-passwords
-[070-rc2-vote]: https://lists.apache.org/thread.html/8b111ce611238af8b71b95039c299ae0a1ec063ea77f83aa34e6a2bd@%3Cdev.nifi.apache.org%3E
\ No newline at end of file
+[070-rc2-vote]: https://lists.apache.org/thread.html/8b111ce611238af8b71b95039c299ae0a1ec063ea77f83aa34e6a2bd@%3Cdev.nifi.apache.org%3E