Return-Path: X-Original-To: archive-asf-public-internal@cust-asf2.ponee.io Delivered-To: archive-asf-public-internal@cust-asf2.ponee.io Received: from cust-asf.ponee.io (cust-asf.ponee.io [163.172.22.183]) by cust-asf2.ponee.io (Postfix) with ESMTP id D305D200B4B for ; Thu, 7 Jul 2016 06:05:59 +0200 (CEST) Received: by cust-asf.ponee.io (Postfix) id D17FF160A73; Thu, 7 Jul 2016 04:05:59 +0000 (UTC) Delivered-To: archive-asf-public@cust-asf.ponee.io Received: from mail.apache.org (hermes.apache.org [140.211.11.3]) by cust-asf.ponee.io (Postfix) with SMTP id A82C2160A64 for ; Thu, 7 Jul 2016 06:05:58 +0200 (CEST) Received: (qmail 63225 invoked by uid 500); 7 Jul 2016 04:05:57 -0000 Mailing-List: contact dev-help@nifi.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: dev@nifi.apache.org Delivered-To: mailing list dev@nifi.apache.org Received: (qmail 63212 invoked by uid 99); 7 Jul 2016 04:05:57 -0000 Received: from pnap-us-west-generic-nat.apache.org (HELO spamd3-us-west.apache.org) (209.188.14.142) by apache.org (qpsmtpd/0.29) with ESMTP; Thu, 07 Jul 2016 04:05:57 +0000 Received: from localhost (localhost [127.0.0.1]) by spamd3-us-west.apache.org (ASF Mail Server at spamd3-us-west.apache.org) with ESMTP id E74991804C2 for ; Thu, 7 Jul 2016 04:05:56 +0000 (UTC) X-Virus-Scanned: Debian amavisd-new at spamd3-us-west.apache.org X-Spam-Flag: NO X-Spam-Score: 1.549 X-Spam-Level: * X-Spam-Status: No, score=1.549 tagged_above=-999 required=6.31 tests=[HEADER_FROM_DIFFERENT_DOMAINS=0.001, HTML_MESSAGE=2, KAM_LOTSOFHASH=0.25, RCVD_IN_DNSWL_LOW=-0.7, RCVD_IN_MSPIKE_H2=-0.001, SPF_PASS=-0.001] autolearn=disabled Received: from mx2-lw-us.apache.org ([10.40.0.8]) by localhost (spamd3-us-west.apache.org [10.40.0.10]) (amavisd-new, port 10024) with ESMTP id RQooZgO-Zt8O for ; Thu, 7 Jul 2016 04:05:53 +0000 (UTC) Received: from mail-pf0-f180.google.com (mail-pf0-f180.google.com [209.85.192.180]) by mx2-lw-us.apache.org (ASF Mail Server at mx2-lw-us.apache.org) with ESMTPS id AF5075FE33 for ; Thu, 7 Jul 2016 04:05:52 +0000 (UTC) Received: by mail-pf0-f180.google.com with SMTP id h14so2352681pfe.1 for ; Wed, 06 Jul 2016 21:05:52 -0700 (PDT) X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20130820; h=x-gm-message-state:mime-version:subject:from:in-reply-to:date :message-id:references:to; bh=xPjf7CdQlBXhqdf6tzI17IINrcgclRIn7CBjReJSEEo=; b=lGQdZxu/XgRXR3sK55dMi9L+TF7RpeC6WlrsGe7VMfYMXVJxCz0Fmg2TU2ym5wnaNV dyVOJ2myLz0xznSS7/eKrnA0RfVf2qpoRApsGx9gcuI0GZdPRnjl4/PZvkJlmCm2pLIr fp5wUlNoVH3TAOtR3ndaNp596iyMUNTCn2KQmMXTBohhQWkw2lMHnLtey3mJRUG/lHSi CjWCEx/a5daUxdpxH39RkVUpkb5YMh82on+KuQ7w6MtvX3u2NwhVw0cWyktgqpFyn4kr B+0C/Ah8gDPVU43FaxE9b4VFOrR40vE7KyR0qxZWi/0tv3cLvC9Cy8rKtT/CPDnkCn2Q vrDg== X-Gm-Message-State: ALyK8tKAYv9C2+gPEp1BZt49fth7d3jO9y2SPKHEroc1CS83t9GLC7vFnjM5TiZEZFndOA== X-Received: by 10.98.86.72 with SMTP id k69mr1548018pfb.166.1467864346011; Wed, 06 Jul 2016 21:05:46 -0700 (PDT) Received: from [192.168.1.3] (cpe-172-91-141-241.socal.res.rr.com. [172.91.141.241]) by smtp.gmail.com with ESMTPSA id yp4sm833332pab.48.2016.07.06.21.05.44 for (version=TLS1 cipher=ECDHE-RSA-AES128-SHA bits=128/128); Wed, 06 Jul 2016 21:05:45 -0700 (PDT) Content-Type: multipart/signed; boundary="Apple-Mail=_B0231849-830F-4A5F-AB25-ACA3DC1D5D51"; protocol="application/pgp-signature"; micalg=pgp-sha512 Mime-Version: 1.0 (Mac OS X Mail 9.3 \(3124\)) Subject: Re: [VOTE] Release Apache NiFi MiNiFi 0.0.1 (RC1) X-Pgp-Agent: GPGMail 2.6b2 From: Andy LoPresto In-Reply-To: Date: Wed, 6 Jul 2016 21:06:18 -0700 Message-Id: References: To: dev@nifi.apache.org X-Mailer: Apple Mail (2.3124) archived-at: Thu, 07 Jul 2016 04:06:00 -0000 --Apple-Mail=_B0231849-830F-4A5F-AB25-ACA3DC1D5D51 Content-Type: multipart/alternative; boundary="Apple-Mail=_5AF637D6-A116-4823-9D03-D9729C4303E0" --Apple-Mail=_5AF637D6-A116-4823-9D03-D9729C4303E0 Content-Transfer-Encoding: quoted-printable Content-Type: text/plain; charset=utf-8 Hi, I verified the GPG signature and all hash signatures. Contrib check ran = fine. I used one of the example config.yml files in the System Admin Guide and = deployed it to the compiled binary. The tool ran successfully and wrote = to a log file on my system. I have a couple notes about the release but = nothing blocking. +1 (non-binding) Notes/questions: README.md: * Could we use HTTPS links when possible? * The note about the time to run a parallel Maven build says on a = moderate dev laptop it should complete in less than 10 minutes. While = true, a more accurate statement would be < 2 minutes. * The mkdir example references =E2=80=9Cexample-nifi-deploy=E2=80=9D and = =E2=80=9Cexample-minifi-deploy=E2=80=9D interchangeably. * Are there separate MiNiFi mailing lists and IRC nodes coming? System Admin Guide: * Could we use HTTPS links when possible? config.yml: * Could we please change the default algorithm for protecting sensitive = property values to something stronger than the current selection? I = would open a Jira if necessary, but this is one of those things that is = really better to do before the first release so users have a = backward-compatible config.yml file moving forward. If we change it in a = subsequent release, we will need to do significant migration = hand-holding. My suggestion would be = "PBEWITHSHA256AND256BITAES-CBC-BC=E2=80=9D which is significantly = stronger, but after trying a few BC options, I continue to get = EncryptionExceptions even though I have the JCE unlimited cryptographic = strength jurisdiction policy files installed, so this may be a 0.0.2 = fix. Is BouncyCastle not enabled by default? * Question about how processors and connectors reference each other =E2=80= =94 it appears connectors reference source processors by name but = destination processors or ports by ID? Is this consistent or just = demonstrating the flexibility of the system? Also, what enforces = processor name uniqueness, as this is not an existing feature of NiFi. All in all looks like a lot of great work and will expand the user base = and opportunities for NiFi significantly. Thanks. Andy LoPresto alopresto@apache.org alopresto.apache@gmail.com PGP Fingerprint: 70EC B3E5 98A6 5A3F D3C4 BACE 3C6E F65B 2F7D EF69 > On Jul 6, 2016, at 7:27 PM, Aldrin Piri wrote: >=20 > Hello Apache NiFi Community, >=20 > I am pleased to be calling this vote for the source release of Apache = NiFi > - MiNiFi, > minifi-0.0.1. >=20 > The source zip, including signatures, digests, etc. can be found at: > https://repository.apache.org/content/repositories/orgapachenifi-1087 >=20 > The Git tag is minifi-0.0.1-RC1 >=20 > The Git commit hash is d6ebeda6bce8259f0531e8455965625333315bdb > * > = https://git-wip-us.apache.org/repos/asf?p=3Dnifi-minifi.git;a=3Dcommit;h=3D= d6ebeda6bce8259f0531e8455965625333315bdb >=20 > * > = https://github.com/apache/nifi-minifi/commit/d6ebeda6bce8259f0531e84559656= 25333315bdb >=20 > Checksums of minifi-0.0.1-source-release.zip: > MD5: b63355fb419ca09b26fe12485b3bf4a5 > SHA1: 4c9352b7d4d53d139a707dbdcd03df73dbfb847d > SHA256: = d52e7f614afe6aee05e6796e429f2813b51f36d2b6d83a4c08a1fb1fdb50b2ff >=20 > Release artifacts are signed with the following key: > https://people.apache.org/keys/committer/aldrin >=20 > KEYS file available here: > https://dist.apache.org/repos/dist/release/nifi/KEYS >=20 > 30 issues were closed/resolved for this release: > = https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=3D1231602= 0&version=3D12335481 >=20 > Release note highlights can be found here: > = https://cwiki.apache.org/confluence/display/MINIFI/Release+Notes#ReleaseNo= tes-Version0.0.1 >=20 > 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. = Then > please vote: >=20 > [ ] +1 Release this package as minifi-0.0.1 > [ ] +0 no opinion > [ ] -1 Do not release this package because... >=20 > Thanks! --Apple-Mail=_5AF637D6-A116-4823-9D03-D9729C4303E0 Content-Transfer-Encoding: quoted-printable Content-Type: text/html; charset=utf-8 Hi,

I = verified the GPG signature and all hash signatures. Contrib check ran = fine. 

I = used one of the example config.yml files in the System Admin Guide and = deployed it to the compiled binary. The tool ran successfully and wrote = to a log file on my system. I have a couple notes about the release but = nothing blocking. 

+1 (non-binding)

Notes/questions:

README.md:
* Could = we use HTTPS links when possible?
* The note about = the time to run a parallel Maven build says on a moderate dev laptop it = should complete in less than 10 minutes. While true, a more accurate = statement would be < 2 minutes. 
* The = mkdir example references =E2=80=9Cexample-nifi-deploy=E2=80=9D and = =E2=80=9Cexample-minifi-deploy=E2=80=9D interchangeably. =  
* Are there separate MiNiFi mailing lists = and IRC nodes coming?

System Admin Guide:
* Could we use HTTPS = links when possible?

config.yml:
* Could we please change the = default algorithm for protecting sensitive property values to something = stronger than the current selection? I would open a Jira if necessary, = but this is one of those things that is really better to do before the = first release so users have a backward-compatible config.yml file moving = forward. If we change it in a subsequent release, we will need to do = significant migration hand-holding. My suggestion would be = "PBEWITHSHA256AND256BITAES-CBC-BC=E2=80=9D which is significantly = stronger, but after trying a few BC options, I continue to get = EncryptionExceptions even though I have the JCE unlimited cryptographic = strength jurisdiction policy files installed, so this may be a 0.0.2 = fix. Is BouncyCastle not enabled by default?
* = Question about how processors and connectors reference each other =E2=80=94= it appears connectors reference source processors by name but = destination processors or ports by ID? Is this consistent or just = demonstrating the flexibility of the system? Also, what enforces = processor name uniqueness, as this is not an existing feature of NiFi. =  

All in = all looks like a lot of great work and will expand the user base and = opportunities for NiFi significantly. Thanks. 

Andy = LoPresto
alopresto@apache.org
alopresto.apache@gmail.com
PGP Fingerprint: 70EC = B3E5 98A6 5A3F D3C4  BACE 3C6E F65B 2F7D EF69

On Jul 6, 2016, at 7:27 PM, Aldrin Piri <aldrinpiri@gmail.com> wrote:

Hello = Apache NiFi Community,

I am pleased to be = calling this vote for the source release of Apache NiFi
- = MiNiFi,
minifi-0.0.1.

The = source zip, including signatures, digests, etc. can be found at:
https://repository.apache.org/content/repositories/orgapachenif= i-1087

The Git tag is = minifi-0.0.1-RC1

The Git commit hash is = d6ebeda6bce8259f0531e8455965625333315bdb
*
https://git-wip-us.apache.org/repos/asf?p=3Dnifi-minifi.git;a=3D= commit;h=3Dd6ebeda6bce8259f0531e8455965625333315bdb

*
https://github.com/apache/nifi-minifi/commit/d6ebeda6bce8259f05= 31e8455965625333315bdb

Checksums of = minifi-0.0.1-source-release.zip:
MD5: = b63355fb419ca09b26fe12485b3bf4a5
SHA1: = 4c9352b7d4d53d139a707dbdcd03df73dbfb847d
SHA256: = d52e7f614afe6aee05e6796e429f2813b51f36d2b6d83a4c08a1fb1fdb50b2ff

Release artifacts are signed with the = following key:
https://people.apache.org/keys/committer/aldrin

KEYS file available here:
https://dist.apache.org/repos/dist/release/nifi/KEYS

30 issues were closed/resolved for this = release:
https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectI= d=3D12316020&version=3D12335481

Release = note highlights can be found here:
https://cwiki.apache.org/confluence/display/MINIFI/Release+Note= s#ReleaseNotes-Version0.0.1

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. Then
please vote:

[ ] +1 Release this = package as minifi-0.0.1
[ ] +0 no opinion
[ = ] -1 Do not release this package because...

Thanks!

= --Apple-Mail=_5AF637D6-A116-4823-9D03-D9729C4303E0-- --Apple-Mail=_B0231849-830F-4A5F-AB25-ACA3DC1D5D51 Content-Transfer-Encoding: 7bit Content-Disposition: attachment; filename=signature.asc Content-Type: application/pgp-signature; name=signature.asc Content-Description: Message signed with OpenPGP using GPGMail -----BEGIN PGP SIGNATURE----- Comment: GPGTools - https://gpgtools.org iQIcBAEBCgAGBQJXfdU7AAoJEDxu9lsvfe9pQzEP/0nJ07ekjfsu0CJEFd2qSu6S KdmAffwQhC7d/z0wGe4rJNO80IYa9pXzNdhesO+Y2g8UvDUx+kWDusiMPRH7iWzs PqTCF/55svuF+HrQ4rq47m0x6IGPQAP11D88NmEyDMS7zZNAZQBzw9wVBUQBKqIi kOHZYe1T26PQGKWnHc7nc6gyCiHr+ag0m7Rm36woWRNq1WzDerGDJeK0FA71+cu/ 9pG048bHXuv6W1iTQ5krhq+WUK9NUFqb+SxczVvnMxjYpeYOTLMg7VV7CKRm/Nn0 mFvItDBgKJanQQoUamax7ud89EAovvYdx3v0VPh0wlH6spWwdQlqOEewz85GjxNf M4UyBx99yOYsVkySlbTCuliip91DkA5+GkF3s42PXnRm87Q4y7mhAlNJFMYLubB7 wLjilKolsxRt6aVHh18Rd0MPBh007MkVB6zuyuB0Ibfxk2R6d6NhXX4uHhMJDYqe VTQ88KeI46bUnHNtQqqzFYdeJ5KDXPl+SxK2QWKhwdWpeZ+axJg/O31H9QEP26uY VmlMxbPbI7etXbglRBwsQVHhBk69Cb4kH8qxQYJDBmbxqI5emIueSjqrFPp1UqOA szNFxEZXK5TJAHY+ssC51BhJMrqt09qiKcseWD/PUdQuBxxkTM3+csXkfbHzoa2e 4UsuQdx4tgUG1mnQc3ri =xcxY -----END PGP SIGNATURE----- --Apple-Mail=_B0231849-830F-4A5F-AB25-ACA3DC1D5D51--