mxnet-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Sheng Zha <szha....@gmail.com>
Subject Re: Issue with releases / feedback from ASF board
Date Sun, 24 May 2020 01:05:12 GMT
Thanks for the reply. Besides the clarification below, we will track and
address here [1] the rest of the comments in this thread.

> > - We will introduce source releases on PyPI and Maven using apache-mxnet
> > name to provide users with the option to have Apache distribution and
allow
> > users to compile CUDA/cuDNN code as an option.
>
> I assume that mean you will two distribution on PyPI? Or is the intent to
remove the other one?

- We PPMC will create apache-mxnet package with Apache releases in the form
of source distributions. This is intended as first-party release to comply
with the draft release policy.
- As individual, and with appropriate names and description as determined
by trademark review, I intend to continue to provide binary releases on
PyPI for the convenience of the community. This is out of necessity as
compiling all the CUDA code in MXNet can take hours even on powerful CPUs.

-sz

[1] https://github.com/apache/incubator-mxnet/issues/18397

On Sat, May 23, 2020 at 5:15 PM Justin Mclean <justin@classsoftware.com>
wrote:

> Hi,
>
> > - MXNet publishes only nightly pre-release builds to dist.mxnet.io for
> the
> > verification purpose for projects in the ecosystem and for developers who
> > work on the bleeding edge.
>
> IMO Something more needs to be done here, at the very least I would expect
> to se a very large disclaimer that these are not releases for use of the
> general public and for internal development use only and are not Apache
> Releases.  A google search brings up that page and it is incorrectly titled
> "Apache MXNet Python Binary Distribution”. I see other download pages that
> just contain links and no information to what the files are.
>
> It also needs to be clear what a user is installed from this install page
> [1] which I assume is using the above? The GitHub download page [2] is also
> confusing as it contains a mix of Apache and non-Apache releases.
>
> > - PyPI releases are not the act of this PPMC, but are from individuals
> > acting as third-party for the convenience of the community.
>
> Currently this page isn’t in line with Apache trademark policy.
>
> > With my PPMC hat on, we will take the following actions:
> >
> > - We will try to take down problematic Maven releases immediately and
> > discuss in the community how to proceed with future Maven releases.
>
> Thanks for that.
>
> > - We will introduce source releases on PyPI and Maven using apache-mxnet
> > name to provide users with the option to have Apache distribution and
> allow
> > users to compile CUDA/cuDNN code as an option.
>
> I assume that mean you will two distribution on PyPI? Or is the intent to
> remove the other one?
>
> > Finally, we appreciate any lesson other projects can share on licensing
> and
> > distribution that involves CUDA code. Thanks.
>
> I’m not aware of any other project that uses CUDU code.
>
> Thanks,
> Justin
>
> 1. https://mxnet.apache.org/get_started/?
> 2. https://github.com/apache/incubator-mxnet/releases
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: general-unsubscribe@incubator.apache.org
> For additional commands, e-mail: general-help@incubator.apache.org
>
>

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