Newsgroups: php.internals
Path: news.php.net
Xref: news.php.net php.internals:53937
Mailing-List: contact internals-help@lists.php.net; run by ezmlm
Received-SPF: pass (pb1.pair.com: domain gmail.com designates 74.125.83.42 as permitted sender)
MIME-Version: 1.0
In-Reply-To: <4E1DE20E.20902@sugarcrm.com>
References: <4E17F5A0.3070409@sugarcrm.com>
	<BC37F785-39A7-4A38-ADBD-482C7D87438B@roshambo.org>
	<4E1B9343.3090000@sugarcrm.com>
	<967B58EB-C704-40CD-AFEE-D0CA2192F4FA@roshambo.org>
	<4E1DC072.8080300@sugarcrm.com>
	<CAH-PCH7=08Pqq=5-Z5BA1wpc8sXcS20ohmsq8FGnDm-yQGqbyQ@mail.gmail.com>
	<4E1DE20E.20902@sugarcrm.com>
Date: Wed, 13 Jul 2011 20:35:37 +0200
Message-ID: <CAH-PCH50J+U4Jgupbc70v4ZdXq9nVk74n6AXpmmEQXt=gOP26A@mail.gmail.com>
To: Stas Malyshev <smalyshev@sugarcrm.com>
Cc: Philip Olson <philip@roshambo.org>, PHP Internals <internals@lists.php.net>
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: quoted-printable
Subject: Re: [PHP-DEV] [VOTE] 5.4 features vote
From: tyra3l@gmail.com (Ferenc Kovacs)

On Wed, Jul 13, 2011 at 8:21 PM, Stas Malyshev <smalyshev@sugarcrm.com> wro=
te:
> 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 the=
n
> 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 a=
re
> 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.

--=20
Ferenc Kov=C3=A1cs
@Tyr43l - http://tyrael.hu