Requesting a courtesy extra day please :-) On Sat, Jun 25, 2016 at 11:12 AM, Joe Witt <[email protected]> wrote:
> Timing these is not easy. But requesting a courtesy weekend extra day is > totally reasonable and has been done in the past. > On Jun 25, 2016 8:09 AM, "Ryan H" <[email protected]> wrote: > > > I'd love to get the opportunity to test the nifi-0.7.0-RC1 tag on my > > integration server at work.. Seeing as though the voting started Friday > at > > 3:34.. and ends Monday at 3:34, I'm not sure I'll get the opportunity. > > > > Recommend in the future this is done mon-fri vs the weekend. > > > > Ryan > > > > On Sat, Jun 25, 2016 at 10:39 AM, Joe Witt <[email protected]> wrote: > > > > > Not quite ready to vote but here is the status of my review. > > > > > > Checked out the build/commit/hashes/etc.. and all those things checked > > out. > > > > > > Extraneous file: > > > - It has /appveyor.yml file. Obviously this is not a big deal but > > > should be ignored from source release somehow. > > > Recommendation: File a JIRA to to block this from being in the source > > > release. > > > > > > Licensing concerns > > > - The LICENSE file has this entry "This product bundles 'Jolt' which > > > is available under an Apache License" > > > We should not have apache licensed items in our license file. We > > > only need to carry forward NOTICE information of such dependencies and > > > those would go in our NOTICE if applicable. > > > - The nifi-assembly/NOTICE file has an "MIT License" section. This > > > should be removed. MIT licensed items should be reflected in the > > > LICENSE file and Luaj already appears to be there. > > > - The nifi-assembly/NOTICE file references "Python Software > > > Foundation" section. Python license is category A. Such dependency > > > belongs in LICENSE file and not NOTICE. Only if that dependency has a > > > NOTICE with legally required items should there be a reference to it. > > > Recommendation: File a JIRA to correct these items. > > > > > > Functional issue > > > - Cannot get a secured cluster working that worked well on 0.6.0. > > > After upgrading now seeing the following line. It either means I > > > upgraded incorrectly, or we're missing critical migration guidance, or > > > we have introduced a new bug. I cannot login to the cluster and in > > > the nifi-user.log of the NCM if found this entry: > > > 2016-06-25 14:19:12,017 INFO [NiFi Web Server-23] > > > o.a.n.w.a.c.IllegalArgumentExceptionMapper > > > java.lang.IllegalArgumentException: User account already created > > > CN=box1.testing.org, OU=NIFI, O=Apache-NiFi, L=Here, ST=There, > > > C=EVERYWHERE. Returning Bad Request response. > > > Status: Still looking into this. Do not yet understand what is > > happening. > > > > > > We presently do not have migration guidance for moving from 0.6 to > > > 0.7. This may be correct but wanted to verify. > > > > > > Thanks > > > Joe > > > > > > On Sat, Jun 25, 2016 at 6:55 AM, Pierre Villard > > > <[email protected]> wrote: > > > > Hi, > > > > > > > > +1 > > > > > > > > Thanks Joe for the amazing work to have this RC out. > > > > > > > > Ran through the helper release guide. > > > > Signature and checksums are OK. > > > > Maven build with tests and contrib-check OK on Windows 10. > > > > Tested some flows and everything looks OK. > > > > > > > > -Pierre > > > > > > > > > > > > 2016-06-24 21:34 GMT+02:00 Joe Percivall > > <[email protected] > > > >: > > > > > > > >> Hello Apache NiFi Community, > > > >> > > > >> I am pleased to be calling this vote for the source release of > Apache > > > NiFi, > > > >> nifi-0.7.0. > > > >> > > > >> The source zip, including signatures, digests, etc. can be found at: > > > >> > > https://repository.apache.org/content/repositories/orgapachenifi-1083/ > > > >> > > > >> The Git tag is nifi-0.7.0-RC1 > > > >> The Git commit hash is 56dc8aefac822454f2d4133e8cbde903a628ec5b > > > >> * > > > >> > > > > > > https://git-wip-us.apache.org/repos/asf?p=nifi.git;a=commit;h=56dc8aefac822454f2d4133e8cbde903a628ec5b > > > >> * > > > >> > > > > > > https://github.com/apache/nifi/commit/56dc8aefac822454f2d4133e8cbde903a628ec5b > > > >> > > > >> Checksums of nifi-0.7.0-source-release.zip: > > > >> MD5: 8dc31d1f8103f9679cfe4b9533a4049b > > > >> SHA1: dc160c9611dc18523c994cd9086fc7088cc520f4 > > > >> SHA256: > > 7df056fb6af0eb9bdb94c17bf5bc2db288ed2b0d0a8ad23127dab5cdf74ce767 > > > >> > > > >> Release artifacts are signed with the following key: > > > >> http://pgp.mit.edu/pks/lookup?op=get&search=0x3C6DBAFE22886FEE > > > >> > > > >> KEYS file available here: > > > >> https://dist.apache.org/repos/dist/release/nifi/KEYS > > > >> > > > >> 131 issues were closed/resolved for this release: > > > >> > > > >> > > > > > > https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=12316020&version=12335078 > > > >> Release note highlights can be found here: > > > >> > > > >> > > > > > > https://cwiki.apache.org/confluence/display/NIFI/Release+Notes#ReleaseNotes-Version0.7.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. > > Then > > > >> please vote: > > > >> > > > >> [ ] +1 Release this package as nifi-0.7.0 > > > >> [ ] +0 no opinion > > > >> [ ] -1 Do not release this package because... > > > >> > > > > > >
