Andy,
Thanks for the extra eyes on the Slack PR, I will look at the client auth piece 
but may have some questions as I'm still hoping to "see the Matrix" on all that 
security stuff :)

About to take the red pill,
Matt

P.S. To echo Andy's thoughts, thanks to Joe for organizing the release! 

> On Jun 13, 2016, at 9:36 PM, Andy LoPresto <alopre...@apache.org> wrote:
> 
> Thanks for organizing this, Joe. I replied to Joe Witt’s question on 1795 and 
> removed it from 0.7.0, but Jira was down earlier so it didn’t stick. All good 
> now. 
> 
> I’ll also throw eyes on the PutSlack PR and look forward to someone reviewing 
> the client auth piece. It’s small, and will be superseded by NIFI-1990, which 
> standardizes the certificate behavior for clustering and site-to-site (over 
> socket and HTTPS). 
> 
> Andy LoPresto
> alopre...@apache.org
> alopresto.apa...@gmail.com
> PGP Fingerprint: 70EC B3E5 98A6 5A3F D3C4  BACE 3C6E F65B 2F7D EF69
> 
>> On Jun 13, 2016, at 3:26 PM, Matt Burgess <mattyb...@gmail.com> wrote:
>> 
>> I'll take the PutSlack PR and Ricky's unpack PR, and if there's an update on 
>> the Elasticsearch PR I'll take that too. As always though, the more eyes the 
>> better :)
>> 
>> Thanks,
>> Matt
>> 
>> 
>>> On Jun 13, 2016, at 5:52 PM, Joe Percivall <joeperciv...@yahoo.com.INVALID> 
>>> wrote:
>>> 
>>> Team,
>>> 
>>> Things are closing in well but we need to get pretty specific on these to 
>>> keep the release moving roughly along the lines of the schedule we've 
>>> discussed previously.  Those of you who have tickets on here that can be 
>>> moved to 1.0.0 please do so.  Otherwise, let's please keep 
>>> discussion/status information up so we can all see how we're trending 
>>> toward release candidate readiness.
>>> 
>>> Below, I've explicitly outlined each person that is involved in each ticket 
>>> so if you are on the hook for a ticket please help to get it closed out. 
>>> There are a couple which have patches or PRs with no comments and need 
>>> review, if able please help out the release by reviewing them.
>>> 
>>> The current items on the release based on JIRA fix version that remain are:
>>> 
>>> - "Cluster communication requires client certificates even if 
>>> needClientAuth set to false" NIFI-1981[1] [status] PR created by Andy 
>>> LoPresto.  NEEDS REVIEW.
>>> 
>>> - "Mock Framework allows processor to route to Relationships that the 
>>> Processor does not support" NIFI-1152[2]
>>> [status] Patch created by Puspendu Banerjee addressing Mark Payne's 
>>> comments. Needs another round of review
>>> 
>>> - "Allow user to specify file filter regex when unpacking zip/tar archives" 
>>> NIFI-1586[3] [status] Ricky Saltzer created a PR that addressed a couple 
>>> comments and is rebased (request by Matt Burgess). Awaiting full review.
>>> 
>>> - "Create PutSlack processor" NIFI-1578 [4] [status] Adam Lamar pushed a 
>>> new commit addressing comments. Awaiting review from Matt Burgess or Andy 
>>> LoPresto. 
>>> 
>>> -  "Allow empty Content-Type in InvokeHTTP processor" NIFI-1620[5] [status] 
>>> Pierre Villard addressed Adam Taft's comments on the PR and is awaiting a 
>>> final review.
>>> 
>>> 
>>> - "If unable to write to Content Repository, Process Session should 
>>> automatically roll itself back" NIFI-1644[6] [status] No progress, 
>>> commented asking Mark Payne (reporter) to see if it can slide.
>>> 
>>> - "Misconfigured MonitorMemory ReportingTask can not be stopped" 
>>> NIFI-1690[7] [status] Oleg Zhurakousky created a PR and is awaiting review.
>>> 
>>> - "StandardProcessNode and AbstractConfiguredComponent duplicate instance 
>>> variable "annotationData"" NIFI-2009[8] [status] No progress, commented 
>>> asking Oleg Zhurakousky (assignee) to see if it can slide.
>>> 
>>> - "Create a processor to extract WAV file characteristics" NIFI-615[9] 
>>> [status] PR submitted by Joe Skora, last comment addresses Joe Witt's 
>>> concern's and is awaiting a full review.
>>> 
>>> - "Add SNMP processors" NIFI-1537[10] [status] Pierre Villard created a PR 
>>> which addressed various comments, awaiting review from Oleg Zhurakousky.
>>> 
>>> - "Add option to bulk using Index or Update to PutElasticsearch" 
>>> NIFI-1594[11] [status] João Henrique Ferreira de Freitas created a PR but 
>>> needs to address Matt Burgess' comments.
>>> 
>>> - "Improve documentation regarding PropertyDescriptor name & displayName" 
>>> NIFI-1795[12] [status] No progress, awaiting word from Andy LoPresto if it 
>>> can slide
>>> 
>>> - "Create FlowDebugger processor" NIFI-1829[13] [status] Joe Skora created 
>>> a PR and addressed review comments by Tony Kurc. Awaiting final review by 
>>> Tony.
>>> 
>>> - "SplitJson enhancements for flowfile names and additional options" 
>>> NIFI-1933[14] [status] Patch submitted by Alex Halldin. NEEDS REVIEW.
>>> 
>>> - "InferAvroSchema dynamically set record name" NIFI-1934[15] [status] 
>>> Patch submitted by Alex Halldin. NEEDS REVIEW.
>>> 
>>> - "Added ConvertDynamicJsonToAvro processor" NIFI-1935[16] [status] Patch 
>>> submitted by Alex Halldin. Currently being commented on by Bryan Bende and 
>>> Joe Witt on master vs 0.x branch but needs a full review.
>>> 
>>> 
>>> [1] https://issues.apache.org/jira/browse/NIFI-1981
>>> [2] https://issues.apache.org/jira/browse/NIFI-1152
>>> [3] https://issues.apache.org/jira/browse/NIFI-1568
>>> [4] https://issues.apache.org/jira/browse/NIFI-1578
>>> [5] https://issues.apache.org/jira/browse/NIFI-1620
>>> [6] https://issues.apache.org/jira/browse/NIFI-1644
>>> [7] https://issues.apache.org/jira/browse/NIFI-1690
>>> [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-1795
>>> [13] https://issues.apache.org/jira/browse/NIFI-1829
>>> [14] https://issues.apache.org/jira/browse/NIFI-1933
>>> [15] https://issues.apache.org/jira/browse/NIFI-1934
>>> [16] https://issues.apache.org/jira/browse/NIFI-1935
>>> 
>>> - - - - - - 
>>> Joseph Percivall
>>> linkedin.com/in/Percivall
>>> e: joeperciv...@yahoo.com
> 

Reply via email to