Agree, we should make a proper assessment of what all these packages are before we try managing them. Do you know who published them before?
Moving forward, it'd be great if you could document the entire process (and all issues you encounter) in confluence. This would allow us to re-visit decisions later on and give us a source of information for questions exactly like this one. If we decide to add a new package to the publish process, we could just document it there and have a central point to look it up. -Marco On Tue, May 22, 2018 at 1:34 AM, Naveen Swamy <[email protected]> wrote: > I think this needs quite a bit of rework to clean up, currently I am > thinking to publish only the mxnet-full_2.11-{platform} x 3 and revisit > what the other packages should be published by the next release > > On Mon, May 21, 2018 at 3:49 PM, Naveen Swamy <[email protected]> wrote: > > > I am working on publishing MXNet Scala packages of the 1.2 release to > > maven and observed that there are about 20 packages that needs to be > > published. I think this is too many of them and probably will confuse the > > users. > > > > I think we can cut down the number of packages, I wanted ask if someone > > knows why the below packages were published and if it is ok not publish > > them going forward. > > > > Proposing to not publish > > --- > > > > mxnet-full-parent_2.11 > > mxnet-parent_2.11 > > mxnet-scala-native-parent > > Any other packages that you propose to remove? > > --- > > > > ---Full List -- > > libmxnet-init-scala-{platform} x 2 > > libmxnet-scala-{platform} x 3 > > mxnet-core_2.11 > > mxnet-examples_2.11 > > mxnet-full-parent_2.11 > > mxnet-full_2.11-{platform} x 3 > > mxnet-infer_2.11 > > mxnet-init_2.11 > > mxnet-macros_2.11 > > mxnet-parent_2.11 > > mxnet-scala-init-native-parent > > mxnet-scala-native-parent > > mxnet-spark_2.11 > > --- > > > > Please let me know your thoughts? > > > > Thanks, Naveen > > >
