mxnet-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Naveen Swamy <mnnav...@gmail.com>
Subject Re: Scala Packages in Maven
Date Tue, 22 May 2018 00:47:27 GMT
not at the moment, certainly is in my radar. Apache release requires a
committer's LDAP username/password. we could see how we can leverage CI
setup to do this

On Mon, May 21, 2018 at 5:44 PM, Marco de Abreu <
marco.g.abreu@googlemail.com> wrote:

> Great, thanks a lot. This looks great!
>
> Is the result of your process going to be a script we can run to generate
> the artefacts? AFAIK, there's been attempts in the community to push
> towards CD, thus it'd be great if this process could directly be designed
> with an automated processing step in mind.
>
> -Marco
>
> On Tue, May 22, 2018 at 2:41 AM, Naveen Swamy <mnnaveen@gmail.com> wrote:
>
> > I am not sure who published it in the past, hence this discussion.
> >
> > I am already in the process of documenting them here, I clean it up and
> add
> > more info as I make progress.
> > 1)
> > https://cwiki.apache.org/confluence/display/MXNET/Release+Process#
> > ReleaseProcess-Step1.12.CreateScalaMavenPackages(WIP)
> >
> > 2) https://cwiki.apache.org/confluence/display/MXNET/MXNet-Scala
> >
> > On Mon, May 21, 2018 at 5:37 PM, Marco de Abreu <
> > marco.g.abreu@googlemail.com> wrote:
> >
> > > 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 <mnnaveen@gmail.com>
> > 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 <mnnaveen@gmail.com>
> > > 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
> > > > >
> > > >
> > >
> >
>

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