RE: [PHP-DEV] Merge policy

From: Date: Tue, 12 Dec 2000 11:18:50 +0000
Subject: RE: [PHP-DEV] Merge policy
References: 1  Groups: php.dev 
Request: Send a blank email to php-dev+get-40950@lists.php.net to get a copy of this message
At 13:20 12/12/2000, James Moore wrote:
Stas, I think mergeing any bug fix that is fairly major is OK, IE will case problems to some of the users that might well upgrade and will not beable to do so becuase of this bug. I would hope that you can judge wether it is major enough to go in and wont cause problems. That is the main thing, dont include code that might cause problems this late in the release cycle, the next RC will be the final one so the code wont get as much testing as it would have done if it had been added at the begining of the cycle. To be honest if you are adding patches to the tree at this point then it would be a good idea to create a regression test for the php-qa team to test it and only add the patch if your sure it wont cause problems else where and is really needed before this next release.
I agree. I think Stas is talking about the serialization fix, and even though this bug wasn't considered a showstopper for 4.0.4, it's a good idea to have it in.
Just my £0.02
That's not fair, the English small suggestions are worth 50% more than the American ones :) Zeev -- Zeev Suraski <zeev@zend.com> CTO, Zend Technologies Ltd. http://www.zend.com/

« previous php.dev (#40950) next »