Newsgroups: php.internals
Path: news.php.net
Xref: news.php.net php.internals:54211
Mailing-List: contact internals-help@lists.php.net; run by ezmlm
Received-SPF: pass (pb1.pair.com: domain gmail.com designates 209.85.160.170 as permitted sender)
MIME-Version: 1.0
In-Reply-To: <17F372BC-F6A7-48C5-BD22-02D51A8BD728@roshambo.org>
References: <CAB75mSWYWsN7j35pLZY8Y2S1mXikkE04Sq_-aYKae5SVoj_zVw@mail.gmail.com>
	<17F372BC-F6A7-48C5-BD22-02D51A8BD728@roshambo.org>
Date: Tue, 26 Jul 2011 17:00:25 +0200
Message-ID: <CAH-PCH5XhcjsyedtA-3Nbo+8Dpv_j7fUkLNhGcKJXKxLBNMU9A@mail.gmail.com>
To: Philip Olson <philip@roshambo.org>
Cc: JJ <jawed@php.net>, internals@lists.php.net
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: quoted-printable
Subject: Re: [PHP-DEV] session_* removal in 5.4
From: tyra3l@gmail.com (Ferenc Kovacs)

On Tue, Jul 26, 2011 at 4:57 PM, Philip Olson <philip@roshambo.org> wrote:
>
> On Jul 25, 2011, at 1:57 PM, JJ wrote:
>
>> While looking over the release notes for 5.4a1
>> (http://www.php.net/archive/2011.php#id2011-06-28-1) I noticed that
>> the related session_* functions had been removed.
>>
>> As I interpreted it, this goes against the spirit of the release RFC
>> for x.y+1.z releases, specifically:
>>
>> - Backward compatibility must be kept
>> - API compatibility must be kept (user land)
>>
>> The removal of these functions makes sense (to me) but I think in
>> order to respect the release RFC we should either:
>>
>> a) defer the removal of session_* functions till the appropriate release
>> b) update the RFC nomeclature to cover this use case (as Florian
>> pointed out, the current wording leaves it open to interpretation)
>>
>> I do realize I'm late to the party (sorry) and I'm not sure if it's
>> too late to revert course on this specific change...but I think the
>> session_* removal change will make the upgrade process more difficult
>> because of its' far-reaching impact.
>
> In reality, PHP 5.4 does not follow the aforementioned release RFC as it
> breaks a lot of BC. It follows part of it, but certainly not all.
>
> If the session_* functions are restored due to BC, then a lot of other
> old stuff will need to follow along. Here are a few options:
>
> =C2=A0(A) Rename 5.4 to 6.0 ... :)
> =C2=A0(B) Remove all BC breaking changes from 5.4
> =C2=A0(C) Change the release RFC (addendum?)
> =C2=A0(D) Mention that 5.4 does not fully follow the release RFC, and why
>
> I suspect a version of (D) will be implemented at this point, and 5.4
> kinda sorta existed before the RFC. A difficult decision.
>
> Regards,
> Philip
>
>
> --
> PHP Internals - PHP Runtime Development Mailing List
> To unsubscribe, visit: http://www.php.net/unsub.php
>
>

Could we get a list of the BC breaks?
It would be required to get together eventually as we have to write
the 5.3->5.4 migration guide as we did in the past for the previous
versions.


--=20
Ferenc Kov=C3=A1cs
@Tyr43l - http://tyrael.hu