+1, binding.

   * Verified sigs/hashes
   * Used release guide with no issues
   * Ran through some tests with flow versioning functionality.
   * Ran usual test flows



On Wed, Jan 10, 2018 at 6:38 AM, Marco Gaido <marcogaid...@gmail.com> wrote:

> +1 (not binding). Ran through release guide with no issues and run some
> workflows.
>
> 2018-01-10 4:41 GMT+01:00 Jeremy Dyer <jdy...@gmail.com>:
>
> > +1 non binding. Ran through release guide with no issues and ran several
> > test workflows from personal projects
> >
> > - Jeremy Dyer
> >
> > > On Jan 9, 2018, at 8:11 PM, Andy LoPresto <alopre...@apache.org>
> wrote:
> > >
> > > +1, binding
> > >
> > > I performed the following verifications:
> > >
> > > * verified the GPG key signature
> > > * verified the MD5/SHA1/SHA256 checksums
> > > * verified the git commit ID
> > > * verified the presence of LICENSE, NOTICE, and README
> > > * verified the Maven build was successful, including all unit tests,
> RAT
> > check, and code style guidelines
> > > * verified the application started successfully
> > > * verified the new behavior for host header handling was present
> > > * verified the application integrates successfully with the Apache NiFi
> > Registry
> > > * verified the CountText processor works as anticipated
> > > * verified the flow versioning functionality by making local changes,
> > committing, and restoring prior versions of the flow
> > >
> > > Andy LoPresto
> > > alopre...@apache.org
> > > alopresto.apa...@gmail.com
> > > PGP Fingerprint: 70EC B3E5 98A6 5A3F D3C4  BACE 3C6E F65B 2F7D EF69
> > >
> > >> On Jan 9, 2018, at 9:13 AM, Mark Payne <marka...@hotmail.com> wrote:
> > >>
> > >> +1 (binding) - Release this package as nifi-1.5.0
> > >>
> > >> Was able to successfully build with contrib-check and grpc profile.
> > Verified MD5 sum.
> > >> Started up, added a Flow Registry Client pointing to an existing Flow
> > Registry and was
> > >> able to immediately import a flow and start it running. This flow also
> > verified the fix for
> > >> NIFI-4749 made it into the build yesterday.
> > >>
> > >> Thanks for taking on the RM duties this time, Joe! And a big thank you
> > and congrats
> > >> to all of the members of the community that contributed to this
> release
> > - code, JIRA's,
> > >> docs, and support!
> > >>
> > >> Thanks
> > >> -Mark
> > >>
> > >>
> > >>> On Jan 9, 2018, at 5:19 AM, Joe Witt <joew...@apache.org> wrote:
> > >>>
> > >>> Hello,
> > >>>
> > >>> I am pleased to be calling this vote for the source release of Apache
> > >>> NiFi nifi-1.5.0.
> > >>>
> > >>> The source zip, including signatures, digests, etc. can be found at:
> > >>> https://repository.apache.org/content/repositories/
> orgapachenifi-1116
> > >>>
> > >>> The Git tag is nifi-1.5.0-RC1
> > >>> The Git commit ID is 46d30c7e92f0ad034d9b35bf1d05c350ab5547ed
> > >>> https://git-wip-us.apache.org/repos/asf?p=nifi.git;a=commit;h=
> > 46d30c7e92f0ad034d9b35bf1d05c350ab5547ed
> > >>>
> > >>> Checksums of nifi-1.5.0-source-release.zip:
> > >>> MD5: 046f2dde4af592dd8c05e55c2bbb3c4f
> > >>> SHA1: 63b9a68b9f89200fd31f5561956a15b45b1b9c8c
> > >>> SHA256: 40b155c4911414907835f2eb0d5a4da798935f27f1e5134218d904fe6c94
> > 2d13
> > >>>
> > >>> Release artifacts are signed with the following key:
> > >>> https://people.apache.org/keys/committer/joewitt.asc
> > >>>
> > >>> KEYS file available here:
> > >>> https://dist.apache.org/repos/dist/release/nifi/KEYS
> > >>>
> > >>> 195 issues were closed/resolved for this release:
> > >>> https://issues.apache.org/jira/secure/ReleaseNote.jspa?
> > projectId=12316020&version=12341668
> > >>>
> > >>> Release note highlights can be found here:
> > >>> https://cwiki.apache.org/confluence/display/NIFI/
> > Release+Notes#ReleaseNotes-Version1.5.0
> > >>>
> > >>> 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:
> > >>>
> > >>> [ ] +1 Release this package as nifi-1.5.0
> > >>> [ ] +0 no opinion
> > >>> [ ] -1 Do not release this package because...
> > >>
> > >
> >
>

Reply via email to