+1 (non-binding)
Full build with contrib-check, ran few workflows successfully.
2016-10-19 2:39 GMT+02:00 Koji Kawamura :
> +1 (non-binding)
>
> - git tag and commit ID verified
> - Downloaded nifi-0.7.1-source-release.zip and verified hashes
> - Full build finished
+1 (non-binding)
- git tag and commit ID verified
- Downloaded nifi-0.7.1-source-release.zip and verified hashes
- Full build finished without issue
- Application runs without issue on Mac with java 1.8.0_111-b14
- Found a trivial typo on release note wiki page, updated the wiki
page:
+1 (binding)
reviewed License and notice
Built successfully from source using openjdk 1.8.0 on amazon linux.
verified hashes and signature
ran a few simple flows without issue
On Tue, Oct 18, 2016 at 2:28 PM, Michael Moser wrote:
> +1 (non-binding)
>
> git tag and commit
+1 (non-binding)
git tag and commit ID verified
Downloaded nifi-0.7.1-source-release.zip and verified hashes
Source builds with RAT checks using Java 1.7.0_79
Application runs and a few templates work as expected on CentOS 6
On Tue, Oct 18, 2016 at 1:38 PM, Joe Skora wrote:
Yeah, I'll get my keys added. I didn't want to move the target commit once
we had that zeroed in.
On Tue, Oct 18, 2016 at 6:27 PM, Joe Witt wrote:
> +1 (binding).
>
> full build verification steps all passed/were as expected. L looks
> good. Simple live testing behaved
+1 (binding).
full build verification steps all passed/were as expected. L looks
good. Simple live testing behaved as expected.
Something to address for future purposes is please don't forget to add
your keys to the KEYS file in the 0.x and master.
Thanks for stepping up to take on the RM
+1, I was able to verify hashes, build with tests and checks, run NiFi and
do simple testing. Thanks for putting this release together, Joe.
On Sun, Oct 16, 2016 at 8:32 PM, Joe Skora wrote:
> Hello,
>
> I am pleased to be calling this vote for the source release of Apache
+1 (binding)
Downloaded all artifacts.
Verified GPG signature (with SHA512 digest algorithm).
Verified MD5, SHA1, and SHA256 checksums.
Unzipped and built (contrib-check and all tests passed).
Ran application and smoke tested with simple flows.
Verified NIFI-2373 [1] (GetHTTP not working with TLS
Got it! Makes sense.
On Mon, Oct 17, 2016 at 1:54 PM, Andy LoPresto wrote:
> That should read “please use *at least* SHA-256 as the hash algorithm.”
> SHA-512 and SHA-384 are preferred.
>
> Andy LoPresto
> alopre...@apache.org
> *alopresto.apa...@gmail.com
Andy,
Thanks for catching that. I'm sorry, those both crossed my mind early on,
but once I got into the instructions I tracked to those.
I will fix those add the hash and send the email ASAP.
And I'll look at updating the release instructions this week while it's
fresh in my mind.
Joe
On
That should read “please use *at least* SHA-256 as the hash algorithm.” SHA-512
and SHA-384 are preferred.
Andy LoPresto
alopre...@apache.org
alopresto.apa...@gmail.com
PGP Fingerprint: 70EC B3E5 98A6 5A3F D3C4 BACE 3C6E F65B 2F7D EF69
> On Oct 17, 2016, at 10:53 AM, Andy LoPresto
Joe,
Thanks for preparing the release. Please send the “helper” email to accompany
this (example from 1.0.0 here [1]) and include the SHA-256 hash of the release
ZIP as well.
Similarly, when you perform the GPG signing activity, please use SHA-256 as the
hash algorithm. Currently you are
Hello,
I am pleased to be calling this vote for the source release of Apache NiFi
nifi-0.7.1.
The source zip, including signatures, digests, etc. can be found at:
https://repository.apache.org/content/repositories/orgapachenifi-1091
The Git tag is nifi-0.7.1-RC1
The Git commit ID is
13 matches
Mail list logo