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 <bbe...@gmail.com> wrote: > 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 <andre-li...@fucs.org> wrote: > >> 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 <andre-li...@fucs.org> wrote: >> >>> 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 ~/nifi/nifi-nar-bundles/nifi-cybersecurity-bundle/nifi-cyber >>> security-nar/target/nifi-cybersecurity-nar-1.2.0-SNAPSHOT.nar >>> ~/devel/nifi-1.2.0-SNAPSHOT/lib/nifi-cybersecurity-nar-1.2.0 >>> -SNAPSHOT.nar >>> >>> (note the different ~/nifi ~/devel used to ensure I don't explode the >>> rest of the already compiled components). >>> >>> When I try to make changes to the flow I am displayed with the following >>> error: >>> >>> [image: Inline image 1] >>> >>> This happens even when I try to drag and drop connected processors >>> around the canvas. >>> >>> >>> Oddly enough I can still add and delete components to the canvas but >>> whatever touches the tainted processor cannot be modified at all. >>> >>> Examples of messages: >>> >>> *Attempt to move* >>> >>> Component Position >>> [5, cb0a31ac-015b-1000-7473-873a47eb702e, >>> cb0a52ab-015b-1000-e43a-f6293a9ae99d] >>> is not the most up-to-date revision. This component appears to have been >>> modified >>> >>> >>> *Attempt to delete a downstream processor* >>> Error >>> [1, cb0a31ac-015b-1000-7473-873a47eb702e, >>> cb0b2ae4-015b-1000-35a8-9eaf6a45fc6a] >>> is not the most up-to-date revision. This component appears to have been >>> modified >>> >>> >>> I don't have a 1.1.0 instance around me at the moment but I vaguely >>> remember being able to do that in the past. >>> >>> Can someone confirm this is new and expected behavior? >>> >>> Cheers >>> >>> >>> On Wed, May 3, 2017 at 5:54 AM, Andy LoPresto <alopre...@apache.org> >>> wrote: >>> >>>> I’ll review & merge as soon as they are available. >>>> >>>> Andy LoPresto >>>> alopre...@apache.org >>>> *alopresto.apa...@gmail.com <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 <bbe...@gmail.com> wrote: >>>> >>>> Thanks Drew. These seem like good candidates for the release. >>>> >>>> On Tue, May 2, 2017 at 3:42 PM, Andrew Lim <andrewlim.apa...@gmail.com> >>>> 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-3773 >>>> https://issues.apache.org/jira/browse/NIFI-3774 >>>> >>>> Sarah Olson and I have been working on these. We should have PRs >>>> submitted for them very soon. >>>> >>>> -Drew >>>> >>>> >>>> On May 2, 2017, at 2:11 PM, Aldrin Piri <aldrinp...@gmail.com> wrote: >>>> >>>> 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 established within ASF to support >>>> configuring these builds. >>>> >>>> [1] https://issues.apache.org/jira/browse/NIFI-3772 >>>> >>>> On Tue, May 2, 2017 at 11:13 AM, Andrew Lim <andrewlim.apa...@gmail.com >>>> > >>>> wrote: >>>> >>>> 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 <joe.w...@gmail.com> wrote: >>>> >>>> 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 <scottyas...@gmail.com> >>>> >>>> wrote: >>>> >>>> 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 version to 3.5.17. >>>> - Reduced download size by removing bundled dependencies. >>>> - User Experience Improvements >>>> - Ever wish that it was easier to align components on the canvas? Me >>>> too...and now you can! >>>> - We now provide deep links to any component(s) on the canvas. This >>>> will help make collaborating and sharing more natural. >>>> - Users will enjoy a better understanding of the scope of >>>> >>>> Controller >>>> >>>> Services through an improved experience. >>>> - All actions available on the operate palette are now also >>>> >>>> available >>>> >>>> under the context menu too! >>>> >>>> Thanks! >>>> >>>> On Tue, May 2, 2017 at 10:17 AM, Bryan Bende <bbe...@gmail.com> wrote: >>>> >>>> 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 separate effort >>>> - NIFI-3765 (Status operation for NodeManager) - Active review, looks >>>> like it could be merged relatively soon >>>> >>>> Once these are finalized we should be able to start the RC process. >>>> >>>> I've started putting together the release notes on the Wiki (still a >>>> work in progress): >>>> https://cwiki.apache.org/confluence/display/NIFI/ >>>> Release+Notes#ReleaseNotes-Version1.2.0 >>>> >>>> If anyone knows of anything that should be highlighted, feel free to >>>> mention it here and I can update the notes. >>>> >>>> Thanks! >>>> >>>> -Bryan >>>> >>>> >>>> On Thu, Apr 27, 2017 at 5:52 PM, Bryan Bende <bbe...@gmail.com> wrote: >>>> >>>> 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, Russell Bateman < >>>> >>>> r...@windofkeltia.com> >>>> >>>> wrote: >>>> >>>> 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 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 watching to see it closing in. >>>> >>>> Thanks >>>> Joe >>>> >>>> On Mon, Apr 24, 2017 at 5:40 AM, roboh <hen...@gmail.com> wrote: >>>> >>>> >>>> Hi, >>>> >>>> is there any date set for 1.2.0 release yet? >>>> We are running into an NIFI-3389 >>>> <https://issues.apache.org/jira/browse/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-list.39713.n7.nabble.com/ >>>> >>>> Closing-in-on-a-NiFi-1-2-0-release-tp14907p15532.html >>>> >>>> Sent from the Apache NiFi Developer List mailing list archive at >>>> Nabble.com. >>>> >>>> >>>> >>>> >>>> >>>> >>>> >>>> -- >>>> *Scott Aslan = new WebDeveloper(* >>>> *{ "location": { "city": "Saint Cloud", "state": "FL", >>>> "zip": "34771" }, "contact": { "email": >>>> "scottyas...@gmail.com <scottyas...@gmail.com>", "linkedin": >>>> "http://www.linkedin.com/in/scottyaslan >>>> <http://www.linkedin.com/in/scottaslan>" }});* >>>> >>>> >>>> >>>> >>>> >>>> >>> >> >
