Re: Re: cvs: php4(PHP_4_0_7) /sapi/roxen roxen.c

On Sun, 3 Feb 2002, Yasuo Ohgaki wrote: Sometimes it takes a while for me to reply, but here it is :) > 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. > I think we really need developer's web sites to > keep these kind of rules. > > IIRC, when we made a 2 branches, there is one simple > rule for MFH. If it's a bug fix, merge it if it's > possible. The general 'rule' is (we actually don't have rules for it) is to merge critical fixes to the release branch, to make sure that IF there will be a new release of an already release branch, those very critical fixes are taken into account. > 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.) > One 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. Derick --------------------------------------------------------------------- PHP: Scripting the Web - www.php.net - derick@php.net SRM: Site Resource Manager - www.vl-srm.net ---------------------------------------------------------------------