Newsgroups: php.internals Path: news.php.net Xref: news.php.net php.internals:57594 Return-Path: Mailing-List: contact internals-help@lists.php.net; run by ezmlm Delivered-To: mailing list internals@lists.php.net Received: (qmail 49249 invoked from network); 1 Feb 2012 10:12:17 -0000 Received: from unknown (HELO lists.php.net) (127.0.0.1) by localhost with SMTP; 1 Feb 2012 10:12:17 -0000 Authentication-Results: pb1.pair.com smtp.mail=ondrej@sury.org; spf=pass; sender-id=pass Authentication-Results: pb1.pair.com header.from=ondrej@sury.org; sender-id=pass Received-SPF: pass (pb1.pair.com: domain sury.org designates 209.85.210.42 as permitted sender) X-PHP-List-Original-Sender: ondrej@sury.org X-Host-Fingerprint: 209.85.210.42 mail-pz0-f42.google.com Received: from [209.85.210.42] ([209.85.210.42:51849] helo=mail-pz0-f42.google.com) by pb1.pair.com (ecelerity 2.1.1.9-wez r(12769M)) with ESMTP id 84/83-23487-000192F4 for ; Wed, 01 Feb 2012 05:12:16 -0500 Received: by dang27 with SMTP id g27so861865dan.29 for ; Wed, 01 Feb 2012 02:12:13 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=sury.org; s=google; h=mime-version:from:date:message-id:subject:to:content-type :content-transfer-encoding; bh=5D5k2Tpd63kFrXPKHD7Ae+nSX4jy6slD9fjbMKInhwk=; b=G87G/LNfcvVfwk7RxsxMMQVmP2PyLIPdO7LaRhM+3nNUhXfepi5LkElvNOOWO++jSL cJ8n2OQpnLu9YjlgrNtGT4gLM6wlv7q6QMZGUJhjWnd1F9IIzsY8CJrq0M7Ea+e+A7No qTSeUERWQRV6PGc0LuQKYQHm6KThYk22ZFiIc= Received: by 10.68.216.4 with SMTP id om4mr41247758pbc.19.1328091132955; Wed, 01 Feb 2012 02:12:12 -0800 (PST) MIME-Version: 1.0 Received: by 10.142.44.18 with HTTP; Wed, 1 Feb 2012 02:11:52 -0800 (PST) Date: Wed, 1 Feb 2012 11:11:52 +0100 Message-ID: To: Debian PHP Maintainers , PHP internals Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: quoted-printable Subject: Uploading 5.4 RC to unstable (Was: Upcoming transition of php5 to 5.4) From: ondrej@sury.org (=?UTF-8?B?T25kxZllaiBTdXLDvQ==?=) Hi, I was thinking that it could be a good idea (after current version migrates to testing) to upload 5.4RCx to unstable to begin work on transition as soo= n 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. Ccing PHP internals to let them know and ask if it is a good idea (the 5.4R= C will be probably used by more people when uploaded to Debian unstable, i.e. it means more testing, but also more bugreports). O. ---------- Forwarded message ---------- From: Ond=C5=99ej Sur=C3=BD Date: Wed, Feb 1, 2012 at 08:40 Subject: Upcoming transition of php5 to 5.4 To: Debian Release Hi, this is just a heads up that we would like to ship wheezy with php5 5.4 which is in upstream RC phase now (and in debian-experimental). It introduce a couple of incompatible changes (for a full list see attached UPGRADING file), most notably (not listing minor changes and added features= ): - default charset is now utf-8 - magic_quotes are deprecated (with warning) - safe_mode and register_globals was removed - three new reserved words: callable, insteadof and trait - multibyte support is now default - removed syntax (break $var, continue $var) - sqlite(1) extension was removed (already done in php5.3 in Debian) I am inclined to let the current php5 in unstable to transition to testing and then upload next 5.4.0 RC to unstable with transition blocking bug, so we can start testing existing software as soon as possible. I also plan to provide "official" backports for Debian squeeze, so people can come and test new php5.4 before they upgrade to wheezy. Final note: We already had similar transitions in php (4->5, 5.2->5.3, etc.= ), so it's not really a big deal, but it will require some amount of work henc= e this email. Ondrej P.S.: Please Cc: me as I am not subscribed to the list (but I do check the web archives). -- =EF=BB=BFOnd=C5=99ej Sur=C3=BD --=20 =EF=BB=BFOnd=C5=99ej Sur=C3=BD