Re: [RESULTS][VOTE] Release Apache MXNet (incubating) version 1.4.0.rc3

[Piyush Ghai]

Hi all,

I’m happy to announce the results of the vote. 

This vote passes with 7 +1 votes (4 binding) and no 0 or -1 votes.

+1 votes
Carin / binding
Sheng / binding
Indhu / binding
Haibin / binding
Qing 
Roshani
Yuxi Hu

0 Votes 
No votes

-1 Votes
No votes


Vote thread can be found here [1]. 
I will continue with the release process on general@ and the release 
announcement will follow in the next few days.

Thanks,
Piyush 


[1] 
https://lists.apache.org/thread.html/618ad28580e838254f998deb71373467374a05228401dae0323a6d0f@%3Cdev.mxnet.apache.org%3E
 

On 2019/02/19 17:53:08, Piyush Ghai  wrote: 
> Hi all,> 
> 
> There’s a small clarification. I was just made aware that only PMC members 
> have binding votes. > 
> So I’m nullifying this result as for now. > 
> 
> As per the PMC criteria, I still need at least 2 more votes from PMC members. 
> > 
> 
> I’ll update this thread when I have sufficient number of votes from PMC 
> members. > 
> 
> Thanks,> 
> Piyush> 
> 
> On 2019/02/19 17:40:43, Piyush Ghai  wrote: > 
> > Dear MXNet community,> > 
> > > 
> > I’m happy to announce the results of the vote. > > 
> > > 
> > This vote passes with 4 +1 votes (3 binding) and no 0 or -1 votes.> > 
> > > 
> > +1 votes> > 
> > Carin / binding> > 
> > Qing / binding> > 
> > Roshani / binding> > 
> > Yuxi Hu> > 
> > > 
> > 0 Votes > > 
> > No votes> > 
> > > 
> > -1 Votes> > 
> > No votes> > 
> > > 
> > > 
> > Vote thread can be found here [1]. > > 
> > I will continue with the release process on general@ and the release 
> > announcement will follow in the next few days.> > 
> > > 
> > Thanks,> > 
> > Piyush > > 
> > > 
> > > 
> > [1] 
> > https://lists.apache.org/thread.html/618ad28580e838254f998deb71373467374a05228401dae0323a6d0f@%3Cdev.mxnet.apache.org%3E
> >  
> > >
> >  > 

Re: [VOTE] Release Apache MXNet (incubating) version 1.4.0.rc3

[Indhu]

+1

Built from source. Verified distributed training of Resnet50 works fine.

On Tue, Feb 19, 2019, 11:43 AM Sheng Zha  -[Y] Are release files in correct location?
> -[Y] Do release files have the word incubating in their name?
> -[Y] Are the digital signature and hashes correct?
> -[Y] Does DISCLAIMER file exist?
> -[Y] Do LICENSE and NOTICE files exists?
> -[Y] Is the LICENSE and NOTICE text correct?
> -[N] Is the NOTICE year correct?
> -[Y] Un-included software dependencies are not mentioned in LICENSE or
> NOTICE? (sz: did not finish checking)
> -[Y] License information is not mentioned in NOTICE?
> Is there any 3rd party code contained inside the release? If so:
> -[Y] Does the software have a compatible license?
> -[Y] Are all software licenses mentioned in LICENSE?
> -[Y] Is the full text of the licenses (or pointers to it) in LICENSE?
> Is any of this code Apache licensed? Do they have NOTICE files? If so:
> -[Y] Have relevant parts of those NOTICE files been added to this NOTICE
> file?
> -[Y] Do all source files have ASF headers?
> -[Y] Do the contents of the release match with what's tagged in version
> control?
> -[N] Are there any unexpected binary files in the release?
> -[Y] Can you compile from source? Are the instruction clear?
>
> +1 with the caveat:
> - NOTICE year was fixed on master but not on the release candidate. rc3
> still reads "2017-2018"
>
> -sz
>
> On 2019/02/19 00:19:52, Roshani Nagmote 
> wrote:
> > +1 Downloaded, installed on Ubuntu 16.04. Verified signatures.
> > Built from source with cuda enabled. Ran train_mnist.py test
> successfully.
> >
> > Thanks,
> > Roshani
> >
> > On Sun, Feb 17, 2019 at 12:13 PM Carin Meier 
> wrote:
> >
> > > +1 Downloaded and verified the signature on the tar. Built and tested
> the
> > > Scala/Clojure package
> > >
> > > On Sun, Feb 17, 2019 at 2:13 PM Qing Lan  wrote:
> > >
> > > > +1 (binding) on the release. Checked Mac + Linux (Ubuntu 16.04) build
> > > from
> > > > source successfully. Checked Scala build with no errors.
> > > >
> > > > On 2/15/19, 6:08 PM, "Piyush Ghai"  wrote:
> > > >
> > > > Dear MXNet community,
> > > >
> > > > I would like to propose a vote to release Apache MXNet
> (incubating)
> > > > version v1.4.0.
> > > > Voting will start today, Friday February 15th 6pm PST and will
> close
> > > > on Monday,
> > > > February 18th 6pm PST.
> > > >
> > > > Link to release notes:
> > > >
> > > >
> > > >
> > >
> https://cwiki.apache.org/confluence/display/MXNET/Apache+MXNet+%28incubating%29+1.4.0+Release+Notes
> > > > <
> > > >
> > >
> https://cwiki.apache.org/confluence/display/MXNET/Apache+MXNet+(incubating)+1.4.0+Release+Notes
> > > > >
> > > >
> > > > Link to release candidate 1.4.0.rc3:
> > > >  <
> https://github.com/apache/incubator-mxnet/releases/tag/1.4.0.rc3/>
> > > > https://github.com/apache/incubator-mxnet/releases/tag/1.4.0.rc3 <
> > > > https://github.com/apache/incubator-mxnet/releases/tag/1.4.0.rc3>/
> > > >
> > > > Link to source and signatures on apache dist server:
> > > >
> https://dist.apache.org/repos/dist/dev/incubator/mxnet/1.4.0.rc3/ <
> > > > https://dist.apache.org/repos/dist/dev/incubator/mxnet/1.4.0.rc3/>
> > > >
> > > >
> > > > Please remember to TEST first before voting accordingly:
> > > > +1 = approve
> > > > +0 = no opinion
> > > > -1 = disapprove (provide reason)
> > > >
> > > >
> > > > Best regards,
> > > > Piyush
> > > >
> > > >
> > >
> >
>

Re: [VOTE] Release Apache MXNet (incubating) version 1.4.0.rc3

[Sheng Zha]

-[Y] Are release files in correct location?
-[Y] Do release files have the word incubating in their name?
-[Y] Are the digital signature and hashes correct?
-[Y] Does DISCLAIMER file exist?
-[Y] Do LICENSE and NOTICE files exists?
-[Y] Is the LICENSE and NOTICE text correct?
-[N] Is the NOTICE year correct?
-[Y] Un-included software dependencies are not mentioned in LICENSE or NOTICE? 
(sz: did not finish checking)
-[Y] License information is not mentioned in NOTICE?
Is there any 3rd party code contained inside the release? If so:
-[Y] Does the software have a compatible license?
-[Y] Are all software licenses mentioned in LICENSE?
-[Y] Is the full text of the licenses (or pointers to it) in LICENSE?
Is any of this code Apache licensed? Do they have NOTICE files? If so:
-[Y] Have relevant parts of those NOTICE files been added to this NOTICE
file?
-[Y] Do all source files have ASF headers?
-[Y] Do the contents of the release match with what's tagged in version control?
-[N] Are there any unexpected binary files in the release?
-[Y] Can you compile from source? Are the instruction clear?

+1 with the caveat:
- NOTICE year was fixed on master but not on the release candidate. rc3 still 
reads "2017-2018"

-sz

On 2019/02/19 00:19:52, Roshani Nagmote  wrote: 
> +1 Downloaded, installed on Ubuntu 16.04. Verified signatures.
> Built from source with cuda enabled. Ran train_mnist.py test successfully.
> 
> Thanks,
> Roshani
> 
> On Sun, Feb 17, 2019 at 12:13 PM Carin Meier  wrote:
> 
> > +1 Downloaded and verified the signature on the tar. Built and tested the
> > Scala/Clojure package
> >
> > On Sun, Feb 17, 2019 at 2:13 PM Qing Lan  wrote:
> >
> > > +1 (binding) on the release. Checked Mac + Linux (Ubuntu 16.04) build
> > from
> > > source successfully. Checked Scala build with no errors.
> > >
> > > On 2/15/19, 6:08 PM, "Piyush Ghai"  wrote:
> > >
> > > Dear MXNet community,
> > >
> > > I would like to propose a vote to release Apache MXNet (incubating)
> > > version v1.4.0.
> > > Voting will start today, Friday February 15th 6pm PST and will close
> > > on Monday,
> > > February 18th 6pm PST.
> > >
> > > Link to release notes:
> > >
> > >
> > >
> > https://cwiki.apache.org/confluence/display/MXNET/Apache+MXNet+%28incubating%29+1.4.0+Release+Notes
> > > <
> > >
> > https://cwiki.apache.org/confluence/display/MXNET/Apache+MXNet+(incubating)+1.4.0+Release+Notes
> > > >
> > >
> > > Link to release candidate 1.4.0.rc3:
> > >  
> > > https://github.com/apache/incubator-mxnet/releases/tag/1.4.0.rc3 <
> > > https://github.com/apache/incubator-mxnet/releases/tag/1.4.0.rc3>/
> > >
> > > Link to source and signatures on apache dist server:
> > > https://dist.apache.org/repos/dist/dev/incubator/mxnet/1.4.0.rc3/ <
> > > https://dist.apache.org/repos/dist/dev/incubator/mxnet/1.4.0.rc3/>
> > >
> > >
> > > Please remember to TEST first before voting accordingly:
> > > +1 = approve
> > > +0 = no opinion
> > > -1 = disapprove (provide reason)
> > >
> > >
> > > Best regards,
> > > Piyush
> > >
> > >
> >
> 

Re: [VOTE] Release Apache MXNet (incubating) version 1.4.0.rc3

[Haibin Lin]

+1
Built from source on Ubuntu and it passed kvstore unit tests.

Best,
Haibin

On Tue, Feb 19, 2019 at 10:03 AM Piyush Ghai  wrote:

> Hi all,
>
> I still need more votes from PMC members in order to conclude this vote.
>
> PMC members, please TEST and vote accordingly. Your votes will help us
> release MXNet version soon.
> I’m extending the voting thread until Feb 20th 12 AM PST.
>
> Best regards,
> Piyush
>
>
> On 2019/02/16 02:01:25, Piyush Ghai  wrote:
> > Dear MXNet community,>
> >
> > I would like to propose a vote to release Apache MXNet (incubating)
> version v1.4.0.>
> > Voting will start today, Friday February 15th 6pm PST and will close on
> Monday,>
> > February 18th 6pm PST.>
> >
> > Link to release notes:>
> >
> >
> https://cwiki.apache.org/confluence/display/MXNET/Apache+MXNet+%28incubating%29+1.4.0+Release+Notes
> <
> https://cwiki.apache.org/confluence/display/MXNET/Apache+MXNet+(incubating)+1.4.0+Release+Notes>>
>
> >
> > Link to release candidate 1.4.0.rc3:>
> >  
> https://github.com/apache/incubator-mxnet/releases/tag/1.4.0.rc3 <
> https://github.com/apache/incubator-mxnet/releases/tag/1.4.0.rc3>/>
> >
> > Link to source and signatures on apache dist server:>
> > https://dist.apache.org/repos/dist/dev/incubator/mxnet/1.4.0.rc3/ <
> https://dist.apache.org/repos/dist/dev/incubator/mxnet/1.4.0.rc3/> >
> >
> >
> > Please remember to TEST first before voting accordingly:>
> > +1 = approve>
> > +0 = no opinion>
> > -1 = disapprove (provide reason)>
> >
> >
> > Best regards,>
> > Piyush>

Re: [VOTE] Release Apache MXNet (incubating) version 1.4.0.rc3

[Piyush Ghai]

Hi all, 

I still need more votes from PMC members in order to conclude this vote. 

PMC members, please TEST and vote accordingly. Your votes will help us release 
MXNet version soon. 
I’m extending the voting thread until Feb 20th 12 AM PST. 

Best regards,
Piyush


On 2019/02/16 02:01:25, Piyush Ghai  wrote: 
> Dear MXNet community,> 
> 
> I would like to propose a vote to release Apache MXNet (incubating) version 
> v1.4.0.> 
> Voting will start today, Friday February 15th 6pm PST and will close on 
> Monday,> 
> February 18th 6pm PST.> 
> 
> Link to release notes:> 
> 
> https://cwiki.apache.org/confluence/display/MXNET/Apache+MXNet+%28incubating%29+1.4.0+Release+Notes
>  
> >
>  
> 
> Link to release candidate 1.4.0.rc3:> 
>  
> https://github.com/apache/incubator-mxnet/releases/tag/1.4.0.rc3
>  /> 
> 
> Link to source and signatures on apache dist server:> 
> https://dist.apache.org/repos/dist/dev/incubator/mxnet/1.4.0.rc3/ 
>  > 
> 
> 
> Please remember to TEST first before voting accordingly:> 
> +1 = approve> 
> +0 = no opinion> 
> -1 = disapprove (provide reason)> 
> 
> 
> Best regards,> 
> Piyush> 

Re: [RESULTS][VOTE] Release Apache MXNet (incubating) version 1.4.0.rc3

[Piyush Ghai]

Hi all,

There’s a small clarification. I was just made aware that only PMC members have 
binding votes. 
So I’m nullifying this result as for now. 

As per the PMC criteria, I still need at least 2 more votes from PMC members. 

I’ll update this thread when I have sufficient number of votes from PMC 
members. 

Thanks,
Piyush

On 2019/02/19 17:40:43, Piyush Ghai  wrote: 
> Dear MXNet community,> 
> 
> I’m happy to announce the results of the vote. > 
> 
> This vote passes with 4 +1 votes (3 binding) and no 0 or -1 votes.> 
> 
> +1 votes> 
> Carin / binding> 
> Qing / binding> 
> Roshani / binding> 
> Yuxi Hu> 
> 
> 0 Votes > 
> No votes> 
> 
> -1 Votes> 
> No votes> 
> 
> 
> Vote thread can be found here [1]. > 
> I will continue with the release process on general@ and the release 
> announcement will follow in the next few days.> 
> 
> Thanks,> 
> Piyush > 
> 
> 
> [1] 
> https://lists.apache.org/thread.html/618ad28580e838254f998deb71373467374a05228401dae0323a6d0f@%3Cdev.mxnet.apache.org%3E
>  
> >
>  

[RESULTS][VOTE] Release Apache MXNet (incubating) version 1.4.0.rc3

[Piyush Ghai]

Dear MXNet community,

I’m happy to announce the results of the vote. 

This vote passes with 4 +1 votes (3 binding) and no 0 or -1 votes.

+1 votes
Carin / binding
Qing / binding
Roshani / binding
Yuxi Hu

0 Votes 
No votes

-1 Votes
No votes


Vote thread can be found here [1]. 
I will continue with the release process on general@ and the release 
announcement will follow in the next few days.

Thanks,
Piyush 


[1] 
https://lists.apache.org/thread.html/618ad28580e838254f998deb71373467374a05228401dae0323a6d0f@%3Cdev.mxnet.apache.org%3E
 

Re: Rust Client Lib

[Pedro Larroy]

Relevant to this conversation about Rust / Swift bindings, is this
recent interview with Yann LeCun which I think hits the nail in the
head:   
https://venturebeat.com/2019/02/18/facebooks-chief-ai-scientist-deep-learning-may-need-a-new-programming-language/amp/

The questions are, do people / science community really want something
different than Python?  If so what language would it be?   Rust would
be good for production but for experimentation the most likely
candidate is a language like Swift or Julia.

Pedro.

On Tue, Feb 19, 2019 at 5:53 AM Sheng Zha  wrote:
>
> Hi,
>
> Thanks for sharing the results. A problem in the benchmark is that the 
> comparison does not take into account that MXNet is making a copy while 
> pytorch is not.
>
> MXNet made the choice of not doing a zero-copy for numpy arrays, but instead 
> making a copy of the numpy data. This means that users are free to change the 
> numpy array after passing it into MXNet. On the other hand, PyTorch chose not 
> to make a copy, by keeping the array alive through incrementing the reference 
> count and then reuse the data pointer.
>
> This also explains why pytorch fp16 is this much worse than fp32 in your 
> results (`.half()` has to make a copy).
>
> If you control for that factor, you will find MXNet to be 50%-100% faster on 
> your workload. I shared the results in your gist comments [1]. Feel free to 
> let me know if you have questions.
>
> -sz
>
> [1] 
> https://gist.github.com/SunDoge/59a8ff336703b45be30b46dc3ee8b4ab#gistcomment-2841120
>
> On 2019/02/19 02:33:20, epsund...@gmail.com  wrote:
> > I wrote some benchmark code, and here's the discussion:
> > https://discuss.mxnet.io/t/hybrid-training-speed-is-20-slower-than-pytorch/2731/3
> >
> > There's another discussion here:
> > https://discuss.mxnet.io/t/performance-of-symbol-vs-ndarray-vs-pytorch/870/6
> >
> > I slightly modify it:
> > https://gist.github.com/SunDoge/59a8ff336703b45be30b46dc3ee8b4ab
> >
> >
> > On 2019/02/18 19:26:27, Edison Gustavo Muenz  
> > wrote:
> > > Hello!
> > >
> > > > mxnet is somehow slower than pytorch, even with hybridize on, and that's
> > > why I start writing binding for pytorch now.
> > >
> > > I believe many people in this list will be very interested in why you say
> > > this.
> > >
> > > As far as I know, and correct me if I'm wrong, MXNet is supposed to be a
> > > very fast, if not the fastest, dl framework. I mean in raw performance
> > > numbers.
> > >
> > > Would you mind expanding on what you mean? I'm genuinely interested.
> > >
> > > Best,
> > > Edison Gustavo Muenz
> > >
> > > On Mon 18. Feb 2019 at 17:28, epsund...@gmail.com 
> > > wrote:
> > >
> > > > The rust crate for tensorflow support only inference, which limit its
> > > > usage. If you really want to deploy your network, TensorRT and TVM may 
> > > > be
> > > > better choice.
> > > >
> > > > I really want to write a dl framework in rust from scratch. However,
> > > > there's no mature GPU Tensor library in rust (rust-ndarray is a great 
> > > > crate
> > > > but it only support CPU. arrayfire may support ND array in the future,
> > > > which is a good candidate). So I have to write bindings for existing
> > > > project, which is much easier. .The benefit is that I can safely wrap 
> > > > those
> > > > unsafe C pointer, and with the help of generic, I can manipulate data 
> > > > with
> > > > ndarray in a type-safe way.
> > > >
> > > > The only difficulty is that I'm a postgraduate and I'm pretty sure my 
> > > > boss
> > > > won't be happy to see me writing rust code instead of doing research.
> > > > Besides, mxnet is somehow slower than pytorch, even with hybridize on, 
> > > > and
> > > > that's why I start writing binding for pytorch now.
> > > >
> > > > On 2019/02/09 01:35:04, Zach Boldyga  wrote:
> > > > > I did some homework and stumbled across something that changed my 
> > > > > view of
> > > > > where machine learning libraries are headed:
> > > > >
> > > > >
> > > > https://github.com/tensorflow/swift/blob/master/docs/WhySwiftForTensorFlow.md
> > > > >
> > > > > Google & Apple are building first-class support for Tensorflow right 
> > > > > into
> > > > > the Swift language. They chose Swift very carefully, and while they 
> > > > > noted
> > > > > Rust is a great choice for lots of reasons, the learning curve of the
> > > > > language is too steep... It seems like Rust isn't going to get much 
> > > > > love
> > > > > from the ML community in the places that matter.
> > > > >
> > > > > I also see that as of writing this, the Rust crate for Tensorflow has
> > > > only
> > > > > ~10,000 lifetime downloads, which is pretty low considering how much
> > > > effort
> > > > > the client library required. So the existing set of practitioners in 
> > > > > the
> > > > > language is very small, and it's unlikely to grow.
> > > > >
> > > > > Also, the benefits of Rust memory safety and ownership won't really be
> > > > > realized via a client library that uses FFI on a C 

答复: [Announcement] New Committer - Kan Wu (@wkcn)

[MiraiWK WKCN]

I am happy and honored to be a MXNet committer.

It's a pleasure to cooperate with you, and contribute to MXNet together.

Thanks,
Kan Wu



发件人: Zhao, Patric 
发送时间: 2019年2月19日 14:24
收件人: dev@mxnet.incubator.apache.org; d...@mxnet.apache.org
抄送: Anirudh Subramanian; Jackie Wu
主题: RE: [Announcement] New Committer - Kan Wu (@wkcn)

Congratulation!

We have the cooperation with Kan before and he is easy to communicate and very 
professional :)

It's really deserved!

> -Original Message-
> From: Lv, Tao A [mailto:tao.a...@intel.com]
> Sent: Tuesday, February 19, 2019 2:17 PM
> To: dev@mxnet.incubator.apache.org; d...@mxnet.apache.org
> Cc: Anirudh Subramanian ; Jackie Wu
> 
> Subject: RE: [Announcement] New Committer - Kan Wu (@wkcn)
>
> Congratulations Kan! You're well deserved!
>
> -Original Message-
> From: Sheng Zha [mailto:szha@gmail.com]
> Sent: Tuesday, February 19, 2019 2:10 PM
> To: dev@mxnet.incubator.apache.org; d...@mxnet.apache.org
> Cc: Anirudh Subramanian ; Jackie Wu
> 
> Subject: [Announcement] New Committer - Kan Wu (@wkcn)
>
> Hi,
>
> Please join me in welcoming Kan Wu (@wkcn), as a new committer!
>
> Kan has brought many valuable contributions to MXNet [1]. He also enriches
> the MXNet ecosystem with his operator toolkit MobulaOP.
>
> We are excited to have Kan join us as a committer.
>
> -sz
>
> [1]
> https://github.com/apache/incubator-
> mxnet/pulls?utf8=%E2%9C%93=is%3Apr+author%3Awkcn+
> [2] https://github.com/wkcn/MobulaOP