Basically, if you plot the number of duplicate bugs over time you can estimate the # of undiscovered bugs, thus you can estimate the release candidate date.
If most of the bugs reported are new, non duplicate, that would mean that it's hard to statisiticaly project the total # of unknown bugs thus you are in alpha.
Commercial reality is you release a few days after getting final reqs. spec. ;-)
.V
Michael Marrotte wrote:
Does anyone know if there’s any standard guideline for estimating how much alpha and beta testing an application should get?
Michael Marrotte
Software Engineering Manager
1958 Commonwealth Lane
Tallahassee, FL 32303
Phone 850.350.7852
Mobile 850.322.6780
Fax 850.575.1729
Email [EMAIL PROTECTED] <mailto:[EMAIL PROTECTED]>
MSN Messenger [EMAIL PROTECTED] <mailto:[EMAIL PROTECTED]>
------------------------------------------------------------------------
--------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
-- Vic Cekvenich
Development Engineer Struts Portal / RIA CMS <http://www.baseBeans.com> NYC/Silicon Valley cell: 917 825 3035
--------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
