Re: Extend MXNET distributed training with MPI AllReduce

Hi, Patric It's pretty nice work! A question: how the future code structure would look like when putting this allreduce module as an submodule? We will have two communication submodules? Is there any plan to give an unified abstraction for communication so that a single communication submodule

Re: [VOTE] Change Scala namespace from dmlc to org.apache

> would be to either (1) provide a fascade from the new package to the > old > package or (2) keep two copies of the scala code temporarily along > with two > copies of the JNI entry points. In both of these cases we could setup > @deprecated on all public call

Re: [VOTE] Change Scala namespace from dmlc to org.apache

re Chris: I do not have any good idea about this. On Tue, Mar 13, 2018 at 8:13 AM, Chris Olivier <cjolivie...@gmail.com> wrote: > is it possible to somehow alias a namespace in scala > in order to maintain backwards compatibility? > > On Tue, Mar 13, 2018 at 7:21 AM

Re: [VOTE] Change Scala namespace from dmlc to org.apache

> > modification technical vote. > > > > > >> > > > > > > > > >> > > > > > > > > >> > > > On Mon, Mar 12, 2018 at 9:56 AM, Marco de Abreu < > > > > > >> > > > marc

Re: [VOTE] Disconnect all non-C API's from mxnet versioning

; >> in > > >> > > time, > > >> > > >> but our users would be losing trust due to unexpected failures > > >> during > > >> > > >> upgrades. > > >> > > >> > > >> > > >> -M

Re: [VOTE] Disconnect all non-C API's from mxnet versioning

how about release cycle? On Mon, Mar 12, 2018 at 9:37 AM, Yuan Tang wrote: > +1 > > On Mon, Mar 12, 2018 at 12:35 PM, Marco de Abreu < > marco.g.ab...@googlemail.com> wrote: > > > +1 > > > > Tianqi Chen schrieb am Mo., 12. März 2018, > >

Re: [VOTE] Change Scala namespace from dmlc to org.apache

I think we'd specify it will change in the next version (1.2)? On Mon, Mar 12, 2018 at 9:26 AM, Chris Olivier wrote: > This vote is for the code-change of altering the Scala API namespace from > dmlc to org.apache. > > > Vote will conclude on Thursday, 5pm PDT. > > Thank

Re: Publishing Scala Package/namespace change

I think last time we postpone it because the release is a minor version but actually such a change is actually affordable for a jump from 1.1 - 1.2 -1 on separate versions (not following apache rules) On Fri, Mar 9, 2018 at 2:38 PM, Chris Olivier wrote: > IMHO, I don't

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

l.com> wrote: > > >> > > >> The PR template is designed for that and its poor adoption is causing > > the > > >> same issue of missing information in PRs. My concern of using JIRA is > > that > > >> more overhead would deter contribution

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

+1 on both suggestions a bit concern is on the quality of JIRA which is created automatically I can see a lot of PRs are not described comprehensively, if we just post what in description to JIRA, it's error-propagating but the quality of JIRA is a big topic worth more discussions On Thu,

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

I think the right approach here is to start another vote on terminate the starting process of using JIRA, since we have passed this vote On Tue, Mar 6, 2018 at 9:13 PM, Eric Xie wrote: > -1 > > JIRA is ancient and arcane. This adds unnecessary overhead. > > On 2018/03/03

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

gt; Agreed. I feel its unnecessary too - let's leave the [MODULE] out. > > > > > -Marco > > > > On Tue, Feb 27, 2018 at 11:34 PM, Yuan Tang <terrytangy...@gmail.com> > > wrote: > > > > > +1 > > > > > > On Tue, Feb 27,

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

Marthi <smar...@apache.org> wrote: > On Tue, Feb 27, 2018 at 10:50 PM, Nan Zhu <zhunanmcg...@gmail.com> wrote: > > > Thanks, Suneel! > > > > the vote still remains sense on its major points > > > > " > > 1. most of PRs should be titled

Re: [VOTE] Release MXNet version 1.1.0.RC1

tested with scala-package's building and unit test +1 On Sat, Feb 10, 2018 at 10:49 AM, YiZhi Liu wrote: > Let's make the voting end at 11:10 p.m., Tuesday, February. 13th. > > Thanks for reminding. > > Best, > Yizhi > > 2018-02-10 9:54 GMT-08:00 Marco de Abreu

Re: [VOTE] When in Doubt, Wait 24 Hours Before Merging

+1, but do not understand why we merged PRs which was not completely approved? On Thu, Feb 1, 2018 at 4:20 PM, Sheng Zha wrote: > Hi, > > In order to avoid having miscommunication and unaligned expectation, I'd > like to propose a lazy vote on a new rule for merging pull

Re: Release plan - MXNET 1.0.1

ch and build from there. Happy to > help with this if needed. > > On Thu, Jan 25, 2018 at 6:19 AM, Nan Zhu <zhunanmcg...@gmail.com> wrote: > > > +1 and suggest consolidating all maintenance releases under the same > > major.minor version into a single branch > >

Re: Release plan - MXNET 1.0.1

+1 and suggest consolidating all maintenance releases under the same major.minor version into a single branch On Wed, Jan 24, 2018 at 9:06 PM, Meghna Baijal wrote: > I agree. If the release candidate is being cut from the master branch, it > should be considered a

Re: Request For comments: MXNet Scala Inference API

google.com/document/d/13EVnCtQ5d0wCnHWTsZT0jNzHdQfv2 > PR9AnX1YNlOhm0/edit?usp=sharing. > You can leave your comments there and I will move the final version of the > document again to the wiki. > > Thanks, Naveen > > > On Mon, Jan 22, 2018 at 6:48 PM, Nan Zhu <zhunanmcg...@gma

Re: Increase indentation limit from 100 to 120 characters

are doing something special BTW, considering monitor-relevant concern, http://scalameta.org/scalafmt/ tells that 100 is good enough even for a 30'' wide monitor On Fri, Jan 5, 2018 at 11:10 AM, Chris Olivier <cjolivie...@gmail.com> wrote: > Why -1? > > On Fri, Jan 5, 2018 at 11

Re: Increase indentation limit from 100 to 120 characters

-1 for scala part On Fri, Jan 5, 2018 at 9:48 AM, Marco de Abreu wrote: > +1 > > Am 05.01.2018 5:49 nachm. schrieb "Chris Olivier" : > > +1 > > On Fri, Jan 5, 2018 at 8:00 AM, Pedro Larroy > > wrote: > > > Hi

Re: Refactoring MXNet scala code to use "org.apache.mxnet"

anywhere to mark it as a breaking change in the latest version? On Thu, Jan 4, 2018 at 2:16 PM, Roshani Nagmote wrote: > Hello all, > > I am working on publishing mxnet-scala release to maven repository and as a > part of that, I will also be refactoring mxnet-scala

Re: request for reviewing PR in ps-lite

; > > On Sat, Dec 2, 2017 at 10:04 AM, CodingCat <coding...@apache.org> > wrote: > > > > > > > ping > > > > > > > > On Fri, Dec 1, 2017 at 12:18 AM, Nan Zhu <zhunanmcg...@gmail.com> > > wrote: > > > > > > > >> Hi, a

Re: What's everyone working on?

Subject: Re: What's everyone working on? Hi Nan Zhu, Thanks for the update. Curious to know what part of mxnet-spark are you working on? I am also evaluating the integration of MXNet with Spark, planning to start with PySpark and also looking into spark-deep learning-pipelines <https://github

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

+1 and recommend Jenkins-GitHub plugin with which committers/(accounts with assigned permissions) can trigger Jenkins build with "Test this please, Jenkins!" "Retest this please, Jenkins!" And accounts in the list can trigger build automatically when submitting a PR

Re: run Jenkins in a newer version of OS

I see, thanks, Mu! On Wed, Aug 23, 2017 at 9:18 AM, Mu Li <muli@gmail.com> wrote: > We can (should) upgrade the docker image used in CI from ubuntu 14.04 to > ubuntu 16.04 > > On Wed, Aug 23, 2017 at 7:01 AM, Nan Zhu <zhunanmcg...@gmail.com> wrote: > > &g

run Jenkins in a newer version of OS

Hi, all I just noticed that our Jenkins is running on Ubuntu 14.04, which does not even contain JDK8 in its default repo I am trying to do https://github.com/apache/incubator-mxnet/pull/7574/files to use some JDK8 APIs JDK 9 has been the topic, we might want to at least move on to JDK 8 Is it

Re: Java API for MXNet

have a well defined Java API you could look at the work I have > done by then and see how it can be plugged in or what can be learnt > from it. > > Jörn > > On Wed, Aug 16, 2017 at 9:05 PM, Nan Zhu <zhunanmcg...@gmail.com> wrote: > > +1 for Sandeep's suggestion > &g

Re: Java API for MXNet

me it looks like that the C API is very stable and used by all/most > >> > other APIs. If we have a Java API - accessing the C API via JavaCPP - > >> > then we should end up with a pretty stable solution and a lot the code > >> > that is duplicated with th

Re: Java API for MXNet

gt; >> > Even if we don't use JavaCPP, the JNI layer should be easy to get into > >> > a state where both can share it, the current Scala JNI layers LibInfo > >> > classes could be converted to Java classes and would in most cases > >> > require only minor

Re: Java API for MXNet

are it, the current Scala JNI layers LibInfo > > classes could be converted to Java classes and would in most cases > > require only minor changes in the Scala code. > > > > Jörn > > > > [1] https://github.com/apache/mahout/tree/master/viennacl/src/main > > &g

Re: Java API for MXNet

e converted to Java classes and would in most cases > require only minor changes in the Scala code. > > Jörn > > [1] https://github.com/apache/mahout/tree/master/viennacl/src/main > > On Wed, Aug 16, 2017 at 5:30 PM, Nan Zhu <zhunanmcg...@gmail.com> wrote: > >

Re: Java API for MXNet

I agree with Yizhi My major concern is the duplicate implementations, which are usually one of the major sources of bugs, especially with two languages which are naturally interactive (OK, Calling Scala from Java might need some more efforts). It is just like we provide C++ & C APIs of MxNet in

Re: how CI system works in MxNet?

ra/browse/INFRA-14840 > > On Sun, Aug 13, 2017 at 9:21 AM, Nan Zhu <zhunanmcg...@gmail.com> wrote: > > > no, I mean the CI system in our github repo.. > > > > On Sun, Aug 13, 2017 at 8:06 AM, shiwen hu <yajiedes...@gmail.com> > wrote: > > > >

Re: how CI system works in MxNet?

last build of a residual file. Try make clean. first > > > > 2017-08-13 22:35 GMT+08:00 Nan Zhu <zhunanmcg...@gmail.com>: > > > >> Hi, all > >> > >> I just noticed something which raises this question > >> > >> Yesterday afternoon

how CI system works in MxNet?

Hi, all I just noticed something which raises this question Yesterday afternoon, I checked https://github.com/apache/incubator-mxnet/commits/master and the first commit passed all tests However, when I checked again this morning, the test result was changed to fail... (one of my PRs also

Re: [Vote] New MXNet Logo

+1 Get Outlook for iOS From: Joseph Spisak Sent: Saturday, March 4, 2017 9:07:54 PM To: d...@mxnet.apache.org Subject: [Vote] New MXNet Logo [cid:9B78EEE7-84AC-4010-A7A6-DF7A4C196DCF@hsd1.ca.comcast.net.] Let's vote

Re: New Logo?

I assume that this vote is to decide *whether* we need a new logo? not specifically to one of the designs in the original vote under DMLC repo? On Tue, Feb 21, 2017 at 8:26 AM, Nan Zhu <zhunanmcg...@gmail.com> wrote: > +1 > > On Mon, Feb 20, 2017 at 11:57 PM, Henri Yandell <