I disagree.  Bug fixes are endless (this is not just a figure of speech), 
and if we schedule another RC every time someone fixes a bug, we'll never 
release.  None of the bugs fixed since RC7 are showstoppers, so the show 
goes on...

Zeev

At 23:56 22/4/2001, [EMAIL PROTECTED] wrote:
>On Sun, 22 Apr 2001, Zeev Suraski wrote:
>
> > At 22:47 22/4/2001, Sascha Schumann wrote:
> > >On Sun, 22 Apr 2001, Zeev Suraski wrote:
> > >
> > > > I'm going to base 4.0.5 on the RC7 tag, so this won't make it in 
> anyway.
> > >
> > >     It would be really inconvenient for users of PHP, if PHP
> > >     4.0.5 would not be compatible with existing web-servers.
> > >     Would you mind explaining how you came to the conclusion that
> > >     PHP 4.0.5 needs to be based on the RC7 tag?
> >
> > As I said last week, RC7 was to be the last RC, after which 4.0.5 would be
> > released in the beginning of the following week (i.e. tomorrow), barring
> > major unexpected bugs (the thttpd changes don't fall in that category).
>
>I don't think this is wise to do. Harald put in some fixes for COM support
>(a lot even) and Sascha's patch will fix bugs in thttpd support. I don't
>think it's a prob to delay the Release another week, as it's been a very
>long time since php4.0.4pl1 anyway. Releases with less bugs (through the
>patches from Harald and Sascha) are prefered over a fast release. You
>can see what happens if a product is release to fast if you look at the
>Win* OSses.
>
>regards,
>
>Derick Rethans
>PHP-QA
>
>---------------------------------------------------------------------
>         PHP: Scripting the Web - www.php.net - [EMAIL PROTECTED]
>              SRM: Site Resource Manager - www.vl-srm.net
>---------------------------------------------------------------------

--
Zeev Suraski <[EMAIL PROTECTED]>
CTO &  co-founder, Zend Technologies Ltd. http://www.zend.com/


-- 
PHP CVS Mailing List (http://www.php.net/)
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
To contact the list administrators, e-mail: [EMAIL PROTECTED]

Reply via email to