Hi, Part of the Heron binary release is more than just the client artifacts that would be loaded into Maven Central. For example if you look at an old release prior to Heron being donated to Apache we have install scripts and tarred binaries for use in different operating systems. You can view them here -> https://github.com/apache/incubator-heron/releases/tag/0.17.8. Where would be go about hosting these install scripts and tar.gz files? I think each of them are ~500MB in size today. My initial thoughts (for simplicity) are that we could ignore the tar.gz files containing binaries and just offer install scripts and one supported docker image. If binaries are needed for manual installation I think people could just compile parts of Heron at that point. I'll look into the licensing/policy issues on the Heron docker container in the meantime.
- Josh On Fri, Jan 17, 2020 at 7:24 PM Dave Fisher <[email protected]> wrote: > The ASF as a whole is rather conservative in the sense of being slow to > change. > > Maven Central for JAR packaging has been around for over a decade AND is > supported by Apache projects. > > Docker is comparatively new and there is less policy around it. There is > some, but perhaps not well documented. > > I think we should evaluate the docker file and see what licensing/policy > questions there are. We can then ask the VP, Legal Affairs on > [email protected] > > Regards, > Dave > > Sent from my iPhone > > > On 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 > >>>>> > >>>> > >>> > >> > >
