nifi-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Bryan Bende <bbe...@gmail.com>
Subject Re: Closing in on a NiFi 1.2.0 release?
Date Tue, 02 May 2017 19:51:12 GMT
Thanks Drew. These seem like good candidates for the release.

On Tue, May 2, 2017 at 3:42 PM, Andrew Lim <andrewlim.apache@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 <aldrinpiri@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.apache@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.witt@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 <scottyaslan@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 <bbende@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 <bbende@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 <
>>> russ@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 <henczr@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":
>>>>> "scottyaslan@gmail.com <scottyaslan@gmail.com>",        "linkedin":
>>>>> "http://www.linkedin.com/in/scottyaslan
>>>>> <http://www.linkedin.com/in/scottaslan>"    }});*
>>>
>>>
>

Mime
View raw message