On Tue, Jun 23, 2015 at 3:20 PM, Ross Gardler (MS OPEN TECH)
<ross.gard...@microsoft.com> wrote:
> There is nothing preventing "clearly identifiable non-release artifacts
> available to the general public".
The Releases Policy page forbids it explicitly:
During the process of developing software and preparing a release, various
packages are made available to the developer community for testing
purposes. **Do not include any links on the project website that might
encourage non-developers to download and use nightly builds, snapshots,
release candidates, or any other similar package.** The only people who are
supposed to know about such packages are the people following the dev list
(or searching its archives) and thus aware of the conditions placed on the
package. If you find that the general public are downloading such test
packages, then remove them.
Under no circumstances are unapproved builds a substitute for releases. If
this policy seems inconvenient, then release more often. Proper release
management is a key aspect of Apache software development.
What differentiates the "general public" from "developers" is whether they are
aware of the conditions placed on the artifacts and thus exercising informed
consent.
Those conditions are are not limited to instability of the codebase, but also
whether the artifacts meet Apache's licensing and legal requirements for
releases.
Marvin Humphrey
---------------------------------------------------------------------
To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org
For additional commands, e-mail: general-h...@incubator.apache.org
