Re: Re: cvs: php4(PHP_4_0_7) /sapi/roxen roxen.c
| From: | Yasuo Ohgaki | Date: | Wed, 06 Feb 2002 09:43:03 +0000 |
| Subject: | Re: Re: cvs: php4(PHP_4_0_7) /sapi/roxen roxen.c | ||
| References: | 1 | Groups: | php.dev |
| Request: | Send a blank email to php-dev+get-79324@lists.php.net to get a copy of this message | ||
Derick Rethans wrote:
On Sun, 3 Feb 2002, Yasuo Ohgaki wrote: Sometimes it takes a while for me to reply, but here it is :)Not really. I'm one of them that hesitate to use any version end with 0 for production systems. I feel confortable Version X.X.2 or X.X.3, especially when I don't know anything about source code. Therefore, I feel needs for 4.1.2, since there are critical bugs in 4.1.1. Some of them are easily merged from HEAD.Thanks. I feel it also. Although, I think are better to release 4.1.2 before 4.2.0.What _very_ critical fixes where done in the 4.1 branch? IMO, they certaily do not need a new 'bug-fix' release as was needed for 4.1.0. Therefore there shall not be an 4.1.2.
For me, segfault, data loss, security problem, bugs that can lead really hard to find in a script, build problem, problems that have no workaround and makes PHP useless for certain job. There may be others.I wouldn't merge my massive PostgreSQL changes to release branch, but I would like to merge simple and critical bug fixes to relase branch.What do you define as critical exactly? For me it is a security problem, or a major feature of PHP not working (ie. sessions or a bug in the MySQL module which renders it totally useles.)
We can agree on this one. Probably other problems, too :) -- Yasuo Ohgaki _________________________________________________________ Do You Yahoo!? Get your free @yahoo.com address at http://mail.yahoo.comOne think build error is ciritical, but others not :)I wasn't aware that it was a build error. In this case it should be merged of course.