On Wed, Jul 13, 2011 at 8:21 PM, Stas Malyshev <smalys...@sugarcrm.com> wrote:
> 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?
tyrael@thor:~/checkouts$ php -n -r 'echo PHP_VERSION."\n";echo
ini_get("magic_quotes_gpc")."\n";'
5.3.6-6~dotdeb.1
1
tyrael@chronos:~/checkouts/php/src/php/php-src/branches/PHP_5_4$
./sapi/cli/php -n -r 'echo PHP_VERSION."\n";echo
ini_get("magic_quotes_gpc")."\n";'
5.4.0alpha2-dev
1
it's still on by default (if you don't use a php.ini which disables
it), so you won't get the deprecated message, as it is only ommited
when you change that ini, or call the magic_quotes methods.
AFAIK
>
>> 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.
where did you get the 1 year? I mentioned the next minor version, I
thinks thats about 2-3 years from now.
I talked with a few people about the improvement of the current
security docs, and it was brough up also, that we would need a better
way to introduce our suggested/introduced changes before rolling out
an RC or a golden release.
the new php.net will be there also, so I'm positive about that we will
have more channels to communicate with the community.
--
Ferenc Kovács
@Tyr43l - http://tyrael.hu
--
PHP Internals - PHP Runtime Development Mailing List
To unsubscribe, visit: http://www.php.net/unsub.php
