Hey guys, just getting back from vacation, sorry for any delay in responses from my end.
A source release must contain no binary objects. Full details are available on the ASF release policy page [1]. Bazel can download them, http_file should be what you need. -Jake [1]: http://www.apache.org/legal/release-policy.html On Fri, Jul 21, 2017 at 7:02 AM, Karthik Ramasamy <[email protected]> wrote: > FYI - If the binary tar balls need to be removed, I believe bazel has a way > to download these files > and compile them. Let me investigate and report back. > > On Thu, Jul 20, 2017 at 2:07 PM, Bill Graham <[email protected]> wrote: > > > Hi, > > > > In the incubator vote thread John mentioned the following: > > > > - The contents of > > > https://github.com/twitter/heron/tree/master/third_party seems > > > to be mostly binary files, and you'll need to clean that up for your > > first > > > release. > > > > > > Jake mentioned the following: > > > > This is similar to other projects using a local third_party cache > directory > > > that have come to the Apache Incubator, Cassandra, Mesos and Aurora > are a > > > couple that jump into mind. We will ensure that this is addressed and > > that > > > no source release contains any of these files. > > > > > > What do we need to do to address this? Do we have to remove them from the > > repo and pull them at build time, or do we just need to check how we go > > about including them in our distribution? > > > > We'd like to start whatever cleanup is required before we move the code > to > > apache, so we can continue to cut releases while this is being tackled. > > > > thanks, > > Bill > > >
