www-legal-discuss mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "John D. Ament (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (LEGAL-323) Clarify if binary artifacts are part of a release
Date Wed, 02 Aug 2017 03:26:00 GMT

    [ https://issues.apache.org/jira/browse/LEGAL-323?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16110216#comment-16110216
] 

John D. Ament commented on LEGAL-323:
-------------------------------------

I have to agree with Justin.  While I have not reviewed anywhere near the number of releases
he has, and I suspect his count is far lower than reality, I would be shocked if the foundation
suddenly said that CatX dependencies can be included in binary releases.  This is especially
after the comments in LEGAL-319, clarifying that it is CatX but cannot be included in releases.

> Clarify if binary artifacts are part of a release
> -------------------------------------------------
>
>                 Key: LEGAL-323
>                 URL: https://issues.apache.org/jira/browse/LEGAL-323
>             Project: Legal Discuss
>          Issue Type: Question
>            Reporter: Andrew Wang
>            Assignee: Chris A. Mattmann
>
> Hi,
> Reading the release policy and particularly http://www.apache.org/legal/release-policy.html#compiled-packages
I'm still confused as to whether binary artifacts are considered part of a release.
> {quote}
> The Apache Software Foundation produces open source software. All releases are in the
form of the source materials needed to make changes to the software being released.
> As a convenience to users that might not have the appropriate tools to build a compiled
version of the source, binary/bytecode packages MAY be distributed alongside official Apache
releases.
> {quote}
> This seems to imply that only the source is the official release. Binary artifacts are
not part of the release, and are just distributed on the side.
> Reading the rest of this page though, it's pretty clear that binary artifacts still need
to adhere to the requirements for release artifacts, e.g. licensing and distribution location.
> What does this mean in practical terms? If we build a tarball with jars and native libraries
in it, is it part of our official release? What about jars uploaded to Maven Central? When
the PMC votes on a release, are we voting on just the source tarball, or also these additional
binary artifacts?
> Thanks,
> Andrew



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

---------------------------------------------------------------------
To unsubscribe, e-mail: legal-discuss-unsubscribe@apache.org
For additional commands, e-mail: legal-discuss-help@apache.org


Mime
View raw message