[EMAIL PROTECTED] wrote:
Daniel John Debrunner <[EMAIL PROTECTED]> writes:
Kathey Marsden wrote:
Bryan Pendleton wrote:
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.
Seems downright anti-open source to me. Users can be made aware of
the conditions and can be a valuable resource in vetting a release
candidate or beta. But I guess I shouldn't get started. It;s not my
decision to make.
There's nothing to stop a beta-release being produced (ie. voted on &
released as a beta). It's just that no release manager has ever done
that in Derby.
torque does this, but the entire release process (vetting and voting) is
followed.
Isn't there something called lazy consensus? Would that not be good
enough for a beta...?
Lazy consensus never applies to a release (whether beta or not).
-jean
