Re: Closing in on a NiFi 1.2.0 release?

Would it be appropriate to add mention of the 2 new site-to-site reporting tasks (status and bulletin) in the release notes? Virus-free. www.avast.com

Re: Closing in on a NiFi 1.2.0 release?

The issues from yesterday have been resolved so I'll start kicking off another attempt at the RC process. On Wed, May 3, 2017 at 6:10 PM, Bryan Bende wrote: > Quick update... I ran into two issues that will need to be addressed to > create the RC. > > I've created JIRAs for them and tagged them

Re: Closing in on a NiFi 1.2.0 release?

Quick update... I ran into two issues that will need to be addressed to create the RC. I've created JIRAs for them and tagged them as 1.2: https://issues.apache.org/jira/browse/NIFI-3795 https://issues.apache.org/jira/browse/NIFI-3793 On Wed, May 3, 2017 at 2:41 PM, Bryan Bende wrote: > Looks

Re: Closing in on a NiFi 1.2.0 release?

Looks like all of the JIRAs have been resolved and we are in a good place. I'll begin kicking off the RC process. On Tue, May 2, 2017 at 5:48 PM, Andre wrote: > All, > > For some reason my canvas did not refresh after a process bounce (which > generally occurs) but reloading page allows for mod

Re: Closing in on a NiFi 1.2.0 release?

All, For some reason my canvas did not refresh after a process bounce (which generally occurs) but reloading page allows for modifications. Cheers On Wed, May 3, 2017 at 7:43 AM, Andre wrote: > folks, > > I was just working to debug the final thorns found reviewing NIFI-3726 and > noticed an o

Re: Closing in on a NiFi 1.2.0 release?

folks, I was just working to debug the final thorns found reviewing NIFI-3726 and noticed an odd behavior and wanted to confirm. If I recall correctly in the past users could simply replace a processor NAR file and even if that NAR existed the flow would continue to work. I just replaced cp ~/n

Re: Closing in on a NiFi 1.2.0 release?

I’ll review & merge as soon as they are available. Andy LoPresto alopre...@apache.org alopresto.apa...@gmail.com PGP Fingerprint: 70EC B3E5 98A6 5A3F D3C4 BACE 3C6E F65B 2F7D EF69 > On May 2, 2017, at 3:51 PM, Bryan Bende wrote: > > Thanks Drew. These seem like good candidates for the release.

Re: Closing in on a NiFi 1.2.0 release?

Thanks Drew. These seem like good candidates for the release. On Tue, May 2, 2017 at 3:42 PM, Andrew Lim wrote: > There are three doc updates/additions that would be great to include in the > RC: > > https://issues.apache.org/jira/browse/NIFI-3701 > https://issues.apache.org/jira/browse/NIFI-377

Re: Closing in on a NiFi 1.2.0 release?

There are three doc updates/additions that would be great to include in the RC: https://issues.apache.org/jira/browse/NIFI-3701 https://issues.apache.org/jira/browse/NIFI-3773 https://issues.apache.org/jira/browse/NIFI-3774 Sarah Olson and I have been working on these. We should have PRs submitt

Re: Closing in on a NiFi 1.2.0 release?

Haven't had much luck in getting our Docker efforts incorporated into Docker Hub. As a result I have created an issue to track that integration [1] and resolved the original issue. We can evaluate our options and figure out the best path forward. At this time procedures are not yet well establis

Re: Closing in on a NiFi 1.2.0 release?

I will be making updates to the Release Notes and Migration Guidance doc regarding the TLS 1.2 version support. Tracked by: https://issues.apache.org/jira/browse/NIFI-3720 -Drew > On May 2, 2017, at 11:08 AM, Joe Witt wrote: > > Those are great updates. I'd recommend we avoid highlighting

Re: Closing in on a NiFi 1.2.0 release?

Those are great updates. I'd recommend we avoid highlighting the versions of UI components though. Thanks On Tue, May 2, 2017 at 11:03 AM, Scott Aslan wrote: > Hey Bryan, > > Please include the following in the release notes: > > >- Core UI > - Circular references have been removed a

Re: Closing in on a NiFi 1.2.0 release?

Hey Bryan, Please include the following in the release notes: - Core UI - Circular references have been removed and the code modularized. - Upgraded Node version to 6.9.3. - Upgraded npm version to 3.10.10. - Upgraded jQuery version to 3.1.1. - Upgraded D3 versio

Re: Closing in on a NiFi 1.2.0 release?

Quick update... I was looking through PRs and noticed that NIFI-3594 (Encrypted Prov Repo) had already received a +1 and just needed an update to resolve conflicts with master. I spoke to Andy offline and he is planning to resolve the conflicts shortly and we can include this in 1.2.0. Also, NIF

Re: Closing in on a NiFi 1.2.0 release?

All, Looks like we are closer than we have ever been! Down to three outstanding JIRAs... - NIFI-1833 (Azure Processors) - Active review and discussion occurring, appears to be close - NIFI-3260 (Official Docker Image) - Active discussion, looks like this may be moved from the release to a separa

Re: Closing in on a NiFi 1.2.0 release?

Looks like we are down to just a few tickets, and all of them seem to have traction in terms of review and discussion. I'll keep an eye on the tickets and start trying to pull together anything I can to get ready for the RC process. Seems like we are close! On Tue, Apr 25, 2017 at 9:33 AM, Russel

Re: Closing in on a NiFi 1.2.0 release?

Many thanks to all the industrious folk working on this tool that's become indispensable to so many. The community has my enduring gratitude and admiration! Russ On 04/24/2017 07:16 PM, Joe Witt wrote: Robert, We're about 10 or so JIRAs away at this point and all of them have PRs and progres

Re: Closing in on a NiFi 1.2.0 release?

Robert, We're about 10 or so JIRAs away at this point and all of them have PRs and progress on them. We need to close those down and do some stabilization/testing then a release candidate can happen. So perhaps next week we'll be at that point and have a release. This is the right place to be w

Re: Closing in on a NiFi 1.2.0 release?

Hi, is there any date set for 1.2.0 release yet? We are running into an NIFI-3389 issue and would like to know when we can expect 1.2.0 release to be available. Thanks, Robert -- View this message in context: http://apache-nifi-developer-

Re: Closing in on a NiFi 1.2.0 release?

ache@gmail. >>> com> >>>>>>>>>>>>>>> PGP Fingerprint: 70EC B3E5 98A6 5A3F D3C4 BACE 3C6E F65B >>> 2F7D >>>>>>> EF69 >>>>>>>>>>>>>>> >>>>>>>>>>

Re: Closing in on a NiFi 1.2.0 release?

gt;> >>>> >>> >>>>> minor fixes are needed, then I believe >> >>>> >>> >>>>> it is appropriate to Cancel Patch. Once those changes >> (minor or >> >>>> not) >> >>>> >>

Re: Closing in on a NiFi 1.2.0 release?

gt;>> changes of some kind and won't be merged as-is, then we > should > >>>> Cancel > >>>> >>> >>>>> Patch. > >>>> >>> >>>>> > >>>> >>> >>>>> Do you or ot

Re: Closing in on a NiFi 1.2.0 release?

>>>> >>> >>> >>> >>> >>>>> >>>> >>> >>>>> lopre...@apache.org><mailto:alopre...@apache.org>> wrote: >>>> >>> >>>>> >>>> >>> >>>>>

Re: Closing in on a NiFi 1.2.0 release?

>> >>>>> aware of this process). I think it’s better than waiting for the >>> >>> merge, >>> >>> >>> >>> >>> >>> as >>> >>> >>>>> >>> >>> >>>>> I p

Re: Closing in on a NiFi 1.2.0 release?

;> >>>>> just looking for clarification from the contributor, and I don’t >> >>> think >> >>> >>> >> >>> >>> that >> >>> >>>>> >> >>> >>>>> warrants canceling the

Re: Closing in on a NiFi 1.2.0 release?

gt;>> >>>>> On Feb 24, 2017, at 12:08 PM, Mark Payne >>> >>> >>>>> arka...@hotmail.com><mailto:marka...@hotmail.com>> wrote: > >>> >>>>> > >>> >>>>> Personally, I a

Re: Closing in on a NiFi 1.2.0 release?

xVersion of the next release. Then I'll >>> go >>> >>>>> and review JIRA's that are >>> >>>>> in a state of "Patch Available." Even then I often come across many >>> >>>>> PR's >>> >>>>>

Re: Closing in on a NiFi 1.2.0 release?

tted. Then, whenever a committer >> reviews a >> >>>>> PR, he/she should be >> >>>>> responsible for updating the JIRA. If the PR is merged then the JIRA >> >>>>> should be resolved as Fixed. >> >>>>> But if the PR

Re: Closing in on a NiFi 1.2.0 release?

e followed this workflow, then a Release Manager (or anyone else) > >>> > >>> can > >>>>> > >>>>> easily see which tickets > >>>>> need to be reviewed before a release happens and which ones can be > >>> &

Re: Closing in on a NiFi 1.2.0 release?

As someone who has surely been guilty of optimistically setting fix >>>>> versions and then not meeting them, I second Joe's point about it >>> >>> holding >>>>> >>>>> up releases. Better to get the PR out, reviewed, and merged *befor

Re: Closing in on a NiFi 1.2.0 release?

cks (pwicks) < pwi...@micron.com <mailto:pwi...@micron.com>> wrote: Just for clarification, "We really need to avoid the practice of setting fix versions without traction", would mean don't set a version number until after we've submitted a PR? Until after the PR has

Re: Closing in on a NiFi 1.2.0 release?

R > >> and/or review traction necessary. > >> > >> From the contributor point of view: > >> If someone makes a contribution they obviously want that code to end > >> up in a release. But being an RTC community we need and want peer > >> review

Re: Closing in on a NiFi 1.2.0 release?

gt; related to systems or environments which are not easily replicated, >> etc.. are inherently harder to get peer review for. Also, the >> community has grown quite rapidly and sometimes the hygiene of a given >> PR isn't great. So our 'patch available' and 'open PR

Re: Closing in on a NiFi 1.2.0 release?

t times PRs can > sit too long sometimes people put a fix version on the JIRA so it acts > as a sort of 'gating function' on the release. This I am saying is > the practice that should not occur (given the thoughts above). We > should instead take the issue of how to more

Re: Closing in on a NiFi 1.2.0 release?

fair? Thanks Joe On Wed, Feb 22, 2017 at 2:39 PM, Peter Wicks (pwicks) mailto:pwi...@micron.com>> wrote: Just for clarification, "We really need to avoid the practice of setting fix versions without traction", would mean don't set a version number until after we've

Re: Closing in on a NiFi 1.2.0 release?

ix version on the JIRA so it acts > as a sort of 'gating function' on the release. This I am saying is > the practice that should not occur (given the thoughts above). We > should instead take the issue of how to more effectively > triage/review/provide feedback/and manage

Re: Closing in on a NiFi 1.2.0 release?

;We really need to avoid the practice of setting fix versions without traction", would mean don't set a version number until after we've submitted a PR? Until after the PR has been closed? Other? Thanks, Peter -Original Message- From: Joe Witt [mailto:joe.w...@gmail.com] Sent

Re: Closing in on a NiFi 1.2.0 release?

>>> contributions so contributors don't feel like their stuff will just >>> sit forever. >>> >>> Does that make sense and seem fair? >>> >>> Thanks >>> Joe >>> >>> >>> >>>> On Wed, Feb 22,

Re: Closing in on a NiFi 1.2.0 release?

will just >> sit forever. >> >> Does that make sense and seem fair? >> >> Thanks >> Joe >> >> >> >>> On Wed, Feb 22, 2017 at 2:39 PM, Peter Wicks (pwicks) >>> wrote: >>> Just for clarification, "We really need

Re: Closing in on a NiFi 1.2.0 release?

2:39 PM, Peter Wicks (pwicks) < > pwi...@micron.com> wrote: > >> Just for clarification, "We really need to avoid the practice of > setting fix versions without traction", would mean don't set a version > number until after we've submitted a PR? Until after t

Re: Closing in on a NiFi 1.2.0 release?

st for clarification, "We really need to avoid the practice of setting fix >> versions without traction", would mean don't set a version number until >> after we've submitted a PR? Until after the PR has been closed? Other? >> >> Thanks, >> Peter >

Re: Closing in on a NiFi 1.2.0 release?

n", would mean don't set a version number until after > we've submitted a PR? Until after the PR has been closed? Other? > > Thanks, > Peter > > -Original Message- > From: Joe Witt [mailto:joe.w...@gmail.com] > Sent: Wednesday, February 22, 2017 12:55 P

RE: Closing in on a NiFi 1.2.0 release?

e Witt [mailto:joe.w...@gmail.com] Sent: Wednesday, February 22, 2017 12:55 PM To: dev@nifi.apache.org Subject: Closing in on a NiFi 1.2.0 release? team, On the users lists we had an ask of when we are planning to cut a 1.2.0 release. And someone else asked me recently off-list. There are 45 ope

Closing in on a NiFi 1.2.0 release?

team, On the users lists we had an ask of when we are planning to cut a 1.2.0 release. And someone else asked me recently off-list. There are 45 open JIRAs tagged to it as of now. https://issues.apache.org/jira/issues/?jql=project%20%3D%20NIFI%20AND%20fixVersion%20%3D%201.2.0%20AND%20resolution