Thanks for clarifying. All contributors who made more than 10 commits to
msahdow before are committers of MXNet, so their ICLAs should already be on
file: tqchen, bingxu, eric.xie, sxjscience, mli, yajiedesign [1]. If you
think this is OK, one of the mentors or I can start the notification.
Hi,
> Thank you, Justin. Though I’m still uncertain about what the definition of IP
> clearance process is.
The bit you quoted there is for an initial code base, it the second part of
that document you need to look at.
In short as well as the SGA you need to get signed ICLA from all of the
Thank you, Justin. Though I’m still uncertain about what the definition of IP
clearance process is, I found the following paragraphs that seem relevant.
Sounds like we need three votes from our mentors here for this acceptance. If
that’s the case, I can start a vote on it.
Regards,
Sheng
>
Hi,
See also:
https://incubator.apache.org/guides/ip_clearance.html
Thanks,
Justin
HI,
> Yes and yes. I filed the software grant and received confirmation from
> secretary@.
As well as the software grant the incline code base needs to go through IP
clearance. See [1] option 2.
IP clearance involves making sure all all contributors have signed ICLAs and
there are no license
Hi Justin,
Yes and yes. I filed the software grant and received confirmation from
secretary@.
I’m not sure if I should be updating the page, and if so, how.
Regards,
Sheng
> On Jul 22, 2020, at 1:59 AM, Justin Mclean wrote:
>
> Hi,
>
> Has the IP clearance process been followed? I don't
@fhieber we are planning to release the first public beta on this somewhere in
August. At the moment we are finalizing some API changes and also validating
them in GluonNLP. We will publish a transition doc as part of the public beta.
--
You are receiving this because you are subscribed to
+1 binding.
Tested
- build
- gluoncv unittests
- gluoncv training examples
Best,
Zhi
> On Jul 22, 2020, at 12:30 AM, Tao Lv wrote:
>
> +1 (binding)
>
>
>
> - Untar the source code package;
>
> - Build from source code with makefile, USE_BLAS=mkl, USE_MKLDNN=1;
>
> - Check
@szha is there a recent estimate on the timeline for MXNet 2.0? Would you
recommend to develop downstream toolkits (e.g. Sockeye) against the master
branch now or rather wait a little bit longer?
Is there already documentation on how to transition MXNet 1.x projects to 2.x?
--
You are
Hi,
Has the IP clearance process been followed? I don't see it listed on this page
[1]
Does the current release being voted on contain this code?
Thanks,
Justin
1. https://incubator.apache.org/ip-clearance/
+1 (binding)
- Untar the source code package;
- Build from source code with makefile, USE_BLAS=mkl, USE_MKLDNN=1;
- Check mx.__version__;
- Run benchmark_score.py under examples/image-classification.
On Wed, Jul 22, 2020 at 3:13 PM Patrick Mu wrote:
> + 1
>
> Test custom operators: all
+ 1
Test custom operators: all examples using custom operators are passing, no
error or regression found
Ziyi
On 2020/07/22 06:56:46, Kshitij Kalambarkar
wrote:
> + 1
>
> * Built from source on Ubuntu 18.04 with CUDA, CUDNN
> * Verified test_higher_order_grad.py
>
> Great job!
>
> On
+ 1
* Built from source on Ubuntu 18.04 with CUDA, CUDNN
* Verified test_higher_order_grad.py
Great job!
On Wed, Jul 22, 2020 at 12:02 PM Chaitanya Bapat
wrote:
> +1
>
> - Built from source on Ubuntu18 with CUDA ON, USE_INT64_TENSOR_SIZE ON
> - Verified large tensor tests work as expected on
+1
- Built from source on Ubuntu18 with CUDA ON, USE_INT64_TENSOR_SIZE ON
- Verified large tensor tests work as expected on a p3.16xl instance [with
8 Tesla V100 GPUs]
- Verified OpPerf utility works as expected.
Steps followed:
+1
Build from source on Ubuntu 18 with CUDA/CUDNN/NCCL ON and verified with
Horovod 0.19.5 by running unittest and integration tests.
Thanks,
Karan
On Tue, Jul 21, 2020 at 10:23 PM Sheng Zha wrote:
> +1. I checked:
>
> [x] Are release files in correct location? Yes
> [x] Do release files have
15 matches
Mail list logo
