I hope to have a patch for NIFI-1542 this afternoon, unless I run into problems.
On Sun, Feb 21, 2016 at 2:17 PM, Joe Witt <[email protected]> wrote: > Tony, > > Just chatted with Oleg. Sounds like he has a potential solution for > NIFI-1536. I did some testing for NIFI-1527 that I've reopened so we > can validate what was observed. NIFI-1542 is open. > > NIFI-1536 and NIFI-1542 could be moved off of 0.5.1 but NIFI-1527 should > not be. > > So looks like we're not quite ready yet. > > Thanks > Joe > > On Fri, Feb 19, 2016 at 5:05 PM, Tony Kurc <[email protected]> wrote: > > sunday works for me. > > > > On Fri, Feb 19, 2016 at 4:18 PM, Joe Witt <[email protected]> wrote: > > > >> Ok so looks like the major players for the 0.5.1 release are in. > >> Today during some testing it was discovered that there can be issues > >> with multiple HDFS processors with differing configurations and > >> yesterday on StackOverflow it was reported that there are some issues > >> talking to Kafka but there is a viable workaround for now. I > >> personally feel like what we have for an 0.5.1 is good right now > >> without those two JIRAs and that we could do an 0.5.2 if those get > >> sorted soon or they can go in 0.6.0 which if we stick to the > >> previously discussed idea would be mid-March. > >> > >> What do ya'll think? > >> > >> If we did a kick-off of RC say late Sunday (assuming RM is on board > >> too of course) we'd be looking at a midweek release for 0.5.1 > >> > >> Thanks > >> Joe > >> > >> On Wed, Feb 17, 2016 at 9:13 PM, Joe Witt <[email protected]> wrote: > >> > +1 > >> > > >> > On Wed, Feb 17, 2016 at 10:12 PM, Tony Kurc <[email protected]> wrote: > >> >> All, > >> >> Just so we're clear, my expectations is that the fixes we need above > >> will > >> >> go into master (0.6.0-SNAPSHOT). I (or the contributor) will attempt > to > >> >> also apply those fixes to a branch I made off of nifi-0.5.0, called > >> >> "support/nifi-0.5.x", and when done we can test and when satisfied, > >> start > >> >> the 0.5.1 release process. > >> >> > >> >> > >> >> On Wed, Feb 17, 2016 at 8:28 PM, Tony Kurc <[email protected]> wrote: > >> >> > >> >>> I lieu of a decision on a git branching strategy, does anyone object > >> to me > >> >>> naming a branch "support/0.5.x" so I can start pulling together > 0.5.1? > >> >>> > >> >>> On Wed, Feb 17, 2016 at 8:17 PM, Joe Witt <[email protected]> > wrote: > >> >>> > >> >>>> Team, > >> >>>> > >> >>>> First, congrats on getting 0.5.0 out the door. Very nice release > with > >> >>>> excellent new features, enhancements, and bug fixes with > involvement > >> >>>> of many new contributors. > >> >>>> > >> >>>> The effort toward 0.6.0 is well underway and if we are shooting for > >> >>>> our original target would still arrive around mid march-ish. Seems > >> >>>> reasonable given progress so far. > >> >>>> > >> >>>> That said, I'd like to propose we go ahead and put out an 0.5.1 as > >> >>>> soon as the patches are addressed. The finding that Lars helped > >> >>>> expose and that Mark Payne is now working [1] in my view warrants > a > >> >>>> release by itself as it is data loss related. Also, we can address > >> >>>> the work Matt Gilman is doing to ensure properly authorized users > can > >> >>>> access resources they're being blocked by [2] and the > license/notice > >> >>>> findings Sean discovered during the last release [3]. There are a > >> >>>> couple odd/ends in the list as well [4]. Purely a bug fix release > as > >> >>>> spec'd out in release notes [5]. > >> >>>> > >> >>>> I checked with Tony and he is happy to continue performing RM > tasks on > >> >>>> the 0.5.x line. > >> >>>> > >> >>>> [1] https://issues.apache.org/jira/browse/NIFI-1527 > >> >>>> [2] https://issues.apache.org/jira/browse/NIFI-1497 > >> >>>> [3] https://issues.apache.org/jira/browse/NIFI-1520 > >> >>>> [4] https://s.apache.org/nifi-0.5.1-candidate > >> >>>> [5] https://cwiki.apache.org/confluence/display/NIFI/Release+Notes > >> >>>> > >> >>>> Thanks > >> >>>> Joe > >> >>>> > >> >>> > >> >>> > >> >
