Newsgroups: php.internals Path: news.php.net Xref: news.php.net php.internals:54210 Return-Path: Mailing-List: contact internals-help@lists.php.net; run by ezmlm Delivered-To: mailing list internals@lists.php.net Received: (qmail 16507 invoked from network); 26 Jul 2011 14:57:15 -0000 Received: from unknown (HELO lists.php.net) (127.0.0.1) by localhost with SMTP; 26 Jul 2011 14:57:15 -0000 Authentication-Results: pb1.pair.com header.from=philip@roshambo.org; sender-id=unknown Authentication-Results: pb1.pair.com smtp.mail=philip@roshambo.org; spf=permerror; sender-id=unknown Received-SPF: error (pb1.pair.com: domain roshambo.org from 209.85.213.42 cause and error) X-PHP-List-Original-Sender: philip@roshambo.org X-Host-Fingerprint: 209.85.213.42 mail-yw0-f42.google.com Received: from [209.85.213.42] ([209.85.213.42:40604] helo=mail-yw0-f42.google.com) by pb1.pair.com (ecelerity 2.1.1.9-wez r(12769M)) with ESMTP id 56/20-14790-AC5DE2E4 for ; Tue, 26 Jul 2011 10:57:14 -0400 Received: by ywb6 with SMTP id 6so339148ywb.29 for ; Tue, 26 Jul 2011 07:57:11 -0700 (PDT) Received: by 10.142.152.32 with SMTP id z32mr3609705wfd.396.1311692231436; Tue, 26 Jul 2011 07:57:11 -0700 (PDT) Received: from [192.168.1.30] (c-174-61-179-13.hsd1.wa.comcast.net [174.61.179.13]) by mx.google.com with ESMTPS id q2sm641105pbj.51.2011.07.26.07.57.09 (version=TLSv1/SSLv3 cipher=OTHER); Tue, 26 Jul 2011 07:57:10 -0700 (PDT) Mime-Version: 1.0 (Apple Message framework v1084) Content-Type: text/plain; charset=us-ascii In-Reply-To: Date: Tue, 26 Jul 2011 07:57:08 -0700 Cc: internals@lists.php.net Content-Transfer-Encoding: 7bit Message-ID: <17F372BC-F6A7-48C5-BD22-02D51A8BD728@roshambo.org> References: To: JJ X-Mailer: Apple Mail (2.1084) Subject: Re: [PHP-DEV] session_* removal in 5.4 From: philip@roshambo.org (Philip Olson) 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: (A) Rename 5.4 to 6.0 ... :) (B) Remove all BC breaking changes from 5.4 (C) Change the release RFC (addendum?) (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