Hi! On 7/13/11 11:11 AM, Ferenc Kovacs wrote:
I would also change my vote, I would go with keeping it deprecated, but turning it off by default (currently it isn't done, but the suggested development/production inis have this turned off), and remove it with the next minor version bump.
Which basically means doing nothing, as the effective default is the recommended INIs, where it's off. So what would change before now and then that makes it inacceptable to remove it now but acceptable to remove it then?
hopefully the security documentation will be in the better shape and we can figure out how to communicate such changes better to minimalize the impact.
Our abilities to communicate will probably be in 1 year exactly as they are now, unless there's some big project to improve it that I'm not aware of.
-- Stanislav Malyshev, Software Architect SugarCRM: http://www.sugarcrm.com/ (408)454-6900 ext. 227 -- PHP Internals - PHP Runtime Development Mailing List To unsubscribe, visit: http://www.php.net/unsub.php
