Re: [VOTE] Release Apache MXNet (incubating) version 1.7.0.rc0

-1 (binding). It breaks the YOLO training in GluonCV and the basic image classification in AutoGluon. There is an open PR that reverts the `weakref` fix: https://github.com/apache/incubator-mxnet/pull/18692 and we need to see whether to revert that fix or find some other ways to solve the

Re: [VOTE] Release Apache MXNet (incubating) version 1.7.0.rc0

Thanks Ziyi, I've discovered the same issue when I'm trying to use AutoGluon with 1.7.0rc0 and would like to share my finding: Basically, I don't think Gluon Block is designed to be pickleble. But pickling do work for some cases in the old version: I've included two cases in the gist

Re: MXNet 1.6 as last release with Python 2 support?

+1. We should move to support Python>=3.5 only. Get Outlook for iOS From: Lausen, Leonard Sent: Friday, January 17, 2020 10:02:30 AM To: d...@mxnet.apache.org Subject: Re: MXNet 1.6 as last release with Python 2 support? If the lazy

Re: [apache/incubator-mxnet] [RFC] Apache MXNet 2.0 Roadmap (#16167)

Should we create a new branch for 2.0? I think we are also planing for 1.7.0 https://github.com/apache/incubator-mxnet/issues/16864 -- You are receiving this because you were mentioned. Reply to this email directly or view it on GitHub:

Re: [Discuss] MXNet Python 3.6 Support Deprecation

I don’t think we should drop Python 3.5 now because Ubuntu 16.04 ships with that version. I suggest that we should revisit it next year. Best, Xingjian From: Sheng Zha Sent: Tuesday, August 27, 2019 10:49 AM To: d...@mxnet.apache.org Subject: Re: [Discuss] MXNet

Join slack channel

Re: Request for comments - Keras-MXNet as submodule in MXNet

ct: Re: Request for comments - Keras-MXNet as submodule in MXNet define - not mature? Are all new commits that go into MXNet mature ? On Fri, Mar 23, 2018 at 12:02 PM, Xingjian SHI <xsh...@connect.ust.hk> wrote: > -1. We do not need to get the eyeballs this way. Asking users to

Re: Request for comments - Keras-MXNet as submodule in MXNet

library which can be supported > by various different backend framework. It would be better to add backend > framework as Keras's submodule(Keras depends on MXNet) rather than > opposite. > > Best, > Yao > > 2018-03-23 11:44 GMT-07:00 Xingjian SHI <xsh...@connect.ust.hk>: &g

Re: Request for comments - Keras-MXNet as submodule in MXNet

-1. I think we should wait until it's merged into keras-team/keras. The repo is still not mature enough. Best, Xingjian From: sandeep krishnamurthy Sent: Friday, March 23, 2018 1:49 PM To: dev@mxnet.incubator.apache.org Subject:

Re: Cython Document iteration

Great! Also, what’s the current status of Cython support in MXNet? I think we have the option to use Cython, which is added by Tianqi. Best, Xingjian Get Outlook for iOS _ From: Chris Olivier Sent: Friday, March 9, 2018

Re: [RESULT][VOTE] tracking code changes with JIRA by associating pull requests

rts so that there is some sort of holistic view of the direction of the project rather than the way it is now, where PR's just appear out of nowhere. On Thu, Mar 8, 2018 at 11:38 AM, Xingjian SHI <xsh...@connect.ust.hk> wrote: > What's the expected workflow if we use JIRA? I'm not clear about th

Re: [RESULT][VOTE] tracking code changes with JIRA by associating pull requests

What's the expected workflow if we use JIRA? I'm not clear about that. Currently I'll 1) submit the PR, 2) describe what's done in the PR in detail and refer to the related Github issues, 3) create the JIRA item by copying the PR description, 4) change the title of the PR to

Re: [RESULT][VOTE] tracking code changes with JIRA by associating pull requests

We can also consider to give a special label for all the issues that are "working items". There are lots of efforts spent on assigning the correct label to Github issues. We can then easily select the issues we are interested in, e.g,

Re: [RESULT][VOTE] tracking code changes with JIRA by associating pull requests

There is no issue page in Spark (https://github.com/apache/spark) and they rely solely on JIRA to track the working items. This is different from what we are doing now. MXNet associate PRs to working items by linking them to the Github issues, e.g,

Re: [VOTE] Release MXNet version 1.1.0.RC1

+1 From: Chris Olivier Sent: Wednesday, February 14, 2018 1:52 AM To: dev@mxnet.incubator.apache.org Subject: Re: [VOTE] Release MXNet version 1.1.0.RC1 +1 (binding) On Tue, Feb 13, 2018 at 9:49 AM, YiZhi Liu wrote:

Re: Proposal for treating warnings as errors in Linux & Clang builds (-Werror)

It seems we have the `DEV` mode (https://github.com/apache/incubator-mxnet/blob/master/make/config.mk#L28) to do that? Is it correct? Xingjian From: Ziyue Huang Sent: Tuesday, January 16, 2018 9:01 AM To: dev@mxnet.incubator.apache.org