Re: [DISCUSS] NiFi 0.5.1 release

2016-02-22 Thread Tony Kurc 
Yes, now working off 2a459fe21c708c8316dd255c3dc7f8254e7940f1

On Mon, Feb 22, 2016 at 9:48 PM, Joe Witt  wrote:

> Tony,
>
> Went through all commits on the support/nifi-0.5.x branch and all
> JIRAs on 0.5.1.  It appears all are good except [1] and [2].  These
> did get applied to master but not to the support branch.
>
> Can you please apply them?
>
> [1] https://issues.apache.org/jira/browse/NIFI-1514
> [2] https://issues.apache.org/jira/browse/NIFI-1282
>
> Thanks
> Joe
>
> On Mon, Feb 22, 2016 at 9:18 PM, Joe Witt  wrote:
> > Confirmed that is the expected commit.  I'll check each commit id
> > against all JIRAs for 0.5.1 now too.
> >
> > Thanks Tony!
> >
> > On Mon, Feb 22, 2016 at 9:16 PM, Tony Kurc  wrote:
> >> Starting rc1 build off of 280714942097b0703a1f8f92913d95159cd89bfa
> >>
> >> On Mon, Feb 22, 2016 at 9:12 PM, Matt Gilman 
> >> wrote:
> >>
> >>> Patch has been incorporated into master and support/nifi-0.5.x. Thanks.
> >>>
> >>> On Mon, Feb 22, 2016 at 7:34 PM, Joe Witt  wrote:
> >>>
> >>> > Would like to get james wing patch incorporated.  Will ping asap.
> >>> >
> >>> > Thanks
> >>> > Joe
> >>> > On Feb 22, 2016 7:22 PM, "Tony Kurc"  wrote:
> >>> >
> >>> > > All, I've started building nifi-0.5.1-RC1 from commit
> >>> > > f56e1551ebc20495d9bf7cf70814c0e4afba768a. Halt me ASAP if you
> believe
> >>> > this
> >>> > > is erroneous
> >>> > >
> >>> > > On Mon, Feb 22, 2016 at 6:41 PM, Tony Kurc 
> wrote:
> >>> > >
> >>> > > > Yes.
> >>> > > > On Feb 22, 2016 5:31 PM, "Joe Witt"  wrote:
> >>> > > >
> >>> > > >> Tony,
> >>> > > >>
> >>> > > >> I believe 0.5.1 is ready to roll with the exception of
> NIFI-1542 and
> >>> > > >> NIFI-1545 needing to be merged in.  They appear ready to roll.
> Can
> >>> > > >> you do that as part of kicking off the RC?
> >>> > > >>
> >>> > > >> Thanks
> >>> > > >> Joe
> >>> > > >>
> >>> > > >> On Sun, Feb 21, 2016 at 2:57 PM, Oleg Zhurakousky
> >>> > > >>  wrote:
> >>> > > >> > 1536 will be in shortly
> >>> > > >> >
> >>> > > >> > Sent from my iPhone
> >>> > > >> >
> >>> > > >> >> On Feb 21, 2016, at 14:17, Joe Witt 
> 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 <
> trk...@gmail.com>
> >>> > > wrote:
> >>> > > >> >>> sunday works for me.
> >>> > > >> >>>
> >>> > > >>  On Fri, Feb 19, 2016 at 4:18 PM, Joe Witt <
> joe.w...@gmail.com>
> >>> > > >> 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 <
> joe.w...@gmail.com
> >>> >
> >>> > > >> wrote:
> >>> > > >> > +1
> >>> > > >> >
> >>> > > >> >> On Wed, Feb 17, 2016 at 10:12 PM, Tony Kurc <
> >>> trk...@gmail.com>
> >>> > > >> 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

Re: [DISCUSS] NiFi 0.5.1 release

2016-02-22 Thread Joe Witt 
Tony,

Went through all commits on the support/nifi-0.5.x branch and all
JIRAs on 0.5.1.  It appears all are good except [1] and [2].  These
did get applied to master but not to the support branch.

Can you please apply them?

[1] https://issues.apache.org/jira/browse/NIFI-1514
[2] https://issues.apache.org/jira/browse/NIFI-1282

Thanks
Joe

On Mon, Feb 22, 2016 at 9:18 PM, Joe Witt  wrote:
> Confirmed that is the expected commit.  I'll check each commit id
> against all JIRAs for 0.5.1 now too.
>
> Thanks Tony!
>
> On Mon, Feb 22, 2016 at 9:16 PM, Tony Kurc  wrote:
>> Starting rc1 build off of 280714942097b0703a1f8f92913d95159cd89bfa
>>
>> On Mon, Feb 22, 2016 at 9:12 PM, Matt Gilman 
>> wrote:
>>
>>> Patch has been incorporated into master and support/nifi-0.5.x. Thanks.
>>>
>>> On Mon, Feb 22, 2016 at 7:34 PM, Joe Witt  wrote:
>>>
>>> > Would like to get james wing patch incorporated.  Will ping asap.
>>> >
>>> > Thanks
>>> > Joe
>>> > On Feb 22, 2016 7:22 PM, "Tony Kurc"  wrote:
>>> >
>>> > > All, I've started building nifi-0.5.1-RC1 from commit
>>> > > f56e1551ebc20495d9bf7cf70814c0e4afba768a. Halt me ASAP if you believe
>>> > this
>>> > > is erroneous
>>> > >
>>> > > On Mon, Feb 22, 2016 at 6:41 PM, Tony Kurc  wrote:
>>> > >
>>> > > > Yes.
>>> > > > On Feb 22, 2016 5:31 PM, "Joe Witt"  wrote:
>>> > > >
>>> > > >> Tony,
>>> > > >>
>>> > > >> I believe 0.5.1 is ready to roll with the exception of NIFI-1542 and
>>> > > >> NIFI-1545 needing to be merged in.  They appear ready to roll.  Can
>>> > > >> you do that as part of kicking off the RC?
>>> > > >>
>>> > > >> Thanks
>>> > > >> Joe
>>> > > >>
>>> > > >> On Sun, Feb 21, 2016 at 2:57 PM, Oleg Zhurakousky
>>> > > >>  wrote:
>>> > > >> > 1536 will be in shortly
>>> > > >> >
>>> > > >> > Sent from my iPhone
>>> > > >> >
>>> > > >> >> On Feb 21, 2016, at 14:17, Joe Witt  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 
>>> > > wrote:
>>> > > >> >>> sunday works for me.
>>> > > >> >>>
>>> > > >>  On Fri, Feb 19, 2016 at 4:18 PM, Joe Witt 
>>> > > >> 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 >> >
>>> > > >> wrote:
>>> > > >> > +1
>>> > > >> >
>>> > > >> >> On Wed, Feb 17, 2016 at 10:12 PM, Tony Kurc <
>>> trk...@gmail.com>
>>> > > >> 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 <
>>> trk...@gmail.com>
>>> > > >> 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

Re: [DISCUSS] NiFi 0.5.1 release

2016-02-22 Thread Tony Kurc 
Starting rc1 build off of 280714942097b0703a1f8f92913d95159cd89bfa

On Mon, Feb 22, 2016 at 9:12 PM, Matt Gilman 
wrote:

> Patch has been incorporated into master and support/nifi-0.5.x. Thanks.
>
> On Mon, Feb 22, 2016 at 7:34 PM, Joe Witt  wrote:
>
> > Would like to get james wing patch incorporated.  Will ping asap.
> >
> > Thanks
> > Joe
> > On Feb 22, 2016 7:22 PM, "Tony Kurc"  wrote:
> >
> > > All, I've started building nifi-0.5.1-RC1 from commit
> > > f56e1551ebc20495d9bf7cf70814c0e4afba768a. Halt me ASAP if you believe
> > this
> > > is erroneous
> > >
> > > On Mon, Feb 22, 2016 at 6:41 PM, Tony Kurc  wrote:
> > >
> > > > Yes.
> > > > On Feb 22, 2016 5:31 PM, "Joe Witt"  wrote:
> > > >
> > > >> Tony,
> > > >>
> > > >> I believe 0.5.1 is ready to roll with the exception of NIFI-1542 and
> > > >> NIFI-1545 needing to be merged in.  They appear ready to roll.  Can
> > > >> you do that as part of kicking off the RC?
> > > >>
> > > >> Thanks
> > > >> Joe
> > > >>
> > > >> On Sun, Feb 21, 2016 at 2:57 PM, Oleg Zhurakousky
> > > >>  wrote:
> > > >> > 1536 will be in shortly
> > > >> >
> > > >> > Sent from my iPhone
> > > >> >
> > > >> >> On Feb 21, 2016, at 14:17, Joe Witt  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 
> > > wrote:
> > > >> >>> sunday works for me.
> > > >> >>>
> > > >>  On Fri, Feb 19, 2016 at 4:18 PM, Joe Witt 
> > > >> 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  >
> > > >> wrote:
> > > >> > +1
> > > >> >
> > > >> >> On Wed, Feb 17, 2016 at 10:12 PM, Tony Kurc <
> trk...@gmail.com>
> > > >> 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 <
> trk...@gmail.com>
> > > >> 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 <
> > joe.w...@gmail.com>
> > > >> 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
> > > >>

Re: [DISCUSS] NiFi 0.5.1 release

2016-02-22 Thread Tony Kurc 
All, I've started building nifi-0.5.1-RC1 from commit
f56e1551ebc20495d9bf7cf70814c0e4afba768a. Halt me ASAP if you believe this
is erroneous

On Mon, Feb 22, 2016 at 6:41 PM, Tony Kurc  wrote:

> Yes.
> On Feb 22, 2016 5:31 PM, "Joe Witt"  wrote:
>
>> Tony,
>>
>> I believe 0.5.1 is ready to roll with the exception of NIFI-1542 and
>> NIFI-1545 needing to be merged in.  They appear ready to roll.  Can
>> you do that as part of kicking off the RC?
>>
>> Thanks
>> Joe
>>
>> On Sun, Feb 21, 2016 at 2:57 PM, Oleg Zhurakousky
>>  wrote:
>> > 1536 will be in shortly
>> >
>> > Sent from my iPhone
>> >
>> >> On Feb 21, 2016, at 14:17, Joe Witt  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  wrote:
>> >>> sunday works for me.
>> >>>
>>  On Fri, Feb 19, 2016 at 4:18 PM, Joe Witt 
>> 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 
>> wrote:
>> > +1
>> >
>> >> On Wed, Feb 17, 2016 at 10:12 PM, Tony Kurc 
>> 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 
>> 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 
>> 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
>> >>
>>
>

Re: [DISCUSS] NiFi 0.5.1 release

2016-02-22 Thread Tony Kurc 
Yes.
On Feb 22, 2016 5:31 PM, "Joe Witt"  wrote:

> Tony,
>
> I believe 0.5.1 is ready to roll with the exception of NIFI-1542 and
> NIFI-1545 needing to be merged in.  They appear ready to roll.  Can
> you do that as part of kicking off the RC?
>
> Thanks
> Joe
>
> On Sun, Feb 21, 2016 at 2:57 PM, Oleg Zhurakousky
>  wrote:
> > 1536 will be in shortly
> >
> > Sent from my iPhone
> >
> >> On Feb 21, 2016, at 14:17, Joe Witt  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  wrote:
> >>> sunday works for me.
> >>>
>  On Fri, Feb 19, 2016 at 4:18 PM, Joe Witt  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 
> wrote:
> > +1
> >
> >> On Wed, Feb 17, 2016 at 10:12 PM, Tony Kurc 
> 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 
> 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 
> 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
> >>
>

Re: [DISCUSS] NiFi 0.5.1 release

2016-02-22 Thread Joe Witt 
Tony,

I believe 0.5.1 is ready to roll with the exception of NIFI-1542 and
NIFI-1545 needing to be merged in.  They appear ready to roll.  Can
you do that as part of kicking off the RC?

Thanks
Joe

On Sun, Feb 21, 2016 at 2:57 PM, Oleg Zhurakousky
 wrote:
> 1536 will be in shortly
>
> Sent from my iPhone
>
>> On Feb 21, 2016, at 14:17, Joe Witt  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  wrote:
>>> sunday works for me.
>>>
 On Fri, Feb 19, 2016 at 4:18 PM, Joe Witt  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  wrote:
> +1
>
>> On Wed, Feb 17, 2016 at 10:12 PM, Tony Kurc  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  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  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
>>

Re: [DISCUSS] NiFi 0.5.1 release

2016-02-21 Thread Oleg Zhurakousky 
1536 will be in shortly 

Sent from my iPhone

> On Feb 21, 2016, at 14:17, Joe Witt  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  wrote:
>> sunday works for me.
>> 
>>> On Fri, Feb 19, 2016 at 4:18 PM, Joe Witt  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  wrote:
 +1
 
> On Wed, Feb 17, 2016 at 10:12 PM, Tony Kurc  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  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  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
>

Re: [DISCUSS] NiFi 0.5.1 release

2016-02-21 Thread Joe Skora 
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  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  wrote:
> > sunday works for me.
> >
> > On Fri, Feb 19, 2016 at 4:18 PM, Joe Witt  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  wrote:
> >> > +1
> >> >
> >> > On Wed, Feb 17, 2016 at 10:12 PM, Tony Kurc  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  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 
> 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
> >> 
> >> >>>
> >> >>>
> >>
>

Re: [DISCUSS] NiFi 0.5.1 release

2016-02-21 Thread Joe Witt 
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  wrote:
> sunday works for me.
>
> On Fri, Feb 19, 2016 at 4:18 PM, Joe Witt  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  wrote:
>> > +1
>> >
>> > On Wed, Feb 17, 2016 at 10:12 PM, Tony Kurc  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  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  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
>> 
>> >>>
>> >>>
>>

Re: [DISCUSS] NiFi 0.5.1 release

2016-02-19 Thread Tony Kurc 
sunday works for me.

On Fri, Feb 19, 2016 at 4:18 PM, Joe Witt  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  wrote:
> > +1
> >
> > On Wed, Feb 17, 2016 at 10:12 PM, Tony Kurc  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  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  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
> 
> >>>
> >>>
>

Re: [DISCUSS] NiFi 0.5.1 release

2016-02-19 Thread Oleg Zhurakousky 
So I am working in Kafka and while its a bug it’s not easy to fix with the 
current state of things (see more details here 
https://issues.apache.org/jira/browse/NIFI-1534)
So, there need to be some refactoring within NiFi core to address it right, so 
I’ve just changed the target to be 0.6.0.

For the time being, we know about Kafka issue and we know that it’s not an 
issue unless Run-duration > 0. So until 0.6 we should simply recommend to not 
use Run-duartion with PutKafka.

Cheers
Oleg

On Feb 19, 2016, at 4:18 PM, Joe Witt 
> 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 
> wrote:
+1

On Wed, Feb 17, 2016 at 10:12 PM, Tony Kurc 
> 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 
> 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 
> 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

Re: [DISCUSS] NiFi 0.5.1 release

2016-02-19 Thread Brandon DeVries 
+1 for getting 0.5.1 out the door sooner rather than later.  Like you
said... if the other tickets get sorted out in a week or so, we can do
0.5.2.  Otherwise, 0.6.0 isn't that far off.  But a fix involving data loss
is worth doing quickly.

Brandon

On Fri, Feb 19, 2016 at 4:18 PM Joe Witt  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  wrote:
> > +1
> >
> > On Wed, Feb 17, 2016 at 10:12 PM, Tony Kurc  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  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  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
> 
> >>>
> >>>
>

Re: [DISCUSS] NiFi 0.5.1 release

2016-02-19 Thread Joe Witt 
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  wrote:
> +1
>
> On Wed, Feb 17, 2016 at 10:12 PM, Tony Kurc  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  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  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

>>>
>>>

Re: [DISCUSS] NiFi 0.5.1 release

2016-02-17 Thread Joe Witt 
+1

On Wed, Feb 17, 2016 at 10:12 PM, Tony Kurc  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  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  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
>>>
>>
>>

[DISCUSS] NiFi 0.5.1 release

2016-02-17 Thread Joe Witt 
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