t; > http://mxnet.incubator.apache.org/install/index.html?
> > > platform=Linux=R=CPU
> > > and thought that we might want to add a link so our users wouldn't have
> > to
> > > compile it themselves.
> > >
> > > Best regards,
> > > Marco
> > >
ttp://mxnet.incubator.apache.org/install/index.html?
> > platform=Linux=R=CPU
> > and thought that we might want to add a link so our users wouldn't have
> to
> > compile it themselves.
> >
> > Best regards,
> > Marco
> >
> > On Tue, Jul 3, 2018
> Marco
>
> On Tue, Jul 3, 2018 at 7:45 PM Anirudh Acharya
> wrote:
>
> > Hi Marco,
> >
> > A release process for the R-package would probably involve publishing the
> > package to CRAN. Currently it is not done and the r-package would need
> > considerable ch
=Linux=R=CPU
and thought that we might want to add a link so our users wouldn't have to
compile it themselves.
Best regards,
Marco
On Tue, Jul 3, 2018 at 7:45 PM Anirudh Acharya
wrote:
> Hi Marco,
>
> A release process for the R-package would probably involve publishing the
> pac
Hi Marco,
A release process for the R-package would probably involve publishing the
package to CRAN. Currently it is not done and the r-package would need
considerable changes/improvements before it can get published to CRAN.
So at present accessing the package from the S3 bucket is the surest
Hello,
do we have a release process for our R frontend? I noticed the issue at [1]
and it seems like we're only publishing to an S3 bucket which is not under
Apache. Is there another channel for our users to retrieve that package or
is this our only supported official way?
Best regards,
Marco