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?

Twitter processor stays. Great news! Thanks to Joey! Mit freundlichen Grüßen / best regards Kay-Uwe Moosheimer > Am 11.04.2017 um 21:20 schrieb Joe Witt : > > Team, > > Couple of good news updates on the release front is we're in the teens > on number of tickets AND Joey Frazee figured out a wa

Re: Closing in on a NiFi 1.2.0 release?

Team, Couple of good news updates on the release front is we're in the teens on number of tickets AND Joey Frazee figured out a way to clean up the twitter/json.org Cat-X dependency issue so our twitter processor stays! Will keep working the march down to 0 tickets. A lot of good stuff in this r

Re: Closing in on a NiFi 1.2.0 release?

Joe et. al, I think this one is close too (mainly dotting i's and crossing t's on license and notice) https://issues.apache.org/jira/browse/NIFI-3586 On Tue, Apr 4, 2017 at 2:23 PM, Joe Witt wrote: > Team, > > Another update on efforts to close-in on the NiFi 1.2.0 release. > We're below 20 JIR

Re: Closing in on a NiFi 1.2.0 release?

Team, Another update on efforts to close-in on the NiFi 1.2.0 release. We're below 20 JIRAs now and there has been good momentum. A couple items still need work but look really important and then there is review traction/feedback cycles. Will just keep monitoring it and actively defending to clo

Re: Closing in on a NiFi 1.2.0 release?

Team, Status of JIRA cleanup toward an Apache NiFi 1.2.0 release candidate which Mr Bende has so wonderfully volunteered to RM: There are 20 open JIRAs as of now. 12 of 20 have PRs that appear ready/close to ready. One pattern I noticed quite a bit on the 1.2.0 release is heavy usage of 'squatt

Re: Closing in on a NiFi 1.2.0 release?

Sweet! I'll take that deal all day. Thanks Bryan! On Wed, Mar 22, 2017 at 8:26 PM, Bryan Bende wrote: > Joe, > > As of today I believe the PR for NIFI-3380 (component versioning) should > address all of the code review feedback and is in a good place. > > Would like to run through a few more te

Re: Closing in on a NiFi 1.2.0 release?

Joe, As of today I believe the PR for NIFI-3380 (component versioning) should address all of the code review feedback and is in a good place. Would like to run through a few more tests tomorrow, and baring any additional feedback from reviewers, we could possibly merge that tomorrow. That PR will

Re: Closing in on a NiFi 1.2.0 release?

Bryan How are things looking for what you updated on? The nar plugin of course is out. We got another question on the user list for 1.2 so I just want to make sure we're closing in. I'll start doing the JIRA whipping. Thanks JOe On Mon, Mar 13, 2017 at 3:22 PM, Bryan Bende wrote: > Just a qu

Re: Closing in on a NiFi 1.2.0 release?

Just a quick update on this discussion... On Friday we were able to post an initial PR for the component versioning work [1]. I believe we are ready to move forward with a release of the NAR Maven plugin, there are three tickets to be included in the release [2]. If there are no objections, I ca

Re: Closing in on a NiFi 1.2.0 release?

+1 for component versioning in 1.2.0, it will be a solid capstone feature. And I agree it's probably not holding up the release. Thanks, James On Wed, Mar 8, 2017 at 1:21 PM, Bryan Bende wrote: > James, > > No problem :) > > I was mostly just suggesting an overall strategy... > > Usually when

Re: Closing in on a NiFi 1.2.0 release?

James, No problem :) I was mostly just suggesting an overall strategy... Usually when we start closing in on a release we go through the JIRAs tagged for that release and try to figure out which ones can be moved to a future release, and which ones the community is actually working on and close

Re: Closing in on a NiFi 1.2.0 release?

+1 for component versioning in NiFi 1.2! On 03/08/2017 12:40 PM, James Wing wrote: Bryan, I'm 100% in favor of you and Matt Gilman doing all the hard work. Oh, and uh... thanks! :) So the alternatives are: a.) Release 1.2.0 sooner (?), but without component versioning b.) Delay 1.2.0 (?) to inc

Re: Closing in on a NiFi 1.2.0 release?

Bryan, I'm 100% in favor of you and Matt Gilman doing all the hard work. Oh, and uh... thanks! :) So the alternatives are: a.) Release 1.2.0 sooner (?), but without component versioning b.) Delay 1.2.0 (?) to incorporate component versioning Will the NAR plugin alone commit us to all of the compo

Re: Closing in on a NiFi 1.2.0 release?

Just wanted to mention that one of the JIRAs tagged for 1.2.0 is NIFI-3380 "support multiple versions of the same component" [1] and I've been working with Matt Gilman on this [2]. The functionality is very close to being done and I think we should get this into the 1.2.0 release. In order to full

Re: Closing in on a NiFi 1.2.0 release?

This is good discussion that should continue, but what about the original intent of Joe's post? "Is there any reason folks can think of to hold off on a 1.2.0 release?" On Fri, Mar 3, 2017 at 1:45 PM, Mark Payne wrote: > Andy, > > Sorry, i haven't responded to this thread in over a week, but I

Re: Closing in on a NiFi 1.2.0 release?

Andy, Sorry, i haven't responded to this thread in over a week, but I think it's important to keep going. I just clicked "Cancel Patch" on one of my ticket that has a patch available to see which state it returned to. It did in fact go back to Open. Which I agree is less than ideal. Though we

Re: Closing in on a NiFi 1.2.0 release?

Mark, Your understanding of “Patch Available” certainly makes sense and it explains why you approach the process the way you do. I have a slightly different personal understanding of “Patch Available” — I read it to mean “the person responsible for this Jira has contributed code they feel solve

Re: Closing in on a NiFi 1.2.0 release?

Andy, If the reviewer is looking for clarification, then it may make sense to leave the JIRA in "Patch Available" state as you suggest. If there are minor fixes needed, though, then the patch is not ready. In JIRA, the verbiage for Cancel Patch says "The patch is not yet ready to be committed."

Re: Closing in on a NiFi 1.2.0 release?

Mark, I like your point about updating the Jira with the Fix Version at the time the PR review begins (or when the PR is submitted, if the contributor is aware of this process). I think it’s better than waiting for the merge, as I proposed before. I agree that the reviewer is responsible for k

Re: Closing in on a NiFi 1.2.0 release?

Personally, I am afraid that if we don't set a Fix Version on JIRA's, that some PR's will be lost or stalled. I rarely go to github and start looking through the PRs. Instead, I go to JIRA and look at what is assigned with a fixVersion of the next release. Then I'll go and review JIRA's that are

Re: Closing in on a NiFi 1.2.0 release?

Slightly off topic, but your statement "we need reviews/feedback as much as we need contributions" made me think that the project could somehow benefit from the concept of Kanban Work In Progress limits. Not sure how you'd implement this with an open source project, but just a thought. On Thu, Fe

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 *before* setting the fix version in my opinion. Andy LoPresto alopre...@apache.org alopresto

Re: Closing in on a NiFi 1.2.0 release?

Peter, This is just my preference so discussion is certainly open. But the way I see it we should not set the fix version on JIRAs unless they really should block a release without resolution or if due to some roadmap/planning/discussion it is a new feature/improvement that is tied to a release.

RE: Closing in on a NiFi 1.2.0 release?

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 been closed? Other? Thanks, Peter -Original Message- From: Joe Witt [mailto:joe.w...@