Re: [Announcement] New Committer - Zach Kimberg

Congratulations Zach - well deserved! On Thu, May 9, 2019, 13:26 Qing Lan wrote: > Hi All, > > Please join me in welcoming Zach Kimberg (https://github.com/zachgk) as a > new committer. > > He has been solving some important bugs in MXNet JVM with respect to usage > improvement, build issues and

Re: Fujitsu Breaks ImageNet Record using MXNet (under 75 sec)

Agreed! I will mention this to my colleagues at Amazon that can help with that. On Mon, Apr 8, 2019 at 1:32 PM Chaitanya Bapat wrote: > Yes. Moreover, we should be pushing it on our Twitter, Reddit, Medium, etc > social channels. > > On Mon, 8 Apr 2019 at 15:55, Hagay Lu

Re: MXNet 1.4.1 Release Proposal

wrote: > > > Hi Hagay, > > > > I have some experiences in MXNet development, and would love to volunteer > > for driving this release. > > > > Thank you so much! > > > > Best, > > Junru > > > > On Thu, Apr 4, 2019 at 1:51 PM Haga

Re: Fujitsu Breaks ImageNet Record using MXNet (under 75 sec)

That's super cool Chai - thanks for sharing! I also noticed that, and was seeing how we can reach out to the Fujitsu guys so they can contribute back into MXNet... On Mon, Apr 8, 2019 at 10:14 AM Lin Yuan wrote: > Chai, > > Thanks for sharing. This is awesome news! > > Lin > > On Mon, Apr 8, 201

MXNet 1.4.1 Release Proposal

Hello MXNet community, As previously discussed in [0 ], and per the feedback from Pedro, Kellen and Sheng, I'd like to propose releasing MXNet 1.4.1. MXNet 1.4.1 is a patch rel

Re: Discussing plans for next MXNet releases

0, I think it would be more of a roadmap discussion at this stage. > > I hope this makes sense. Would you mind starting a thread focusing on 1.4.1 > patch release? > > -sz > > > On Tue, Apr 2, 2019 at 5:06 PM Hagay Lupesko wrote: > > > Dear MXNet community, > &

Re: Requesting slack access

Hi Xiuquan, Slack invite sent - welcome to the MXNet community! Please slack me @Hagay Lupesko - would love to chat about how you guys are thinking about using MXNet. Hagay On Thu, Apr 4, 2019 at 1:24 AM Xiuquan Lv wrote: > Dear MXNet community, > > > > > Please join me

Re: Podling Report Reminder - April 2019

> wrote: > > > > 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 on

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

Re: [Announcement] New Committer - Patric Zhao

Congrats Patric! On Fri, Mar 15, 2019 at 7:49 AM Joshua Z. Zhang wrote: > > > > Congrats Patrick! > > > > > > Zhi > > > > > On Mar 15, 2019 at 10:46 PM, marco.g.ab...@gmail.com)> wrote: > > > > > > > > Congratulations, great to have you on board! > > > > -Marco > > > > Lv, Tao Aschrieb

Re: Gluon fit API- Design proposal

Wanted to chime in as well. I have reviewed the design shared in the mail offline with Ankit, Lai and Naveen (we work in the same team in Amazon). I think it does a good job at simplifying many low-complexity training use cases, which can make MXNet/Gluon even more friendly to so-called "deep lear

Re: [DISCUSS] Current Publish problems

Good stuff Zach and Qing! Great feedback Edison - would be great if you leave it in the wiki, so that it is saved in the context of the doc with other feedback, such as Kellen's. On Mon, Jan 28, 2019 at 1:58 AM edisongust...@gmail.com < edisongust...@gmail.com> wrote: > Hello all, > > First let m

Re: mxnet slack, contributor

Just sent you an invite! Or you can just follow this link: https://join.slack.com/t/the-asf/shared_invite/enQtNDQ3OTEwNzE1MDg5LWY2NjkwMTEzMGI2ZTI1NzUzMDk0MzJmMWM1NWVmODg0MzBjNjAxYzUwMjIwNDI3MjlhZWRjNmNhOTM5NmIxNDk Welcome! On Sun, Jan 27, 2019 at 10:26 PM Zach Boldyga wrote: > hello, I'm contr

Re: [Announcement] New Committer - Roshani Nagmote

Congrats and so much well deserved :) On Tue, Jan 8, 2019 at 9:20 AM Steffen Rochel wrote: > Congratulation Roshani! > > On Tue, Jan 8, 2019 at 8:53 AM Qing Lan wrote: > > > Congrats Roshani! Great to have you here! > > > > -Qing > > > > > > > > > > > Congrats Roshani. Well deserved. > > > > >

Re: Tensorflow contrib loss functions ported to mxnet

Istavan, This sounds useful to me, and would encourage you to contribute it. It's always helpful if you describe one or two use cases for the contribution (e.g. models/problems where these loss functions are useful) - this stimulates interest. Can you share the link to the PR that got zero attent

Re: [Annoucement] New Committer -- Iblis Lin

Congrats Iblis! On Sat, Jan 5, 2019 at 2:35 PM Steffen Rochel wrote: > Congratulation Ilbis! > > On Sat, Jan 5, 2019 at 1:45 PM Lin Yuan wrote: > > > Welcome Iblis, > > > > Great to see a good Julia support in MXNet! > > > > Lin > > > > On Sat, Jan 5, 2019 at 12:32 PM Marco de Abreu > > wrote:

Re: [Annoucement] New Committer -- Da Zheng

Congrats Da! On Mon, Dec 17, 2018 at 5:44 PM Marco de Abreu wrote: > Welcome Da, great to have you on board! > > Am Di., 18. Dez. 2018, 02:35 hat Lv, Tao A > geschrieben: > > > Congrats Da! Thank you for the effort on bringing MKL-DNN to MXNet. It's > > really the footstone for the latter work

Re: Cambricon MLU support for MXNet.

Welcome to the MXNet community Haochong! It's exciting to learn about your plans to contribute to MXNet! I highly recommend that you document your proposal and technical design in MXNet's design proposals wiki [1 ], where you can

Re: [Announcement] New Committer -- Rahul Huilgol

+1 - congrats Rahul! On Mon, Dec 3, 2018 at 8:09 PM kellen sunderland < kellen.sunderl...@gmail.com> wrote: > Congrats Rahul, well deserved. > > On Mon, Dec 3, 2018 at 6:24 PM Tianqi Chen wrote: > > > Let us welcome Rahul Huilgol as a new Committer of MXNet. He has > > contributed to many fronts

Re: [Announcement] New Committer -- Aaron Markham

Congrats Aaron! Your work on the docs definitely set a new standard and helps the community tremendously - well deserved! On Mon, Dec 3, 2018 at 6:22 PM Tianqi Chen wrote: > Let us welcome Aron Markham as a new committer of MXNet. Aaron has been > actively working on improving documents and web

Re: CI impaired

Thanks for the update Marco and all the hard work put into the CI! On Sat, Dec 1, 2018 at 1:21 PM Marco de Abreu wrote: > Hello everyone, > > the move has just been completed and the old big pipeline as well as the > according job have been disabled. From now on, you will see the details > statu

Re: Apache Infra tickets for MXNet

LGTM. Thanks Marco for clarifying and documenting this - very helpful! Hagay On Sun, Dec 2, 2018 at 6:19 PM Marco de Abreu wrote: > Hello Steffen, > > great suggestion! I have added a section to the wiki page. > > Best regards, > Marco > > On Sat, Dec 1, 2018 at 10:49 PM Steffen Rochel > wrote

Re: Include MKLDNN into default mxnet pip package

> release > > > >>>> period of MKL-DNN and MXNet are not matched very well. I think > > > >>>> it would > > > >>> be > > > >>>> a risk for MXNet release if it hardly depends on the release of > > > >>>> a submodule, n

Re: Updating MXNet's Cub

here will be a dangling untracked > folder "cub" in local disk. Developer can delete it manually. > > Thanks, > Frank > > > On 2018/08/24 17:00:54, Hagay Lupesko wrote: > > Hi all, > > > > > > One of MXNet’s submodule dependencies is a snap

Re: Requesting Slack Access

Invite sent. Welcome Sam! On Fri, Nov 23, 2018 at 11:38 PM Sam Bean wrote: > -- > Sam Bean > *StockX* > *Tech Lead, Machine Learning and Personalization* > *––* > samb...@stockx.com > stockx.com >

Re: [ANNOUNCEMENT] New Committer: Qing Lan

Congrats Qing! Awesome to see you become a committer! On Tue, Nov 20, 2018 at 4:26 PM Marco de Abreu wrote: > Great to have your on board, Qing! > > Am Mi., 21. Nov. 2018, 01:24 hat Naveen Swamy > geschrieben: > > > The Project Podling Management Committee (PPMC) for Apache MXNet has > > invite

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

Great - congrats! On Tue, Nov 20, 2018 at 8:51 AM Anton Chernov wrote: > Dear MXNet community, > > I'm happy to announce the results of the vote. > > This vote passes with 8 +1 votes (4 binding) and no 0 or -1 votes. > > +1 votes > > * Carin / binding > * Indhu / binding > * Sandeep / binding >

Re: [Announce] Upcoming Apache MXNet (incubating) 1.4.0 release

+1 to wait until Java API work is ready since it is a major feature of the release, yet performance should be at least on par with Python. Also, I consider the MKL-DNN feature to be another major feature of the release, the performance boost on CPU is significant [1], as an example, ResNet50-v1 is

Re: LabelBot New Design in Production

Thanks for this useful contribution Harsh! +1 to an updated issue template and +1 to Marco's idea as well Anything that helps the community triage and make it easier for folks that file issues is greatly appreciated Hagay On Thu, Nov 8, 2018 at 4:05 PM Marco de Abreu wrote: > Great job, Harsh!

Re: MKLDNN dynamically linked

+1 Kellen made a good call about watching out for the license. Not an issue for MKL-DNN though, which I believe has an Apache 2 license. On Thu, Nov 8, 2018 at 3:51 PM Zhao, Patric wrote: > +1 for static link :) > > Feel free to let us know if anything we can help. > > > -Original Message---

Re: Requesting access for SLACK

Invite sent Gaurav! On Wed, Nov 7, 2018 at 1:33 PM Gaurav Gireesh wrote: > Hi! > I would like to request access to the Slack channel for MXNet. > > Thanks and regards, > Gaurav Gireesh >

Re: Apache MXNet Workshop in ODSC

This is awesome Naveen and Sandeep! +1 to encourage the community to spread the word and raise awareness of MXNet. On a similar note, I recently had the opportunity to introduce MXNet in two occasions: - Conducting an MXNet workshop in the Nordics ML Summit conference

Re: Include MKLDNN into default mxnet pip package

Awesome collaborative effort across many contributors and companies! The boost is impressive and for MXNet users to get this boost "out of the box" is a great benefit and makes MXNet an even better choice. Alex - can you clarify whether there are any down sides with regards to noon AVX-512 archit

Re: [LAZY VOTE]: rename dockerfiles s/.build.//

The PR provides a good explanation of this change and all code updates. LGTM. On Tue, Oct 16, 2018 at 8:41 AM Pedro Larroy wrote: > Hi > > I would like to rename the dockerfiles since they are used as a runtime > environment and not only as build as they were initially intended. > > More info ab

Re: MXNet - Label Bot functionality

+1 Thanks for the contribution! On Fri, Oct 12, 2018 at 1:41 AM kellen sunderland < kellen.sunderl...@gmail.com> wrote: > Awesome work! Many thanks. > > On Fri, Oct 12, 2018, 1:19 AM Harsh Patel > wrote: > > > Hey, > > I am looking to contribute to MXNet. I have a working implementation > based

Re: Request to join the Slack channel

Invite sent! On Tue, Sep 25, 2018 at 10:29 PM Vikas Kumar wrote: > Please send me an invite to join. > > Thanks > Vikas >

Re: multiple installation guides?

The /test site seems to be something old that should have been removed a long time ago, it lists versions 0.10 and 0.10.14 :) Maybe Aaron has an idea what needs to be done to remove it... On Fri, Sep 14, 2018 at 4:55 PM Alex Zai wrote: > Why do we have two sets of installation guides? > > http:/

Re: Questions regarding C Predict and C++ API provided by MxNet.

Amol, I can try and provide my 2 cents on some of these questions: - "What are the typical uses cases in which C++ (cpp-package) or C (C Predict) APIs are used? For example: inference, training or both." Note that the C API supports inference only. >From my experience as an Amazon Web Services emp

Re: [DISCUSS] Build OSX builds in CI (possibly with TravisCI).

Bravo indeed! Awesome work Kellen and Marco! On Tue, Sep 18, 2018 at 7:56 PM Lin Yuan wrote: > Bravo! This is a very important piece in CI. Thanks Kellen and Marco to > implement it quickly. > > > Lin > > On Tue, Sep 18, 2018, 4:18 PM Marco de Abreu > wrote: > > > Kellen has fixed the one bug i

Re: [VOTE] Release MXNet version 1.3.0.RC0

soning > besides "X mentions the issue" or "fix was done by X". Thanks. > > -sz > > [1] > > https://lists.apache.org/thread.html/d1ed611f98c20d5d85c294b0c07c8bdebca13a209cf66a3872c9123e@%3Cdev.mxnet.apache.org%3E > > On Tue, Sep 4, 2018 at 12:39 PM Hagay Lupesko wrote: > > > San

Re: [VOTE] Release MXNet version 1.3.0.RC0

Sandeep mentions the issue of an error when user tries to load model params trained/saved as FP16. https://github.com/apache/incubator-mxnet/issues/11849 The fix was done by Sandeep: https://github.com/apache/incubator-mxnet/pull/12412 and is ready to be cherry picked into the release branch. This

Re: Propose to discontinue supporting Apache MXNet on Windows 7

+1 (non-binding) Thanks for raising this Lin! Are you suggesting to do it as part of MXNet 1.3? On Wed, Aug 29, 2018 at 9:14 AM Srivastava, Rohit Kumar < srivastava@buckeyemail.osu.edu> wrote: > +1 > > On 8/29/18, 8:39 AM, "sandeep krishnamurthy" > wrote: > > +1 Thanks for bringing this

Re: Updating MXNet's Cub

Thanks for the feedback Chris. Will follow up. On Fri, Aug 24, 2018 at 10:53 AM Chris Olivier wrote: > +1 for pointing to NVidia's repo for the newer Cub and subsequent versions. > > On Fri, Aug 24, 2018 at 10:01 AM Hagay Lupesko wrote: > > > Hi all, > > >

Re: clang-tidy and static code analysis

I really like this proposal. It will help improve the quality of MXNet native code, and maintain a uniform high bar. An extra 5 mins of build time seems reasonable. +1 On Sat, Aug 25, 2018, 07:02 kellen sunderland wrote: > Hello all, > > Inspired by Vanadana, cclaus and the project members who

Updating MXNet's Cub

Hi all, One of MXNet’s submodule dependencies is a snapshot of Nvidia Cub ( https://github.com/dmlc/cub) – the snapshot is of an older version of Cub (1.7), while the latest Nvidia Cub release is 1.8. Note that dmlc/cub has no customizations of the source Cub repo. I’d like to suggest to updat

Re: social media promotion / menu

Thanks for your contribution Aaron! I reviewed your PR, and like the new layout, left a few comments. Note that the preview link you shared doesn't render the social widget anymore (it used to) - please look into it. Thanks! Hagay On Thu, Aug 9, 2018 at 11:50 AM Aaron Markham wrote: > Hi dev,

Re: New committer and PMC member: Carin Meier

Congrats Carin! On Fri, Aug 10, 2018 at 10:23 AM Carin Meier wrote: > Thank you. I'm excited to get more involved and help MXNet grow :) > > On Fri, Aug 10, 2018 at 12:40 PM Marco de Abreu > wrote: > > > Dear MXNet community, > > > > the Project Management Committee (PMC) for Apache MXNet (incu

Re: Release plan - MXNET 1.3

Some thoughts: why not keep it out of 1.3, and merge it into master so it can go out with 1.4 instead? Pros: - Reduce quality risks for 1.3 - More time to test and get feedback before release - Avoid further delays in 1.3 release (lots of good stuff there already for users) Cons: - People will need

Re: Release blocker: non-determinstic forward in gluon

u > point out, is more desirable. > There's a huge amount of non-trivial work that has gone into building these > distribution packages from Sheng which needs to be adapted for our CI > system, and taken into consideration. > > Pedro. > > > On Mon, Jul 30, 2018 at 9:07 A

Re: Release blocker: non-determinstic forward in gluon

Thanks Tong for root-causing the issue! Thanks Sheng for following up with an updated PyPi package. What worries me is that we seem to build MXNet PyPi distribution packages with a build config different than the CI where all of the tests are running. Looking here [1

Re: Pylint Undefined variable/name error

+1 - thanks Vandana! On Thu, Jul 26, 2018 at 8:05 PM sandeep krishnamurthy < sandeep.krishn...@gmail.com> wrote: > Thanks Vandana for picking up this issue. I think this is important to be > fixed and enabled in CI. Please let us know effort required to fix these > issues and we all can jump in a

Re: MXNet Meetup in San Francisco - Aug 1 2018

No, unfortunately we're not planning to stream or record the meetup (equipment/budget) On Fri, Jul 20, 2018 at 9:36 AM Ivan Serdyuk wrote: > Are you providing streaming or recording? > > On Fri, Jul 20, 2018 at 7:27 PM, Hagay Lupesko wrote: > > > Hey folks, > > >

MXNet Meetup in San Francisco - Aug 1 2018

Hey folks, Sandeep and me are hosting a meetup in San Francisco Wednesday Aug 1 2018 on "Emotion recognition in images: from idea to production". The details are here: https://www.meetup.com/deep-learning-with-mxnet/events/252916863/ - note that there is limited capacity, so if you are interested

Re: Request slack access

Invited. On Sun, Jul 15, 2018 at 6:07 PM Sun, Tao wrote: > Can you please grant access for me? > > > Best regards, > > Tao Sun >

Re: FW: Success at Apache: The Apache Way for Executives

Could not agree more Yasser - thanks for sharing! On Tue, Jul 10, 2018 at 11:04 AM Tianqi Chen wrote: > Totally agree with what being said here, as community strives to move > forward it is important to be inclusive and communicative. The same > principle also applies beyond this mail-list, as

Re: C++ api issue labeling

"Feature > > > Request" ( > > > https://github.com/apache/incubator-mxnet/labels/Feature%20request ). > I > > > don't think there is much difference between these two labels. > > > > > > It would make sense to merge the "Feature" lab

Re: Adding section on how to develop with MXNet to the website

you can edit more freely and have comments versus the mxnet.io > site which is more for users and static content. > > > On 7/2/18, 2:03 PM, "Hagay Lupesko" wrote: > > Now I understand Pedro. Agree with Naveen this would be helpful. > > On Sun, Jul 1, 2018 a

Re: Adding section on how to develop with MXNet to the website

> > On Jul 1, 2018, at 12:07 AM, Pedro Larroy > wrote: > > > > Hi Hagay > > > > Meaning how to set the developer environment like CLion to debug MXNet, > how > > to build and run tests etc. Or is this already documented? > > > > Pedr

Re: MXNet 1.3 release - call for volunteers

shani > > On Wed, Jun 27, 2018 at 5:52 PM Hagay Lupesko wrote: > > > Hello community! > > > > I'd like to kickstart the process for MXNet v1.3 release - and ask for a > > volunteer to take on this release as a release manager. I am hoping the > >

Re: Merging Clojure PR

Thanks for your contribution Carin! Unfortunately i can't do a proper review for Clojure, but it's great to see the contribution and see how it develops and grows... On Thu, Jun 28, 2018 at 11:11 AM Carin Meier wrote: > Thanks everyone for your feedback and efforts with the Clojure package PR. >

MXNet 1.3 release - call for volunteers

Hello community! I'd like to kickstart the process for MXNet v1.3 release - and ask for a volunteer to take on this release as a release manager. I am hoping the release process can start next week or so. The release scope is documented here: [1

Re: C++ api issue labeling

Thank you everyone for your suggestions. I will work with a committer to get this updated ASAP. On Mon, Jun 25, 2018 at 8:55 AM Marco de Abreu wrote: > +1 to renaming to Backend > > On Mon, Jun 25, 2018 at 10:13 AM Hagay Lupesko wrote: > > > Thanks Lin for your feedback. &g

Re: Adding section on how to develop with MXNet to the website

Pedro, Anything that helps bring in more contributors is good IMO. But can you please clarify what you mean by "develop MXNet itself"? Hagay On Mon, Jun 25, 2018, 19:33 Markham, Aaron wrote: > More or less... Instructions are in the readme in the docs folder. Focus > on the developer sections.

Re: C++ api issue labeling

tation, "Backend" > better describes the nature of the work (let's assume we change the backend > implementation from C++ to other languages in the future). > > Lin > > On Fri, Jun 22, 2018 at 1:09 AM Hagay Lupesko wrote: > > > Thanks everyone for

Re: C++ api issue labeling

t; things. > > The C++ label refers to the issue for MXNet backend and the CPP package > > refers to the CPP language binding for mxnet. > > We can still make C++ API great again irrespective by filtering out CPP > > package issues :). > > > > Anirudh > > > &g

C++ api issue labeling

Hey community, I was going over the open GitHub issues for MXNet, and noticed that we have two labels for the CPP API: "CPP package", "C++" Wanted to suggest we remove "CPP package" and just stick to "C++" This will make it easier for the community to classify issues and focus on making the C++ A

Re: users@mxnet

Jim, Earlier on the thread you suggested to clarify and expand on the usage of a user@ mailing list and how it is useful for a project. It may be helpful for the community to learn a bit more about it. Could you expand and/or share relevant links and examples? Thank you, Hagay On Tue, Jun 19, 2

Re: Additional mentor to MXNet - Jim Jagielski

That is great news! Welcome on board Jim! On Mon, Jun 18, 2018, 15:14 Naveen Swamy wrote: > Hi All, > > I am excited to announce that we have an additional mentor for MXNet: Jim > Jagielski, the cofounder of Apache, he brings vast experience in building > and growing successful communities arou

Re: Clojure Package

Carin, Thanks for contributing so much to MXNet! I just went through the planned MXNet v1.3 release scope [1], and did not see the Clojure package. I think it would be a great addition to MXNet, and initially can be marked as experimental. Did you consider adding it to MXNet 1.3 as an experimenta

Re: Request for Sign up

Kalyanee, Welcome to MXNet community :) Instructions to subscribe to the dev list here: https://mxnet.incubator.apache.org/community/contribute.html#dev-mailing-list Hagay On Fri, Jun 15, 2018 at 4:36 PM Aaron Markham wrote: > Hi, > Have you checked out this page? > https://mxnet.incubator.ap

Re: users@mxnet

Agree with Indu's points: email list usability and features seems inferior compared to the discussion forum, so I would suggest to keep things simple and stick with the forum. Hagay On Sat, Jun 16, 2018, 06:37 Timur Shenkao wrote: > user mail list > > Pros: > - Apache user mail list is indexed

Re: Details regarding upcoming PR for runtime TensorRT integration

+1 for reviewing a design doc. Naveen - why do you see it sit under ONNX? Isn't it a broader topic of GPU acceleration? Hagay On Mon, Jun 11, 2018, 12:56 Naveen Swamy wrote: > please add your proposal under design proposals, once the community has > reviewed and there is consensus on the appro

Re: Github link on MXNet Homepage

+1 for adding the ribbon: - developers are used to it - the upper bar is crowded, especially on mobile On Thu, Jun 7, 2018, 12:35 Xie, Junyuan wrote: > People usually use a ribbon at the top right conner for github link. Like > this https://pytorch.org/ > > On 6/7/18, 12:33 PM, "singh.rajan28@"

Re: Scala Packages in Maven

+1 for a CD for publishing to Maven +1 for reducing the number of packages. Do we really need more than full, infer and spark (x3 platforms)? On Mon, May 21, 2018 at 5:47 PM, Naveen Swamy wrote: > not at the moment, certainly is in my radar. Apache release requires a > committer's LDAP username/

Re: Proposal of MxNet-to-ONNX exporter

Marek, Can you add more details on your proposal? (Implementation details, operator coverage, test coverage planned) I am aware of similar work done by other contributors (Roshani, Rajan and Anirudh) - how is this going to align? Should you guys work together? Hagay On Mon, May 21, 2018, 11:17

Re: Parallel Inference Proposal

Good suggestion Kellen! I like the idea, it will solve an existing deficiency in MXNet, that has been worked around so far. As an example, the recently added Scala inference API (part of 1.2RC) implemented a dispatcher in Scala to workaround that limitation. Would be great to better understand th

Re: MXNet: Run PR builds on Apache Jenkins only after the commit is reviewed

Build success or failure is a great feedback mechanism, of equal importance to code review. Do we really want to delay it until another Dev gives a thumbs up? It feels like a step backwards from automation. If our problem is resource constraint, can't we address it by throwing more instances into

Re: Apache MXNet build failures are mostly valid - verify before merge

Build stability is a major issue, builds have been failing left and right over the last week. Some of it is due to Jenkins slave issues, but some are real regressions. We need to be more strict in the code we're committing. I propose we configure our master to be a protected branch ( https://help.