In reply to <mid:[EMAIL PROTECTED]> : >> IMHO, the beta site should be the place to start looking for new >> beta versions. I don't think that being a list member is a >> requirement to access the beta site but I could be wrong.
GMM> I would prefer a "closed beta - public beta" approach. The closed GMM> betas should be announced only on the list and only list members GMM> should be able download those builds. The open betas would be the GMM> release candidates in .msi form and should be available to all GMM> people after some days of testing from the members of the list. Honestly, I don't see the need. Plus, the way it is seems to be, already, too much work to keep the beta site current. I rather have the current model working than implementing a new, "heavier", model. GMM> This seems to be an overkill but it has some profound advantages GMM> 1. People wouldn't be able to download potential dangerous betas. GMM> Of course one could say "It's a beta, use it at your own risk" GMM> but the word of mouth in a case like that will be very bad PR, GMM> even if the audience is warned. I've been around for almost 2 years and I never saw a beta build that I could say it was dangerous. Some aren't very good but not bad enough to lose mail. -- Best regards, Goncalo Farias U.S. Department of Redundancy Department ________________________________________________________ Current beta is 3.65.02 | 'Using TBBETA' information: http://www.silverstones.com/thebat/TBUDLInfo.html IMPORTANT: To register as a Beta tester, use this link first - http://www.ritlabs.com/en/partners/testers/
