mxnet-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From YiZhi Liu <javeli...@gmail.com>
Subject Re: Refactoring MXNet scala code to use "org.apache.mxnet"
Date Thu, 11 Jan 2018 21:53:13 GMT
Since we now have changed package prefix to org.apache, does someone have
guidance for posting it to Apache's Maven Repository?

ml.dmlc.mxnet was posted to oss.sonatype.org.

2018-01-04 17:14 GMT-08:00 Lupesko, Hagay <lupesko@gmail.com>:

> Suneel,
>
> I tend to think for this issue, GitHub issue is good enough and we do not
> need JIRA.
> Can you clarify what is the advantage you see in using JIRA over GitHub
> issue for this specific case?
>
> Thanks!
> Hagay
>
> On 1/4/18, 16:34, "Suneel Marthi" <smarthi@apache.org> wrote:
>
>     Jira has been around for a while -
>     https://issues.apache.org/jira/projects/MXNET/
>
>     switch to using jira
>
>     On Thu, Jan 4, 2018 at 7:31 PM, Roshani Nagmote <
> roshaninagmote2@gmail.com>
>     wrote:
>
>     >  Hi,
>     >
>     > As currently, MXNet does not have Jira project, I have created
> github issue
>     > for now.
>     > https://github.com/apache/incubator-mxnet/issues/9315
>     >
>     > Will create the PR and link the issue there.
>     >
>     > Thanks,
>     > Roshani
>     >
>     > On Thu, Jan 4, 2018 at 3:08 PM, Naveen Swamy <mnnaveen@gmail.com>
> wrote:
>     >
>     > > Hi Suneel,
>     > >
>     > > Did we decide that we will using Jira going forward? If not, can
> someone
>     > > summarize on the improvement email on the consensus and lets make
> it
>     > > universal and how to use it, what is expected, etc.,
>     > >
>     > > For the record, I like the idea of using Jira for more openness.
>     > >
>     > > Also, MXNet does not have Jira project, can you help creating one?
>     > >
>     > > Thanks, Naveen
>     > >
>     > >
>     > > On Thu, Jan 4, 2018 at 2:35 PM, Suneel Marthi <smarthi@apache.org>
>     > wrote:
>     > >
>     > > > Is there a Jira for this? Please create a Jira and reference
> that in
>     > the
>     > > PR
>     > > > for this.
>     > > >
>     > > > On Thu, Jan 4, 2018 at 5:16 PM, Roshani Nagmote <
>     > > roshaninagmote2@gmail.com
>     > > > >
>     > > > 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 to use "org.apache.mxnet" instead of "ml.dmlc.mxnet".
>     > > > >
>     > > > > Currently, MXNet-Scala
>     > > > > <http://mxnet.incubator.apache.org/api/scala/index.html>
> library
>     > uses
>     > > > > "ml.dmlc.mxnet" packages. This work will change the way to
> import
>     > > modules
>     > > > > when using mxnet-scala package.
>     > > > >
>     > > > > *Old way:*
>     > > > >
>     > > > > scala> import ml.dmlc.mxnet._
>     > > > >    import ml.dmlc.mxnet._scala> val arr = NDArray.ones(2,
3)
>     > > > >    arr: ml.dmlc.mxnet.NDArray = ml.dmlc.mxnet.NDArray@f5e74790
>     > > > >
>     > > > > *New way:*
>     > > > >
>     > > > > scala> import org.apache.mxnet._
>     > > > >    import org.apache.mxnet._
>     > > > > scala> val arr = NDArray.ones(2, 3)
>     > > > >    arr: org.apache.mxnet.NDArray = org.apache.mxnet.NDArray@
> f5e74790
>     > > > >
>     > > > >
>     > > > > Please let me know if anyone has any thoughts or issues with
> this
>     > > change.
>     > > > >
>     > > > > Thanks,
>     > > > > Roshani
>     > > > >
>     > > >
>     > >
>     >
>
>
>
>


-- 
Yizhi Liu
DMLC member
Amazon Web Services
Vancouver, Canada

Mime
  • Unnamed multipart/alternative (inline, None, 0 bytes)
View raw message