thanks joe . you're doing awesome at the RM thing. Not easy to rally things together and especially difficult now as we're working the 1.x effort in parallel.
By the way I just tried out the thing jskora put in recently for media metadata extraction. Super cool! On Thu, Jun 23, 2016 at 9:16 AM, Joe Percivall <[email protected]> wrote: > Hello Team, > > Thank you all for helping finishing up all the slated 0.7.0 features. > Unfortunately I tested the 0.x branch on Windows 8 I ran into a couple > issues. Two of which are bugs in the test framework that I will fix but the > third has an unknown exact cause and is a blocker. Each of which is listed > below. > > A couple times before during the release process we don't find system > specific issues until the RC vote has already started. In order to try and > alleviate that, I encourage each of you to pull the latest of the 0.x branch > and build on various systems. I have personally run on OS X Yosemite > (10.10.5) and Windows 8. If you run into trouble create an issue and let the > team know. > > - "NIFI-1824 causes failures on Windows" NIFI-2089[1] [status] BLOCKER, Mark > Payne is looking into the exact cause. > > - "TestProcessorLifecyle fails on Windows" NIFI-2092 [status] I am working on > a PR with the fix. > > - "RemoteProcessGroupStatusTest binds to a static Port" NIFI-2097 [status] > Not a blocker as it doesn't prevent a build on all systems (just those that > have something running on port 9990) but I am working on a PR with the fix. > > Once again, NIFI-1974 is listed as "Patch Available" and 0.7.0 in JIRA but a > fix has already been merged into 0.x and work is being done for master. Also > sorry for not sending an update yesterday, I was waiting for a good point to > give an update but things kept being one step away from finished. > > [1] https://issues.apache.org/jira/browse/NIFI-2089 > [2] https://issues.apache.org/jira/browse/NIFI-2092 > [3] https://issues.apache.org/jira/browse/NIFI-2097 > > Joe > - - - - - - > Joseph Percivall > linkedin.com/in/Percivall > e: [email protected] > > > > > On Monday, June 20, 2016 11:44 AM, Bryan Bende <[email protected]> wrote: > I believe NIFI-1895 should be ready to go for 0.7.0 as well... > > https://github.com/apache/nifi/pull/542 > > > On Mon, Jun 20, 2016 at 11:39 AM, Joe Percivall < > [email protected]> wrote: > >> Team, >> >> We are doing a great job finishing up tickets. Six more were closed over >> the weekend and most of the others made progress as well. We only have >> three more that are tagged as 0.7.0 in Jira. There are a couple others >> which are unversioned that are close but haven't been identified as >> important enough to hold up the release for so I will not reflect them here. >> >> The current status for those left tagged as 0.7.0: >> >> - "Processors could be started before the Controller Services that they >> depend on" NIFI-2032[1] [status] Oleg Zhurakousky's PR was looked at by >> Andy LoPresto but not clear if more action is needed. >> >> - "Create a processor to extract WAV file characteristics" NIFI-615[2] >> [status] Waiting for Joe Skora to rebase and put changes into a PR (which >> he said he would do today) and for final review from Joe Percivall (me) >> once the changes are made. >> >> - "Create PutTCP Processor" NIFI-1834[3] [status] I took Matt Brown's >> original commit and applied my comments in another commit. Bryan Bende >> reviewed and I am addressing now. >> >> Also NIFI-1974 and NIFI-1850 are marked as 0.7.0 and "Patch Available" in >> Jira but they are already merged into 0.x and work is being done to get it >> into master. I will not reflect them here. >> >> [1] https://issues.apache.org/jira/browse/NIFI-2032 >> [2] https://issues.apache.org/jira/browse/NIFI-615 >> >> [3] https://issues.apache.org/jira/browse/NIFI-1834 >> >> >> Joe >> - - - - - - >> Joseph Percivalllinkedin.com/in/Percivall >> e: [email protected] >> >> >> >> On Friday, June 17, 2016 2:23 PM, Oleg Zhurakousky < >> [email protected]> wrote: >> >> >> >> 2009 is all done (including 0.x) >> >> Sent from my iPhone >> >> >> > On Jun 17, 2016, at 14:16, Joe Percivall <[email protected]> >> wrote: >> > >> > Team, >> > >> > We are continuing to have good progress towards the 0.7.0 release. >> Tagged as "0.7.0" in Jira and still pending, we currently have 9 tickets >> that are all patch available. >> > >> > As a note, there seem to be a number of unversioned "patch available" >> tickets in Jira. I am going to take a look at them to see if any can easily >> make it into 0.7.0 (or are critical) but unless if they are critical I am >> not going to hold up the release for them. >> > >> > The current status for those tagged as 0.7.0: >> > >> > - "Processors could be started before the Controller Services that they >> depend on" NIFI-2032[1] [status] Critical bug that was added two days ago. >> Oleg Zhurakousky posted a PR and needs review. >> > >> > >> > - "Allow user to specify file filter regex when unpacking zip/tar >> archives" NIFI-1568[2] [status] Matt Burgess finished reviewing and is >> waiting for Ricky Saltzer to address the final comment. >> > >> > - "Create PutSlack processor" NIFI-1578 [3] [status] Matt Burgess found >> one final issue before it is committed. Waiting for Adam Lamar to address. >> > >> > - "Allow empty Content-Type in InvokeHTTP processor" NIFI-1620[4] >> [status] Pierre Villard addressed Adam Taft's comments is waiting for a >> final review. >> > >> > - "Support Custom Properties in Expression Language" NIFI-1974[5] >> [status] No Change, waiting for Mark Payne to give a final review. >> > >> > - "StandardProcessNode and AbstractConfiguredComponent duplicate >> instance variable "annotationData"" NIFI-2009[6] [status] Was merged into >> master but needs to fix merge conflicts to be merged into 0.x >> > - "Create a processor to extract WAV file characteristics" NIFI-615[7] >> [status] Joe Skora posted a new branch addressing the comments but needs to >> rebase and update PR. Branch needs final review from Joe Percivall (me) >> > >> > - "Add SNMP processors" NIFI-1537[8] [status] PR is rebased and Oleg >> Zhurakousky will be reviewing >> > >> > - "Create FlowDebugger processor" NIFI-1829[9] [status] Joe Skora added >> another commit and rebased. Tony won't be able to finalize review until the >> weekend, Michael Moser volunteered to finish >> > >> > >> > Also NiFi-1850 is marked as 0.7.0 and "Patch Available" in Jira but it >> was already was merged into 0.x and work is being done to get it into >> master. I will not reflect it here. >> > >> > [1] https://issues.apache.org/jira/browse/NIFI-2032 >> > [2] https://issues.apache.org/jira/browse/NIFI-1568 >> > [3] https://issues.apache.org/jira/browse/NIFI-1578 >> > [4] https://issues.apache.org/jira/browse/NIFI-1620 >> > [5] https://issues.apache.org/jira/browse/NIFI-1974 >> > [6] https://issues.apache.org/jira/browse/NIFI-2009 >> > [7] https://issues.apache.org/jira/browse/NIFI-615 >> > [8] https://issues.apache.org/jira/browse/NIFI-1537 >> > [9] https://issues.apache.org/jira/browse/NIFI-1829 >> > >> > Joe >> > - - - - - - >> > Joseph Percivalllinkedin.com/in/Percivall >> > e: [email protected] >> > >> > >> > >> > >> > On Wednesday, June 15, 2016 10:56 AM, Joe Percivall >> <[email protected]> wrote: >> > Team, >> > >> > There was a lot of great progress yesterday, we closed or pushed 6 >> tickets. Also two tickets were added that are either critical or finishing >> shortly. The status of the remaining 12 tickets are below: >> > >> > - "Corrupted flow file leads to a wedged flow" NIFI-2015[1] Added >> yesterday. Christopher McDermott, Mark Payne and Oleg Zhurakousky have been >> discussing the bug but no resolution yet. >> > >> > - "Allow user to specify file filter regex when unpacking zip/tar >> archives" NIFI-1568[2] [status] Matt Burgess is continuing to review >> > >> > - "Create PutSlack processor" NIFI-1578 [3] [status] Actively being >> worked on by contributor and reviewers >> > >> > - "Allow empty Content-Type in InvokeHTTP processor" NIFI-1620[4] >> [status] No change since yesterday, still waiting for final review by Adam >> Taft. Commented asking if Adam would like me to finish the review >> > >> > - "If unable to write to Content Repository, Process Session should >> automatically roll itself back" NIFI-1644[5] [status] No progress, >> commented asking Mark Payne (reporter) to see if it can slide. >> > >> > - "Misconfigured MonitorMemory ReportingTask can not be stopped" >> NIFI-1690[6] [status] Actively being worked on by contributor and reviewer >> > >> > - "Support Custom Properties in Expression Language" NIFI-1974[7] >> [status] New yesterday. Yolanda Davis submitted the PR and review by Mark >> Payne. Both are actively working on it. >> > >> > - "StandardProcessNode and AbstractConfiguredComponent duplicate >> instance variable "annotationData"" NIFI-2009[8] [status] +1 from >> committer, just waiting to be merged >> > >> > - "Create a processor to extract WAV file characteristics" NIFI-615[9] >> [status] No change since yesterday, I will review. Needs rebase though >> > >> > - "Add SNMP processors" NIFI-1537[10] [status] No significant change >> since yesterday, Oleg Zhurakousky is waiting for Pierre Villard to rebase. >> > >> > - "Add option to bulk using Index or Update to PutElasticsearch" >> NIFI-1594[11] [status] João Henrique Ferreira de Freitas addressed Matt >> Burgess' comments and is waiting for final review by Matt >> > >> > - "Create FlowDebugger processor" NIFI-1829[12] [status] Joe Skora added >> another commit and rebased. Tony won't be able to finalize review until the >> weekend, Michael Moser volunteered to finish >> > >> > [1] https://issues.apache.org/jira/browse/NIFI-2015 >> > [2] https://issues.apache.org/jira/browse/NIFI-1568 >> > [3] https://issues.apache.org/jira/browse/NIFI-1578 >> > [4] https://issues.apache.org/jira/browse/NIFI-1620 >> > [5] https://issues.apache.org/jira/browse/NIFI-1644 >> > [6] https://issues.apache.org/jira/browse/NIFI-1690 >> > [7] https://issues.apache.org/jira/browse/NIFI-1974 >> > [8] https://issues.apache.org/jira/browse/NIFI-2009 >> > [9] https://issues.apache.org/jira/browse/NIFI-615 >> > [10] https://issues.apache.org/jira/browse/NIFI-1537 >> > [11] https://issues.apache.org/jira/browse/NIFI-1594 >> > [12] https://issues.apache.org/jira/browse/NIFI-1829 >> > - - - - - - >> > Joseph Percivall >> > linkedin.com/in/Percivall >> > e: [email protected] >> > >> > >> > >> > >> > >> > On Tuesday, June 14, 2016 7:11 PM, Andre <[email protected]> wrote: >> > Tony, >> > >> > I second Joe's comments as well. >> > >> > Since the early discussions about the branching model I have been under >> the >> > total impression that once 1.0 is released, 0.x would become support only >> > and updates restricted to critical issues (security & data-loss >> > break-fixes). >> > >> > This is not to say that a NPE or a 100% CPU issue shouldn't be >> backported, >> > but I would imagine the effort to port to 0.x should be driven by the >> > contributor rather than the merger (as it is being done atm). >> > >> > >> >> On Wed, Jun 15, 2016 at 8:13 AM, Joe Witt <[email protected]> wrote: >> >> >> >> According to the discussion we had about the management of the release >> >> lines there would only be incremental releases when something was >> critical >> >> enough (security or data loss). And, if someone really wanted needed a >> >> minor release they could initiate and do that as well. But as far as >> >> continued feature development and focus it would shift to 1.0. >> >> >> >> So emphasis moves to new major line but those staying on the old major >> can >> >> still have options as well. >> >> On Jun 14, 2016 5:31 PM, "Tony Kurc" <[email protected]> wrote: >> >> >> >> Joe, for some reason, my mental image was that I expected we'd keep >> >> releasing new 0.x minor releases for a while along with 1.x. >> >> >> >> Is that everyone else's expectations? >> > >>
