For 1, why would it be a blocker, given that there were previous releases?
Has there been compatibility issues for scala packages? If so, why did we
There are many maven packages that include binary already, so if we can
find the binary for all dependency it's probably best to link to them, and
let maven manage these dependencies.

For 2, since the current CI is based on Jenkins, I imagine it would be some
sort of Jenkins pipeline? Other people who're better versed in Jenkins can
chime in.

Personally, I'm interested in 3 as well. I have a pipeline for building pip
packages that's currently not utilizing the CI, and the item 3 is the
blocker too. Once you finish, it would be great to refer to the same
solution, so that I can move it into the same CI.


On Fri, Jul 27, 2018 at 4:37 PM, Qing Lan <lanking...@live.com> wrote:

> Hi all,
> Recently contributors on Scala Language development worked together and
> finally able to publish Scala package on Maven. Now I would like to raise a
> discussion to automate Scala release process and also discover a standard
> way to release different packages for MXNet so we won’t ask any individuals
> to spend a long time to publish the package.
> There are three blocks that stop this automated process:
>   1.  How to build general hardware-compatible backend dependencies for
> MXNet (Linux CPU/GPU Mac OSX)
>   2.  How to automate the frontend release process and CI integration
>   3.  How to keep credentials for the release in the pipeline
> Scala Release process created by Naveen: https://cwiki.apache.org/
> confluence/display/MXNET/MXNet-Scala+Release+Process
> Thanks,
> Qing

Reply via email to