On Sun, Jan 22, 2017 at 4:59 PM Justin Mclean <jus...@classsoftware.com> wrote:
> Hi, > > > Same thread. Specifically Mark T's response [1] and Craig's affirmation > [2] > > Not sure that applies here as I think we have compiled code without the > corresponding source. Can someone on the project confirm? > > If you look in the tar.gz you'll see that it's R source code, and a JAR for testing. Its not compiled code. > Even then I would expect that to be an unusual exception where there was > no other way of not including the source code. If it’s compiled it not > really open source is it? > > Documentation (recently changed) [1][2] has been clear that source > releases should not contain jar files. Both of these pages use to contain a > release checklist that contained: > "This package may not contain compiled components (such as "jar" files) > because compiled components are not open source, even if they were built > from open source.” > > BTW that checklist was quite useful perhaps we should put it back > somewhere? > The reason that these contents were removed (and now I'm glad I did CTR). The foundation's policy does not mention JARs or any of these provenances. It doesn't make sense for these policies to apply to podlings when they don't apply to TLPs. I'd be fine adding something like a checklist to [3]. John [3]: http://www.apache.org/dev/release.html#what-must-every-release-contain > > Thanks, > Justin > > 1. > https://web.archive.org/web/20161120035911/http://incubator.apache.org/guides/releasemanagement.html#check-list > 2. > https://web.archive.org/web/20160803190705/https://incubator.apache.org/guides/release.html > > > --------------------------------------------------------------------- > To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org > For additional commands, e-mail: general-h...@incubator.apache.org > >
