Newsgroups: php.internals
Path: news.php.net
Xref: news.php.net php.internals:57599
Mailing-List: contact internals-help@lists.php.net; run by ezmlm
Received-SPF: error (pb1.pair.com: domain goirand.fr from 117.121.247.104 cause and error)
DomainKey-Status: good
DomainKey-Signature: a=rsa-sha1; c=simple; d=goirand.fr; h=message-id
	:date:from:mime-version:to:cc:subject:references:in-reply-to
	:content-type:content-transfer-encoding; q=dns; s=postfix; b=gNM
	rjjQJHp1YTHuZ5anwN4MZZBvakjOyFhQUJNMjR0kjEpiFedH4HxlQDat2hy/VPER
	jPl9KgmXmXob8nCBO5yeBvc7LSTo+0frrqA33t0bMGpdQQ8EWt5kV+gL3zHjnSCk
	FulW/l7pl07L9SaV+ajAgyXHYSCzKrCBse+HBywA=
Message-ID: <4F29550D.5020106@goirand.fr>
Date: Wed, 01 Feb 2012 23:06:53 +0800
Organization: GPLHost
User-Agent: Mozilla/5.0 (X11; U; Linux x86_64; en-US; rv:1.9.1.16) Gecko/20111110 Icedove/3.0.11
MIME-Version: 1.0
To: Debian PHP Maintainers <pkg-php-maint@lists.alioth.debian.org>
CC: PHP internals <internals@lists.php.net>
References: <CALjhHG-p-wx37h5QGsx=i5arCt6Nv=8-YFN_G31okKgqFABfjA@mail.gmail.com>
In-Reply-To: <CALjhHG-p-wx37h5QGsx=i5arCt6Nv=8-YFN_G31okKgqFABfjA@mail.gmail.com>
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: quoted-printable
Subject: Re: [php-maint] Uploading 5.4 RC to unstable (Was: Upcoming transition
 of php5 to 5.4)
From: thomas@goirand.fr (Thomas Goirand)

On 02/01/2012 06:11 PM, Ond=C5=99ej Sur=C3=BD wrote:
> Hi,
>=20
> I was thinking that it could be a good idea (after current version migr=
ates
> to testing) to upload 5.4RCx to unstable to begin work on transition as=
 soon
> as possible. RC releases should have stable API(?), so application wise
> there's no problem. I'll fill a release critical bug in our BTS, so
> the 5.4 version
> don't migrate to testing and close it with stable 5.4.0 release.
>=20
> Ccing PHP internals to let them know and ask if it is a good idea (the =
5.4RC
> will be probably used by more people when uploaded to Debian unstable, =
i.e.
> it means more testing, but also more bugreports).
>=20
> O.

I support this.

Removal of some legacy features, like these functions:
session_is_registered(), session_register() and session_unregister(), or
removal of .ini stuff like register_globals and register_long_arrays
WILL break applications.

The sooner we have PHP 5.4 in SID, the sooner people will realize
issues, and start fixing.

Anyways, I think we should write few words in -devel@, including
mentioning the above feature removal (or maybe simply showing the URL:
http://www.php.net/releases/NEWS_5_4_0_alpha1.txt, but I don't think
that's enough, insisting on session_register() removal for example,
which must be still widely used, is crucial).

Also, I'd like to know. In PHP 5.3, we had few deprecated functions
(ereg / eregi pops to mind, but also return new as reference). Are these
now totally removed from PHP 5.4, or do they still show with deprecation
warnings?

Thoughts?

Thomas