+1 (binding)
On 01.12.2017 04:30, Chris Olivier wrote:
+1
Additional note:
This MXNet v1.0 release is planned to be announced at the NIPS conference
starting Monday, 04-Dec and hence would request your support in meeting
this timeline. We will continue to address any non-critical issues after
Hi,
+1 binding (if the issues below are put in a JIRA and fixed for next release)
Much improved over RC0 but rat results are still hard to review. It’s reporting
2138 unknown licenses and I count 625 files without a license header so it’s
easy to miss something and I probably have. As
+1
Additional note:
This MXNet v1.0 release is planned to be announced at the NIPS conference
starting Monday, 04-Dec and hence would request your support in meeting
this timeline. We will continue to address any non-critical issues after
this release as well.
On Thu, Nov 30, 2017 at 4:45 PM,
Hello All,
This is a call for releasing Apache MXNet (incubating) 1.0.0, release
candidate 1.
Apache MXNet community has voted and approved the release.
*Vote thread:*
https://lists.apache.org/thread.html/568bf0c9960f14640b753a5fb6766c
7b0074339d286f405c04ffec96@%3Cdev.mxnet.apache.org%3E
Hello Sergio,
This is how the NOTICE file looks at the moment -
https://github.com/apache/incubator-mxnet/blob/v1.0.0/NOTICE
I had worked on the NOTICE file prior to the 0.11.0 Release and had
followed the link you mentioned.
I had added a few notices into this file, including Caffe, MS coco etc
Hi Sergio,
Thanks for guidance.
The binary file has been removed now.
See: https://github.com/dmlc/tvm/tree/master/apps/android_rpc/gradle/wrapper
We are testing the changes currently and expect to submit a new RC by end
of today.
Regards,
Bhavin Thaker.
On Thu, Nov 30, 2017 at 9:40 AM Sergio
Generally speaking, I follow these key aspects:
* Don't put anything in NOTICE for the sake of an MIT or a 3-clause BSD
licensed dependency.
* For an ALv2 dependency, follow the instructions in the licensing howto:
http://www.apache.org/dev/licensing-howto.html
* For all other licenses, either
Hi all,
The Apache Griffin (incubating) team is pleased to announce the
release of Griffin 0.1.6-incubating.
Apache Griffin is data quality solution for modern data system,
it defines a standard process to define, measure data quality for
well-known dimensions.
The release is available at:
> This was in private chat and a zoom video call between Sheng and myself.
> So it's not a documented event.
> Sheng, maybe you also had similar conversations also with Luke?
Mick,
Yes, I and Luke talked about this too.
John,
Mick and I wrote down this section, because some of our committers
The vote is almost finished. All OpenSkywalking members and Initial Committers
agree that. Thanks to Mick's guidances and helps.
--
Sheng Wu
SkyWalking
-- Original --
From: "mck";;
Date: Thu, Nov 30, 2017 07:20 PM
To:
On Thu, Nov 30, 2017 at 3:51 AM, sebb wrote:
> On 29 November 2017 at 13:44, John D. Ament wrote:
> > On Wed, Nov 29, 2017 at 5:59 AM sebb wrote:
> >
> >> Top posting
> >>
> >> The proposal includes a user@ mailing list.
> >> This is
> >
> > Who owns this code? Will an SGA be provided, or ICLAs from contributors?
> > If ICLAs, are there any of the current 16 contributors who will not
> > provide an ICLA?
>
>
> I gone through this wil Sheng. An SGA will be provided as well as an
> ICLA from contributors.
> Sheng will bring
John, thanks for the time and input. My replies are inline.
> > = Proposal =
> > The goal of this proposal is to bring the existing Skywalking
> > https://github.com/OpenSkywalking/skywalking codebase and existing
> > developers and community into the Apache Software Foundation (ASF) in
> >
> > The proposal includes a user@ mailing list.
> > This is generally not recommended for podlings as their focus needs to
> > be on building the developer community.
> >
>
> Podlings are more than welcomed to include user@ lists. There's nothing
> stopping them from building developers and
On 29 November 2017 at 13:44, John D. Ament wrote:
> On Wed, Nov 29, 2017 at 5:59 AM sebb wrote:
>
>> Top posting
>>
>> The proposal includes a user@ mailing list.
>> This is generally not recommended for podlings as their focus needs to
>> be on building
15 matches
Mail list logo