: At this major juncture in the project (switching build systems), it's worth : re-considering what we need to produce on a release. A -src.tar.gz seems : anachronistic to me given both (a) GitHub source control providing a : convenient download .tar.gz for any release "tag" -- : https://github.com/apache/lucene-solr/releases, and (b) maven central : having -source.jar for convenience in IDE tooling. So why bother?
Because we're required to by ASF policy... http://www.apache.org/legal/release-policy.html#artifacts "Every ASF release MUST contain one or more source packages, which MUST be sufficient for a user to build and test the release provided they have access to the appropriate platform and tools." ... "As a convenience to users that might not have the appropriate tools to build a compiled version of the source, binary/bytecode packages MAY be distributed alongside official Apache releases. In all such cases, the binary/bytecode package MUST have the same version number as the source release and MUST only add binary/bytecode files that are the result of compiling that version of the source code release and its dependencies." -Hoss http://www.lucidworks.com/ --------------------------------------------------------------------- To unsubscribe, e-mail: dev-unsubscr...@lucene.apache.org For additional commands, e-mail: dev-h...@lucene.apache.org
