RE: [PHP-DEV] Merge policy

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. Just my £0.02 James > -----Original Message----- > From: Stanislav Malyshev [mailto:stas@zend.com] > Sent: 12 December 2000 10:52 > To: PHP Development > Subject: [PHP-DEV] Merge policy > > > Since we now have branch for 4.0.4, what is the merge policy to it? Should > any bugfix be merged, or there are any rules/guidelines about it? > > -- > Stanislav Malyshev, Zend Products Engineer > stas@zend.com http://www.zend.com/ +972-3-6139665 ext.106 > > > > -- > PHP Development Mailing List <http://www.php.net/> > To unsubscribe, e-mail: php-dev-unsubscribe@lists.php.net > For additional commands, e-mail: php-dev-help@lists.php.net > To contact the list administrators, e-mail: php-list-admin@lists.php.net