Hi Yizhi,
Here is the Apache guideline
http://www.apache.org/dev/publishing-maven-artifacts.html.
-Naveen
On Wed, Jan 17, 2018 at 5:59 PM, YiZhi Liu wrote:
> Since we now have changed Scala package prefix to org.apache, does someone
> have guidance for posting it to Apache's Maven Repository?
Since we now have changed Scala package prefix to org.apache, does someone
have guidance for posting it to Apache's Maven Repository?
FYI, ml.dmlc.mxnet was posted to oss.sonatype.org.
--
Yizhi Liu
DMLC member
Amazon Web Services
Vancouver, Canada
Hi Haibin,
Thanks for leading this. I suggest that we hold onto this release until we have
clarity on the following items.
1. branch usage and versioning
Given that we are past 1.0 and we're changing APIs, I'd like to suggest that we
first agree on how
versioning works in mxnet. If we follow se
Dear community members,
Now that we're preparing a new release under the 1.0 version, I'd like to
propose that we discuss, clarify, and decide how we use versions and
branches.
Current practice is:
1. we use master branch for development.
2. we fork from master branch and create release branch fo
[
https://issues.apache.org/jira/browse/MXNET-5?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Chris Olivier updated MXNET-5:
--
Component/s: MXNet Engine
> Performance: Refactor gluon data loader
> -
[
https://issues.apache.org/jira/browse/MXNET-5?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Chris Olivier updated MXNET-5:
--
Labels: gluon performance (was: )
> Performance: Refactor gluon data loader
>
Chris Olivier created MXNET-5:
-
Summary: Performance: Refactor gluon data loader
Key: MXNET-5
URL: https://issues.apache.org/jira/browse/MXNET-5
Project: Apache MXNet
Issue Type: Improvement
