MaXxX,
M> You "downgrading" or "rolling-back" guys, you're not using a newest
M> beta for everyday use, so that having a newest-but-broken beta would
M> stop your normal mail activities - are you? :P
You are confusing alpha testing with beta testing.
The purpose of beta testing is to gain real-life experience with
code that is nearly ready for release. That requires using it
for... real life. If beta testers do not use TB for everyday
activity, then TB will not be tested for everyday use.
Ritlabs needs to start distinguishing between "new code" testing,
which is usually called "alpha", from "almost ready for release"
testing, which is usually called "beta".
The difference between these two modes is supposed to be
fundamental, when serious software development methodology is in
use.
Testing in the later stages involves code that is highly stable,
except for bug-fixes. It involves few, small feature additions.
By confusing the two, Ritlabs is failing to unable to get testing
that squeezes out the unusual-but-serious bugs which can only be
discovered by having heavy, real-world use by real users.
d/
--
Dave Crocker <dcrocker-at-brandenburg-dot-com>
Brandenburg InternetWorking <www.brandenburg.com>
Sunnyvale, CA USA <tel:+1.408.246.8253>
________________________________________________________
Current beta is 3.00.11 | '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/
