James Cox wrote: > >>-----Original Message----- >>From: Yasuo Ohgaki [mailto:[EMAIL PROTECTED]] >>Sent: Sunday, February 03, 2002 1:43 AM >>To: [EMAIL PROTECTED]; [EMAIL PROTECTED] >>Subject: [PHP-DEV] Re: [PHP-CVS] cvs: php4(PHP_4_0_7) /sapi/roxen >>roxen.c >> >> >>[EMAIL PROTECTED] wrote: >> >>>Hello, >>> >>>Why are you merging this? This absolutely makes no sense, 1) this branch >>>is proably not used anymore in the future, 2) It's not anyware near a >>>critical thing. Please revert it. >>> >>> >>It may not be a ciritical bug for users other than Roxen. >>Why do you care, if this branch is not going to be used? >> >>There are many patches applied after 4.1.1 release also, >>if you want keep branch clean. >> >> > > Yasuo, I don't see the need here to MFH a patch to 4.1.1 -- unless something > _really_ major needs fixing, (and it doesn't) this branch is as good as > dead..
Thanks. I feel it also. Although, I think are better to release 4.1.2 before 4.2.0. > > If someone is using roxen, then we can stick a diff on the website, as a > minor patch, and / or they can cvs co from HEAD. > > my 2 <insert currency here> > I may not be following previous discussions well. Could you freshen my memory? 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. Do we change this rule after 4.1.0 release? (or I must be missed some rules) 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. If the rule is decided as a result of discussion, I'll follow the rules. Although, it would be really difficult to decide which one is critical or not. One think build error is ciritical, but others not :) -- Yasuo Ohgaki -- PHP Development Mailing List <http://www.php.net/> To unsubscribe, visit: http://www.php.net/unsub.php
