incubator-general mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Sheng Zha (Jira)" <>
Subject [jira] [Commented] (INCUBATOR-253) Issues with MXNet releases and their distribution
Date Mon, 13 Jul 2020 05:04:00 GMT


Sheng Zha commented on INCUBATOR-253:

[~jmclean] you added some notes to it and I'd like to continue the discussion here. You wrote:

> But I have two concerns ... b) branding all release as "3rd party" may not be the best
way to solve the issue.

First, I'd like to clarify that the claim is inaccurate in that we are not classifying all
releases as "3rd party". For example, the source releases are still very much first party
and we only make official source releases. In addition, assuming that you actually referred
to convenience binary releases, I'd like to understand more on why having third-party handle
the binary releases for our releases is "not the best". It serves the needs of our community
for faster installation and the fact of having third-party releases does not appear to be
forbidden in the overall policies in Apache. Could you be more specific on what your concerns

> Issues with MXNet releases and their distribution
> -------------------------------------------------
>                 Key: INCUBATOR-253
>                 URL:
>             Project: Incubator
>          Issue Type: Improvement
>            Reporter: Justin Mclean
>            Assignee: Justin Mclean
>            Priority: Major
> The main issues are:
> 1. Source and convenance binary releases containing Category X licensed code.
> 2. Website giving access to downloads of non released/unapproved code.
> 3. Website giving access to releases containing Category X licensed code.
> 4. Web site doesn't given enough warning to users of the issues with non (P)PMC releases
or making it clear that these are not ASF releases.
> 5. Maven releases containing Category X licensed code.
> 6. PiPy releases containing Category X licensed code.
> 7. Docker releases containing Category X licensed code.
> 8 Docker releases containing unreleased/unapproved code.
> 9. Trademark and branding issues with PiPy and Docker releases. 
> 10. Trademark and brand issues with naming of releases. 
> 11. Developer releases available to users and public searchable
> 12. Releases and other nightly builds on /
containing category X licensed code.
> 13. Lack of clarity on all platforms for what is an ASF release and what is not.
> 14. Branding and release of 3rd parties containing unreleased code. (e.g.
> For PiPy see:
> For Docker see:
> For web site pages see:
> I may of missed something, if so please add it.

This message was sent by Atlassian Jira

To unsubscribe, e-mail:
For additional commands, e-mail:

View raw message