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

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 calls to the old package. > > On Tue, Mar 13, 201

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 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 Nan Zhu wrote: > > > +1 &

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

> >> > > > > > > > > >> > > > > > > > > >> > > > On Mon, Mar 12, 2018 at 9:56 AM, Marco de Abreu < > > > > > >> > > > marco.g.ab...@googlemail.com> wrote: > > > > > >> >

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. > > >> > > >> > &g

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, > > 17:33: > > > > > +1 > > > > > > On Mon, Mar 12, 2018 at

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 you, > > -Chris >

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 think having separate v

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

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 and worsen the quality of > > >> description. > > >> >

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, Ma

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 06:11:12, CodingCat wr

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

feel its unnecessary too - let's leave the [MODULE] out. > > > > > -Marco > > > > On Tue, Feb 27, 2018 at 11:34 PM, Yuan Tang > > wrote: > > > > > +1 > > > > > > On Tue, Feb 27, 2018 at 5:31 PM Suneel Marthi &

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

neel Marthi wrote: > On Tue, Feb 27, 2018 at 10:50 PM, Nan Zhu wrote: > > > Thanks, Suneel! > > > > the vote still remains sense on its major points > > > > " > > 1. most of PRs should be titled as [MXNET-???][MODULE_NAME] PR short > > descri

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

a github PR with PR label in title like [Flink-3456] for eg: - > that way the corresponding JIRA - Flink-3456 here would be automatically > updated. > > On Tue, Feb 27, 2018 at 10:28 PM, Nan Zhu wrote: > > > Hi, Suneel, > > > > how can we enable it? when we titled JI

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

ls is ASF infra recommending? > > Have you used > > https://github.com/apache/spark/blob/master/dev/github_jira_sync.py and > > what is the recommended use case? How do get github issues updated from > > Jira? > > > > Steffen > > > > On Tue,

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

ideally, users report something fishy in github issue when confirmed that it is a bug or something to be improved, we should create JIRAs On Sun, Feb 25, 2018 at 9:31 AM, Chris Olivier wrote: > i believe that JIRAs are “work items@, while github issues are more like > reporting. at least this

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 : > > Please extend the vote un

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 requests. > Specifically

Re: Release plan - MXNET 1.0.1

the previous release branch and build from there. Happy to > help with this if needed. > > On Thu, Jan 25, 2018 at 6:19 AM, Nan Zhu 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 minor release. > > Anyway the e

Re: Request For comments: MXNet Scala Inference API

.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 wrote: > > > is there any way to comment

Re: Request For comments: MXNet Scala Inference API

is there any way to comment inline in wiki? On Mon, Jan 22, 2018 at 6:05 PM, Naveen Swamy wrote: > Hi all, > > I have been looking at MXNet Scala Interface and find that there is a need > for a set of easy to use APIs for the inference use-case. I am proposing a > new set of APIs here > https://

Re: Guidance For Posting Jar to Apache Maven Repo

well, something can be borrowed from Spark again: https://github.com/apache/spark/blob/master/dev/create-release/release-build.sh Best, Nan On Wed, Jan 17, 2018 at 6:01 PM, Naveen Swamy wrote: > Hi Yizhi, > Here is the Apache guideline > http://www.apache.org/dev/publishing-maven-artifacts.htm

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 wrote: > Why -1? > > On Fri, Jan 5, 2018 at 11:03 AM, Nan Zhu

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 > > > > Can we please increase the indent limit from 100 to 120? I find 100 > > too lo

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 code/tests/example and > docs

Re: request for reviewing PR in ps-lite

when > > worker/server fail, right? > > > > I can help to review. ping @Mu for advice. > > > > 2017-12-05 13:13 GMT-08:00 CodingCat : > > > > > ping > > > > > > On Sat, Dec 2, 2017 at 10:04 AM, CodingCat > wrote: > > &g

request for reviewing PR in ps-lite

Hi, all I have been working on integrating MXNet with Spark in a more full-fledged manner. One of the most critical pre-conditions is to make parameter server in mxnet support multiple workers per process. I created the PR in https://github.com/dmlc/ps-lite/pull/121 (OK, sorry for being lateI

Re: What's everyone working on?

;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.com/databricks/spark

Re: What's everyone working on?

working on mxnet-spark, fixing some limitations in ps-lite(busy for daily job in these days, should be back next week) On Tue, Sep 26, 2017 at 10:13 AM, YiZhi Liu wrote: > Hi Dominic, > > I'm working on 0.11-snapshot and we will soon have one. While the > stable release will be after that we

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 https://wiki.jenkins.io/plu

Re: [BUILD FAILED] Branch master build 229

Hi, all this building result is a big noise here, I think Spark has a separate mail list for building results/commit record, etc., can we do that as well? and master branch has been broken for a while, looks like Python2/3: MKLML is the deal breaker Best, Nan On Thu, Aug 24, 2017 at 12:52 PM,

Re: run Jenkins in a newer version of OS

I see, thanks, Mu! On Wed, Aug 23, 2017 at 9:18 AM, Mu Li 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 wrote: > > > Hi, all > > > > I just noticed that our Jenkins

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 p

Re: Java API for MXNet

l 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 wrote: > > +1 for Sandeep's suggestion > > > > On Wed, Aug 16, 2017

Re: Java API for MXNet

If we 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 > wrote: > > +1 for Sandeep's suggestion &

Re: Java API for MXNet

ed 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 the Scala API is the generated code. > &

Re: Java API for MXNet

I don't think there will be problems under "11", did the user see concrete errors? Best, Nan On Wed, Aug 16, 2017 at 9:30 AM, YiZhi Liu wrote: > Hi Nan, > > Users have 2.11, but with a different minor version, will it cause > conflicts? > > 2017-08-17 0:19

Re: Java API for MXNet

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 > > > > On Wed, Aug 16, 2

Re: Java API for MXNet

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 wrote: > > I agree with Yizhi > > > > My major c

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 tw

Re: how CI system works in MxNet?

gt; > On Sun, Aug 13, 2017 at 9:21 AM, Nan Zhu wrote: > > > no, I mean the CI system in our github repo.. > > > > On Sun, Aug 13, 2017 at 8:06 AM, shiwen hu > wrote: > > > > > It may be that Sphinx cannot work incrementally > > > > > >

Re: how CI system works in MxNet?

gt; > > 2017-08-13 22:35 GMT+08:00 Nan Zhu : > > > >> Hi, all > >> > >> I just noticed something which raises this question > >> > >> Yesterday afternoon, I checked > >> https://github.com/apache/incubator-mxnet/commits/master and t

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 expose

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 on a new MXNet logo.

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 wrote: > +1 > > On Mon, Feb 20, 2017 at 11:57 PM, Henri Yandell wrote: > >> We should do a

Re: New Logo?

+1 On Mon, Feb 20, 2017 at 11:57 PM, Henri Yandell wrote: > We should do a vote on this, now that we have everyone here. > > Voting is described here: http://apache.org/foundation/voting.html > > (though basically it comes down to an email saying: > > > Let's vote on a thingy > [ ] +1;