Re: Discussing plans for next MXNet releases

Hi Hagay, Thanks for taking the initiative. The proposed scope in this thread is in my opinion too large to fit in a single thread, so I'd suggest that we start separate threads for each individual release item. To elaborate on the reasons based on each individual item: - For 1.4.1 which is in the

Re: Discussing plans for next MXNet releases

Great initiative. I would like to add the issue that tracks APIs that we would like to break for 2.0 so we can take the chance to streamline and improve customer facing code: https://github.com/apache/incubator-mxnet/issues/9686 I would be happy to volunteer for 2.0 release with assistance from

Re: Discussing plans for next MXNet releases

Release breakdown makes sense to me Hagay. Thanks for initiating a discussion. Some features that I'm personally looking forward to that I hope can make it into 1.5 (schedule permitting): * TensorRT being integrated with the subgraph API * VNNI MKLDNN support * AMP training in MXNet I like th

Re: Podling Report Reminder - April 2019

Thanks for the reminder. I’m working on it and will post the draft back to the list, and would appreciate feedback from the community by then. -sz > On Apr 2, 2019, at 5:23 PM, Tianqi Chen wrote: > > It would be great if the PPMC coordinate and prepare the report > >> On Tue, Apr 2, 2019 at 4

Re: Podling Report Reminder - April 2019

It would be great if the PPMC coordinate and prepare the report On Tue, Apr 2, 2019 at 4:00 PM Hagay Lupesko wrote: > Is anyone working on the podling report? > I'm happy to take care of that if no one else is planning to do it. > > Cheers, > Hagay > > On Fri, Mar 29, 2019 at 4:06 PM wrote: > >

Discussing plans for next MXNet releases

Dear MXNet community, I wanted to initiate a discussion about the plan and scope for the next MXNet releases. I suggest we focus on three releases, and get the process going in parallel: (1) 1.4.1 - patch release on top of 1.4.0 to address some perf regressions and memory leaks I am aware of, such

Re: Podling Report Reminder - April 2019

Is anyone working on the podling report? I'm happy to take care of that if no one else is planning to do it. Cheers, Hagay On Fri, Mar 29, 2019 at 4:06 PM wrote: > Dear podling, > > This email was sent by an automated system on behalf of the Apache > Incubator PMC. It is an initial reminder to

Reminder: MXNet Berlin User Group

Hello Dev, This is a friendly reminder that MXNet Berlin User Group will be held today at 6pm-7pm (CEST) / 9am-10am (PST). More info here: https://cwiki.apache.org/confluence/display/MXNET/Apache+MXNet+%28Incubating%29+User+Groups+recurring+meetings You have been invited to an online meeting, pow

Re: [DISCUSS] Rebrand Gluon to MXNet imperative or something MXNet.

Hi, On Thu, 28 Mar 2019 at 22:08, Mu Li wrote: > The name Gluon is originally used for a collaboration project between > Amazon and Microsoft [1]. > I pinged both Apache and Amazon legal teams later, they confirmed Gluon is > not considered as a trademark. > > [1] > > https://aws.amazon.com/blo

Re: [Announcement] New Committer - Alex Zai

Thanks everyone. Looking forward to helping mxnet continue to grow. Best,Alex On Mon, Apr 1, 2019 1:38 AM, Lin Yuan apefor...@gmail.com wrote: Congrats, Alex! Hope your book is going well :) Lin On Sun, Mar 31, 2019 at 6:18 PM Zhao, Patric wrote: Congratulation, Alex. Thank you to your h