RE: [PHP4BETA] PHP4 Betas

To me this indicates your beta releases are way too far apart. If the only way to see where you stand is by grabbing source from CVS and doing a build, you're probably cutting your effective beta testers by an order of magnitude. Not sure why so much time is needed, but this thinking might work against the goals of a beta program. It feels more like an alpha. > -----Original Message----- > From: David Shadoff [mailto:daves@interlog.com] > Sent: Saturday, October 30, 1999 11:50 PM > To: Rasmus Lerdorf > Cc: php4beta@lists.php.net > Subject: Re: [PHP4BETA] PHP4 Betas > > > >The main issue here is that there were a lot of things > broken in beta2 and > >we are so close to a beta3 that very few of the bug reports > based on beta2 > >are of any use to us at this point. There have been *a lot* > of changes > >since beta2. At this point, if you want someone to pay > attention to a bug > >report, you really need to file it against current cvs, or at least a > >snapshot less than a month old. That doesn't mean we ignore > others, but > >most of the stuff files against beta2 has been fixed. > > Glad to hear it; I definitely *will* re-test all of my bugs > against beta 3 > (when available). > > One suggestion: When you post a Beta version on the PHP > website, could you > please mark it with a release date (preferably on the webpage > itself), so > that unsuspecting folks like myself will understand whether > it's early or > late in that Beta's lifecycle ? > > > > > -- > PHP 4.0 Beta Mailing List <http://www.php.net/version4/> > To unsubscribe, e-mail: php4beta-unsubscribe@lists.php.net > For additional commands, e-mail: php4beta-help@lists.php.net > To contact the list administrators, e-mail: > php4beta-admin@lists.php.net >