Tony,

I believe based on progress with JIRAs today and discussions had that
NiFi 0.5.0 is ready for another RC.

Thanks
Joe

On Sat, Feb 6, 2016 at 11:00 AM, Joe Witt <[email protected]> wrote:
> Hello
>
> Would like some input/advice on
> https://issues.apache.org/jira/browse/NIFI-1484.  In my initial
> testing of this I would consider it worthy of getting resolved right
> away.  But perhaps I'm overthinking it.  Related, but far less urgent,
> is https://issues.apache.org/jira/browse/NIFI-1483.  That one is
> simply an irritation but could cause pause for every user that sees
> it.
>
> Thanks
> Joe
>
> On Sat, Feb 6, 2016 at 3:41 AM, Tony Kurc <[email protected]> wrote:
>> Awesome! I will start working on the rc
>> On Feb 6, 2016 12:34 AM, "Aldrin Piri" <[email protected]> wrote:
>>
>>> All,
>>>
>>> Just wanted to follow up that the members of the community had completed
>>> their testing against NIFI-259 and I performed the merge of that branch
>>> into master.
>>>
>>> In that time, there were a few other issues that had some added bits of
>>> functionality and improvements which were also folded in and incorporated
>>> into the codebase.
>>>
>>> At this time, all issues exclusive of the actual release process for 0.5.0
>>> have been incorporated and resolved.  Congrats on all the effort to tie
>>> these items up on both the contrib and review efforts.  Looking forward to
>>> the community's involvement of the upcoming RC during our release
>>> evaluation and voting process.
>>>
>>> Thanks!
>>> --aldrin
>>>
>>> On Thu, Feb 4, 2016 at 10:33 PM, Aldrin Piri <[email protected]> wrote:
>>>
>>> > All,
>>> >
>>> > Just as an update on some of the remaining items.  I have been doing some
>>> > review work to help close out some of these final issues.  Finished
>>> review
>>> > and merged 1257 and 1259 which brings a lot of great security and
>>> > encryption functions that will help a long way for providing a nice
>>> > foundation for additional support across the entirety of the project.
>>> >
>>> > Along with several of the members of the community, I have been reviewing
>>> > and providing feedback 259 along with several other members of the
>>> > community and its incorporated tickets of 1223, 1379.  We are doing some
>>> > final testing particularly surrounding its interactions and utilization
>>> of
>>> > Kerberos.  Once that wraps up, we will be able to merge that in, closing
>>> > the last of the items scheduled for this release.
>>> >
>>> > Thanks!
>>> > Aldrin
>>> >
>>> > On Thu, Feb 4, 2016 at 9:53 AM, Joe Witt <[email protected]> wrote:
>>> >
>>> >> Tony
>>> >>
>>> >> Agreed.  I will work through these as well and try to ensure the
>>> >> wording accurately reflect what happened.  The release notes are a
>>> >> really important piece of communication we need to get right.
>>> >>
>>> >> Thanks
>>> >> Joe
>>> >>
>>> >> On Thu, Feb 4, 2016 at 6:04 AM, Tony Kurc <[email protected]> wrote:
>>> >> > I am prepping for the release, going through the jiras that have been
>>> >> > closed, I think several have a description that does not match. Good
>>> >> > example is:
>>> >> >
>>> >> > https://issues.apache.org/jira/browse/NIFI-1325
>>> >> >
>>> >> > I believe the final scope of the patch surpassed the original
>>> >> description.
>>> >> > Should this be adjusted for people perusing the JIRA report we link to
>>> >> in
>>> >> > our release notes? I'd say yes. I made a couple small edits to some
>>> >> tickets
>>> >> > already for increased readability. One change I wanted to make was
>>> >> change
>>> >> > NIFI-259 to "New Feature" rather than subtask, but I was concerned
>>> about
>>> >> > this disrupting folks.
>>> >> >
>>> >> > I think a quick consistency and spell check would be good - I've had
>>> >> > several people mention out of band that prior release notes had a
>>> couple
>>> >> > errors. Apparently people love the release notes page on the JIRA
>>> >> > NIFI-1107 is done, just needs a merge, which I'll do tonight.
>>> >> >
>>> >> > On Wed, Feb 3, 2016 at 4:32 PM, Joe Witt <[email protected]> wrote:
>>> >> >
>>> >> >> Latest update for all
>>> >> >>
>>> >> >> You can see the current status here [1].
>>> >> >>
>>> >> >> Looks like several tickets but really it is three efforts:
>>> >> >> 1) Improve encryption options in EncryptContent NIFI-1257,1259
>>> >> >> 2) Provide state management as a framework function
>>> NIFI-259,1223,1339
>>> >> >> 3) Support multi-part S3 uploads NIFI-1107
>>> >> >>
>>> >> >> Based on comments on each they are just in very late stage/detailed
>>> >> >> review.  So we're close.
>>> >> >>
>>> >> >> Thanks
>>> >> >> Joe
>>> >> >>
>>> >> >> [1]
>>> >> >>
>>> >>
>>> https://issues.apache.org/jira/browse/NIFI-1339?jql=project%20%3D%20NIFI%20AND%20fixVersion%20%3D%200.5.0%20AND%20resolution%20%3D%20Unresolved%20ORDER%20BY%20due%20ASC%2C%20priority%20DESC%2C%20created%20ASC
>>> >> >>
>>> >> >> On Thu, Jan 21, 2016 at 12:55 AM, Joe Witt <[email protected]>
>>> wrote:
>>> >> >> > Team
>>> >> >> >
>>> >> >> > Did a full round of 050 JIRA cleanup this evening.  Great progress
>>> is
>>> >> >> > being made.
>>> >> >> >
>>> >> >> > For the proposed NiFi 050 release schedule above we have about 10
>>> >> days
>>> >> >> > of code time left.  There is a pretty large backlog of patch
>>> awaiting
>>> >> >> > items currently showing as aligned to 050.  See here [1].
>>> >> >> >
>>> >> >> > Also there are 25 (as of this writing) open tickets.  See here [2].
>>> >> >> >
>>> >> >> > For the proposed goals of the release as listed previous in this
>>> >> >> > thread it appears the following are likely to occur in 050:
>>> >> >> >   Improved encryption handling: NIFI-1324,1314,1259,
>>> >> >> >   Improved Hive/Kite interaction: NIFI-1193
>>> >> >> >   Interactive Queue Management: NIFI-108
>>> >> >> >   Support for numerous scripting/languages: NIFI-210
>>> >> >> >   Support for state management: NIFI-259
>>> >> >> >
>>> >> >> > The following are at risk or moving out:
>>> >> >> >   NiFi kerberos support: NIFI-1274
>>> >> >> >     No progress on it yet.  Good 060 target.
>>> >> >> >   UX/UI improvements: NIFI-951
>>> >> >> >     These changes appear to be better fit for 1.0.0.
>>> >> >> >
>>> >> >> > [1]
>>> >> >>
>>> >>
>>> https://issues.apache.org/jira/browse/NIFI-1416?jql=project%20%3D%20NIFI%20AND%20status%20%3D%20%22Patch%20Available%22%20AND%20fixVersion%20%3D%200.5.0
>>> >> >> >
>>> >> >> > [2]
>>> >> >>
>>> >>
>>> https://issues.apache.org/jira/browse/NIFI-1404?jql=project%20%3D%20NIFI%20AND%20status%20in%20(Open%2C%20%22In%20Progress%22%2C%20Reopened)%20AND%20fixVersion%20%3D%200.5.0
>>> >> >> >
>>> >> >> > Thanks
>>> >> >> > Joe
>>> >> >> >
>>> >> >> > On Tue, Dec 29, 2015 at 10:08 PM, Joe Witt <[email protected]>
>>> >> wrote:
>>> >> >> >> Thanks Tony - let's plan on that then.
>>> >> >> >>
>>> >> >> >> On Tue, Dec 29, 2015 at 9:58 PM, Oleg Zhurakousky
>>> >> >> >> <[email protected]> wrote:
>>> >> >> >>> Be careful what you wish for ;)
>>> >> >> >>>
>>> >> >> >>> Sent from my iPhone
>>> >> >> >>>
>>> >> >> >>>> On Dec 29, 2015, at 17:44, Tony Kurc <[email protected]> wrote:
>>> >> >> >>>>
>>> >> >> >>>> Joe,
>>> >> >> >>>> I might like to give the release a try.
>>> >> >> >>>>
>>> >> >> >>>> Tony
>>> >> >> >>>>
>>> >> >> >>>>> On Mon, Dec 28, 2015 at 4:30 PM, Joe Witt <[email protected]>
>>> >> >> wrote:
>>> >> >> >>>>>
>>> >> >> >>>>> Team,
>>> >> >> >>>>>
>>> >> >> >>>>> In the spirit of shooting for roughly 6 week release cycles and
>>> >> the
>>> >> >> >>>>> releasing timing of NiFi 0.4.0/0.4.1 I suggest we shoot for Feb
>>> >> 5th,
>>> >> >> >>>>> 2016 as our release vote start date target.  This should mean
>>> >> we're
>>> >> >> >>>>> not altering code past say 1 Feb, 2016 other than for findings
>>> >> that
>>> >> >> >>>>> crop up with the testing/RC.
>>> >> >> >>>>>
>>> >> >> >>>>> The JIRA entries for Apache NiFi 0.5.0 can be quickly found
>>> here
>>> >> >> >>>>>
>>> >> >> >>>>>
>>> >> >>
>>> >>
>>> https://issues.apache.org/jira/browse/NIFI-1333?jql=fixVersion%20%3D%200.5.0%20AND%20project%20%3D%20NIFI
>>> >> >> >>>>>
>>> >> >> >>>>> There are some really great features/fixes there already
>>> >> including
>>> >> >> but
>>> >> >> >>>>> not limited to:
>>> >> >> >>>>>  NiFi kerberos support: NIFI-1274
>>> >> >> >>>>>  Improved encryption handling: NIFI-1324,1314,1259,
>>> >> >> >>>>>  Improved Hive/Kite interaction: NIFI-1193
>>> >> >> >>>>>  UX/UI improvements: NIFI-951
>>> >> >> >>>>>  Interactive Queue Management: NIFI-108
>>> >> >> >>>>>  Support for numerous scripting/languages: NIFI-210
>>> >> >> >>>>>  Support for state management: NIFI-259
>>> >> >> >>>>>
>>> >> >> >>>>> If anyone on the pmc is interested to do the RC work for the
>>> >> release
>>> >> >> >>>>> just holler.  If not I'm happy to do it.
>>> >> >> >>>>>
>>> >> >> >>>>> Thanks
>>> >> >> >>>>> Joe
>>> >> >> >>>>>
>>> >> >>
>>> >>
>>> >
>>> >
>>>

Reply via email to