Dear community, It would be great if more people can validate the release candidate and cast the vote.
Best, Seunghyun On Mon, Mar 4, 2019 at 9:50 PM Justin Mclean <jus...@classsoftware.com> wrote: > Hi, > > > How do you think on this? I discussed with one of our mentors and he was > > fine with including binary LICENSE/NOTICE file to a source code release. > > As long as it clear they are for the binary and not the source release I > don’t see any issue with that. > > > 2. Can you provide me some example projects that are including > > version/commitid/tag for each listed dependencies as a reference? > > As the license can change between versions of a product (see bootstrap for > instance) it’s a good idea to include its version number.. > > > 3. I guess that the archives that you mention are probably sample data > that > > are used for unit/integration tests. If we removed those archives, tests > > will probably fail. > > As long as they don’t contain compiled code (and they didn’t last release > I reviewed) it’s fine. > > Thanks, > Justin > --------------------------------------------------------------------- > To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org > For additional commands, e-mail: general-h...@incubator.apache.org > >
