incubator-general mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Harbs <>
Subject Re: Convenience Binary Policy
Date Tue, 21 Oct 2014 13:55:33 GMT
The one thing I see missing from the proposed text is dependencies and installers.

Particularly this section:
### Compiled packages ### {#compiled-packages}

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.  In all such cases, the
binary/bytecode package MUST have the same version number as the source
release and MUST only add binary/bytecode files that are the result of
compiling that version of the source code release.
How do binary dependencies fit in?

On Oct 21, 2014, at 4:43 PM, Alex Harui <> wrote:

> On 10/21/14, 5:57 AM, "Marvin Humphrey" <> wrote:
>> The problem is that we lack a concise policy document.  That's where the
>> "ASF
>> release policy codification proposal" as worked through on legal-discuss
>> a few
>> months ago is supposed to help.
> Hi Marvin, IMO, this version of the document also doesn’t prohibit me from
> updating the binary package without a vote.  It seems like some portions
> of this document is supposed to apply to binary packages like the
> LICENSE/NOTICE sections so I think that’s why there is still ongoing
> debate on the Flex mailing list about whether I can in fact modify the
> FlexJS binary package.
> At this point, unless someone not on the Flex PMC says that we can’t make
> the modifications, I am planning to add a new entry to the Flex Installer
> that points to bits that are hosted on  my personal server called “Apache
> FlexJS 0.0.2 (with Jburg)” and expose it to the general public.  All of
> the compiled bits are the same, but I have added the jburg.jar to the
> package to workaround the problem.  The original binary package will
> remain on dist/mirrors.
> Thanks,
> -Alex

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

View raw message