Hey Nick, The licensing issues are outlined in this email thread from our last vote: https://mail-archives.apache.org/mod_mbox/incubator-general/201911.mbox/%3C99E443FF-01D7-47C3-9AA0-7F5F1848686E%40classsoftware.com%3E
On Fri, Jan 17, 2020 at 6:46 PM Nicholas Nezis <[email protected]> wrote: > Could someone describe what the licensing issue is? I thought work was > already done to include the various license references. > > On Fri, Jan 17, 2020 at 5:54 PM Ning Wang <[email protected]> wrote: > > > Yeah. Technically artifacts contains the dependency libraries tool. Maybe > > artifacts are more urgent and necessary than the executables. Afterall > > executables are convenient to users but not required in the Apache > release > > process. > > > > On Fri, Jan 17, 2020 at 2:41 PM Josh Fischer <[email protected]> > wrote: > > > > > Gotcha. I understand the difference in the two now, but I'm not sure > why > > > one would be allowed over the other. At the end of the day they are > both > > > compiled binaries released under the Apache foundation. I'll take some > > > time to read through apache docs to see if I can get a better > > understanding > > > of the differences in the two. > > > > > > On Fri, Jan 17, 2020 at 4:28 PM Ning Wang <[email protected]> > wrote: > > > > > > > That's true. Maven artifacts are binaries too. My bad. > > > > > > > > The "binary" I was referring to are the executables, such as > installer, > > > > which contains quite some executables like CLI, exeample jobs, UI, > > > tracker, > > > > etc. The docker image is also part of my "binary". > > > > > > > > Basically users can just install and run their jobs without compiling > > all > > > > the tools from source code. Maven artifacts allow users to build > their > > > > jobs. They still need to compile all the other things in order to run > > the > > > > jobs. > > > > > > > > I hope it is more clear this time. > > > > > > > > > > > > > > > > On Fri, Jan 17, 2020 at 1:59 PM Josh Fischer <[email protected]> > > > wrote: > > > > > > > > > I'm not sure I understand how you are defining the differences > > between > > > > the > > > > > terms "maven artifacts" and "binary releases". Wouldn't a maven > > > > artifact ( > > > > > java jar ) be considered a binary release as well? Am I missing > > > > something? > > > > > > > > > > > > > > > On Fri, Jan 17, 2020 at 1:02 AM Ning Wang <[email protected]> > > > wrote: > > > > > > > > > > > I think we can not make an official binary release yet before > clear > > > all > > > > > > license issues. Therefore, 0.20.0.2 can have maven artifacts but > it > > > > can't > > > > > > have binary release. :( > > > > > > > > > > > > That's just my understanding of Apache requirements. > > > > > > > > > > > > On Thu, Jan 16, 2020 at 2:24 PM Josh Fischer < > [email protected]> > > > > > wrote: > > > > > > > > > > > > > Hi, > > > > > > > > > > > > > > I'd like to start the process to vote for the 0.20.2-incubating > > > > binary > > > > > > > release. Before we start I remember there were concerns about > > the > > > > size > > > > > > of > > > > > > > the Heron binary and where it would be hosted on Apache Infra. > > > Does > > > > > > anyone > > > > > > > have any knowledge on this potential issue? > > > > > > > > > > > > > > - Josh > > > > > > > > > > > > > > > > > > > > > > > > > > > >
