Newsgroups: php.internals Path: news.php.net Xref: news.php.net php.internals:74903 Return-Path: Mailing-List: contact internals-help@lists.php.net; run by ezmlm Delivered-To: mailing list internals@lists.php.net Received: (qmail 55576 invoked from network); 14 Jun 2014 12:45:39 -0000 Received: from unknown (HELO lists.php.net) (127.0.0.1) by localhost with SMTP; 14 Jun 2014 12:45:39 -0000 Authentication-Results: pb1.pair.com header.from=johannes@schlueters.de; sender-id=unknown Authentication-Results: pb1.pair.com smtp.mail=johannes@schlueters.de; spf=permerror; sender-id=unknown Received-SPF: error (pb1.pair.com: domain schlueters.de from 217.114.215.10 cause and error) X-PHP-List-Original-Sender: johannes@schlueters.de X-Host-Fingerprint: 217.114.215.10 mail.experimentalworks.net Received: from [217.114.215.10] ([217.114.215.10:33395] helo=mail.experimentalworks.net) by pb1.pair.com (ecelerity 2.1.1.9-wez r(12769M)) with ESMTP id 0F/67-03909-1F34C935 for ; Sat, 14 Jun 2014 08:45:38 -0400 Received: from [192.168.2.31] (ppp-93-104-11-11.dynamic.mnet-online.de [93.104.11.11]) (using TLSv1 with cipher ECDHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) (Authenticated sender: johannes@schlueters.de) by mail.experimentalworks.net (Postfix) with ESMTPSA id 3039B40F1E; Sat, 14 Jun 2014 14:45:38 +0200 (CEST) To: Stas Malyshev Cc: PHP Internals In-Reply-To: <539B8B74.6030707@sugarcrm.com> References: <539B8B74.6030707@sugarcrm.com> Content-Type: text/plain; charset="UTF-8" Date: Sat, 14 Jun 2014 14:45:07 +0200 Message-ID: <1402749907.2546.1705.camel@guybrush> Mime-Version: 1.0 X-Mailer: Evolution 2.30.3 Content-Transfer-Encoding: 7bit Subject: Re: [PHP-DEV] 5.3 final release From: johannes@schlueters.de (Johannes =?ISO-8859-1?Q?Schl=FCter?=) Hi, On Fri, 2014-06-13 at 16:38 -0700, Stas Malyshev wrote: > As decided in https://wiki.php.net/rfc/php53eol, 5.3 EOL is 1 year after > the 5.5.0 release, which is on June 20th. Do we want to make one last > release before EOL with latest security patches (probably in sync with > 5.4/5.5 releases planned for June 29)? If so, I can scan the logs and > backport the recent security-relevant patches. Last 5.3 was half a year > ago so we probably have some, even with remote exploit potential. The last time this was discussed on security@ I intended for "having one release in July to send 5.3 to eternal sleep" I still plan to do that. I won't directly sync with 5.4/5.5, though (unless there is a critical issue requiring this) to have different news. I expect this final EOL to receive more media echo which shouldn't hide other releases. If there are specific changes you want to see in there please send a note to me (cc security@), I'll check myself, too. johannes