+1 

Tested build from source with CMAKE on ubuntu 18.04, gluoncv master unittests 
passed.

-Zhi

> On Oct 30, 2020, at 7:28 PM, Sheng Zha <[email protected]> wrote:
> 
> +1
> 
>> On Oct 30, 2020, at 5:20 PM, Manu Seth <[email protected]> wrote:
>> 
>> +1
>> 
>> I built MXNet tag 1.8.0.rc2 from source following instructions on [1] using
>> cmake config file [2] on an Ubuntu 18.04 Deep Learning Base AMI, with CUDA
>> v11.0 and cuDNN v8.0.2, and tested it by running all non operator tests in
>> tests/python/gpu/ folder.
>> 
>> [1]
>> https://github.com/apache/incubator-mxnet/blob/1.8.0.rc2/docs/static_site/src/pages/get_started/build_from_source.md#building-mxnet
>> [2]
>> https://github.com/apache/incubator-mxnet/blob/1.8.0.rc2/config/linux_gpu.cmake
>> 
>> Manu Seth
>> 
>>> On Thu, Oct 29, 2020 at 8:08 PM Skalicky, Sam <[email protected]>
>>> wrote:
>>> 
>>> Dear MXNet community,
>>> 
>>> This is the vote to release Apache MXNet (incubating) version 1.8.0.
>>> Voting will start October 29, 20:10:00 PT and close on November 1, 20:10:00
>>> PT.
>>> 
>>> Link to release notes:
>>> https://cwiki.apache.org/confluence/display/MXNET/1.8.0+Release+Notes
>>> 
>>> Link to release candidate:
>>> https://github.com/apache/incubator-mxnet/releases/tag/1.8.0.rc2
>>> 
>>> Link to source and signatures on apache dist server:
>>> https://dist.apache.org/repos/dist/dev/incubator/mxnet/1.8.0.rc2
>>> 
>>> Please remember to TEST first before voting accordingly:
>>> +1 = approve
>>> +0 = no opinion
>>> -1 = disapprove (provide reason)
>>> 
>>> Here are the changes comparing to 1.8.0.rc1:
>>> 
>>> * Updated LICENSE for all submodules
>>> * Updated oneDNN to v1.6.5 for RNN bugfix
>>> * Fixed type issue for broadcast_like
>>> * Fix MKLDNN BatchNorm with even number of channels
>>> * CI enhancements
>>> * Fix SoftReLU fused operator numerical stability
>>> * More Extensions fixes
>>> * Changed intgemm to a submodule instead of fetch
>>> * Updated DISCLAIMER
>>> * Update cuDNN version
>>> 
>>> Best regards,
>>> Sam Skalicky
>>> 
>>> 
>>> 

Reply via email to