essage-
> From: Jason Dai
> Sent: Wednesday, August 19, 2020 10:16 PM
> To: general@incubator.apache.org
> Subject: Re: [VOTE] Release Apache MXNet (incubating) version 1.7.0.rc1
>
> +1 (binding)
>
>
> I checked:
>
> - Incubating
ding votes for this release, please help on this, many thanks!!
Regards,
-Ciyong
-Original Message-
From: Jason Dai
Sent: Wednesday, August 19, 2020 10:16 PM
To: general@incubator.apache.org
Subject: Re: [VOTE] Release Apache MXNet (incubating) version 1.7.0.rc1
+
: Wednesday, August 19, 2020 10:16 PM
To: general@incubator.apache.org
Subject: Re: [VOTE] Release Apache MXNet (incubating) version 1.7.0.rc1
+1 (binding)
I checked:
- Incubating in name
- Signatures and hashes
- Disclaimer, LICENSE and NOTICE
Thanks,
-Jason
On Tue, Aug 18, 2020 at 6:25 PM
t; Currently, the entire test suite will run through many different
> configurations of hardware and docker image via CI pipeline.
> >
> > Thanks,
> > -Ciyong
> >
> > -Original Message-
> > From: Michael Wall
> > Sent: Tuesday, August 18,
ails for all the test cases.
> Currently, the entire test suite will run through many different
> configurations of hardware and docker image via CI pipeline.
>
> Thanks,
> -Ciyong
>
> -Original Message-----
> From: Michael Wall
> Sent: Tuesday, August 18, 2020 9:54 AM
&
Currently, the entire test suite will run through many different configurations
of hardware and docker image via CI pipeline.
Thanks,
-Ciyong
-Original Message-
From: Michael Wall
Sent: Tuesday, August 18, 2020 9:54 AM
To: general@incubator.apache.org
Subject: Re: [VOTE] Release Apache
+1 from me
Checked
- signatures
- incubating in name
- License, Notice and Disclaimer
- Compiled from source with CPP bindings using
https://mxnet.apache.org/versions/1.6/get_started/build_from_source#install-mxnet-for-python,
https://mxnet.apache.org/versions/1.6/get_started/cpp_setup and
Hi Justin,
Since the blocking issue has been resolved, would you mind changing your vote?
Thanks.
Regards,
Sheng
On 2020/07/26 01:27:39, Justin Mclean wrote:
> Hi,
>
> -1 (binding) as this release contains code that hasn’t gone though IP
> clearance (mshadow).
>
> I checked:
> -
t; The vote will be open for 72 hours.
> [ ] +1 release this package as # [ ] +0 no opinion [ ] -1 do not
> release this package because...
>
> Best regards,
> Ciyong Chen
>
> -Original Message-
> From: Sheng Zha
> Sent: Tuesday, August 11, 2020 3:36 AM
> To:
ckage as # [ ] +0 no opinion [ ] -1 do not
> release this package because...
>
> Best regards,
> Ciyong Chen
>
> -----Original Message-----
> From: Sheng Zha
> Sent: Tuesday, August 11, 2020 3:36 AM
> To: general@incubator.apache.org
> Subject: Re: [VOTE] Release Apac
-Original Message-
From: Sheng Zha
Sent: Tuesday, August 11, 2020 3:36 AM
To: general@incubator.apache.org
Subject: Re: [VOTE] Release Apache MXNet (incubating) version 1.7.0.rc1
Hi,
Since the IP clearance for MShadow has passed [1] and third-party release
issues are either resolved or tracked
Hi,
Since the IP clearance for MShadow has passed [1] and third-party release
issues are either resolved or tracked in INCUBATOR-253, let's resume this
vote.
Here's my +1 carried from vote on dev@ [2].
[1]
On Tue, Aug 4, 2020 at 11:01 PM Justin Mclean
wrote:
> Hi,
>
> > 1. Change all MXNet to Apache MXNet (incubating) from documentation
> where it necessary
> > 2. Change maven package description ” MXNet Engine Adapter for DJL”
> to "Deep Java Library (DJL) Engine Adapter for Apache MXNet"
Hi -
Sent from my iPhone
> On Aug 4, 2020, at 8:01 PM, Justin Mclean wrote:
>
> Hi,
>
>> 1. Change all MXNet to Apache MXNet (incubating) from documentation where
>> it necessary
>> 2. Change maven package description ” MXNet Engine Adapter for DJL” to
>> "Deep Java Library (DJL) Engine
Hi,
> 1. Change all MXNet to Apache MXNet (incubating) from documentation where
> it necessary
> 2. Change maven package description ” MXNet Engine Adapter for DJL” to
> "Deep Java Library (DJL) Engine Adapter for Apache MXNet" for clarification
Thanks for doing that. ASF generally
apache.org
Subject: Re: [VOTE] Release Apache MXNet (incubating) version 1.7.0.rc1
Hi,
-1 (binding) as this release contains code that hasn’t gone though IP clearance
(mshadow).
I checked:
- incubating in name
- disclaimer exists
- LICENSE and NOTICE have improved but I did not do an exhaus
Hi,
> Again, we are NOT releasing release candidates.
No but companies that your PPMC members are employed by are.
Those PPMC members are in a good position to make sure their employers are
aware of and follow ASF policies where needed. It's part of a (P)PMC duties to
make sure branding,
Hi Justin,
> It’s not seperate as you release candidates being distributed to users. I
still want to know why release candidates are being released in this way,
in particular by companies where there are MXnet PPMC members. What steps
will the PPMC will take to stop this from happening in the
@incubator.apache.org
Subject: Re: [VOTE] Release Apache MXNet (incubating) version 1.7.0.rc1
Hi,
> It seems that most of the concerns are branding/trademark/legal issues from
> those third-party projects which relies on MXNet and the AWS marketplace (or
> MXNet's downstream projects), wh
Hi,
> It seems that most of the concerns are branding/trademark/legal issues from
> those third-party projects which relies on MXNet and the AWS marketplace (or
> MXNet's downstream projects), which could be tracked separately and improved
> continually to 100% meet the requirement of
To: general@incubator.apache.org
Subject: Re: [VOTE] Release Apache MXNet (incubating) version 1.7.0.rc1
Hi,
> For mshadow, it is a third-party component that MXNet has been relying
> on since the initial contribution to MXNet. It has been included in
> previous releases since its category-
Hi,
> For mshadow, it is a third-party component that MXNet has been relying on
> since the initial contribution to MXNet. It has been included in previous
> releases since its category-A license allows us to do so. For this release,
> we are still releasing it as a third-party module, as
Hi Justin,
Thanks for voting. Here are some clarifications:
For mshadow, it is a third-party component that MXNet has been relying on
since the initial contribution to MXNet. It has been included in previous
releases since its category-A license allows us to do so. For this release,
we are still
Hi,
-1 (binding) as this release contains code that hasn’t gone though IP clearance
(mshadow).
I checked:
- incubating in name
- disclaimer exists
- LICENSE and NOTICE have improved but I did not do an exhaustive check
- No unexpected binary file
- ASF files have ASF headers
- unable to
24 matches
Mail list logo
