Newsgroups: php.internals Path: news.php.net Xref: news.php.net php.internals:89824 Return-Path: Mailing-List: contact internals-help@lists.php.net; run by ezmlm Delivered-To: mailing list internals@lists.php.net Received: (qmail 39135 invoked from network); 16 Dec 2015 14:57:17 -0000 Received: from unknown (HELO lists.php.net) (127.0.0.1) by localhost with SMTP; 16 Dec 2015 14:57:17 -0000 Authentication-Results: pb1.pair.com smtp.mail=tyra3l@gmail.com; spf=pass; sender-id=pass Authentication-Results: pb1.pair.com header.from=tyra3l@gmail.com; sender-id=pass Received-SPF: pass (pb1.pair.com: domain gmail.com designates 74.125.82.49 as permitted sender) X-PHP-List-Original-Sender: tyra3l@gmail.com X-Host-Fingerprint: 74.125.82.49 mail-wm0-f49.google.com Received: from [74.125.82.49] ([74.125.82.49:34974] helo=mail-wm0-f49.google.com) by pb1.pair.com (ecelerity 2.1.1.9-wez r(12769M)) with ESMTP id 11/A6-51216-CCB71765 for ; Wed, 16 Dec 2015 09:57:16 -0500 Received: by mail-wm0-f49.google.com with SMTP id l126so42172384wml.0 for ; Wed, 16 Dec 2015 06:57:16 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:sender:in-reply-to:references:date:message-id:subject :from:to:cc:content-type; bh=Kphk7SsFTt0vIla8UgiJ8l70B3K/7h4jyz4U1/tm1g8=; b=VMoPzbuvfWaLROt/ntsd1nJxEoJxSBzOOYwkCqYtdfhOxzonlNUv6aH7OuKZv+6ZvK fSPqJIFBZdr11v/bq9csE5n4zFsXLjyW8TTAt2vQrpFbqa3fZXnrvT9DTKwcR+ElWNSu TWviZgjkZWTSMSqJUAxlZkhk/jxbiF/ct2ktpgiD0NvpHkc4uDITQpWiN0V+C+MRgjza ut1eH7LCOG0AGHcbwrHYsVXNzKW53EIiVTAmX/70r+/nPfp3zOyP8hGFXJ33PylUQF+A Y941Q8zP64jTT+OKhd0OTQvttJhH/OEOnYqp82I8vRNwvwGDBss382eqEM78cJNhqr6H 0emQ== MIME-Version: 1.0 X-Received: by 10.195.12.163 with SMTP id er3mr52142380wjd.135.1450277834180; Wed, 16 Dec 2015 06:57:14 -0800 (PST) Sender: tyra3l@gmail.com Received: by 10.27.56.84 with HTTP; Wed, 16 Dec 2015 06:57:14 -0800 (PST) In-Reply-To: <566F56EB.7070601@gmail.com> References: <000c01d12fa0$384b8040$a8e280c0$@belski.net> <082001d131ac$ab522b80$01f68280$@belski.net> <5666C73B.1050407@php.net> <566F56EB.7070601@gmail.com> Date: Wed, 16 Dec 2015 15:57:14 +0100 X-Google-Sender-Auth: eZdQr72XmrXrfVy-vR2McQdKsQs Message-ID: To: Julien Pauli Cc: Remi Collet , PHP Internals , Anatol Belsky , Stanislav Malyshev , Stanislav Malyshev Content-Type: multipart/alternative; boundary=047d7bf0d96621cde30527051fd4 Subject: Re: [PHP-DEV] Re: PHP 7.0.1 scheduling From: tyrael@php.net (Ferenc Kovacs) --047d7bf0d96621cde30527051fd4 Content-Type: text/plain; charset=UTF-8 On Tue, Dec 15, 2015 at 12:55 AM, Stanislav Malyshev wrote: > Hi! > > > Why not use RC2 as a chance for some security patches to get tested ? > > If we have a RC2 (which is not bad IMO, we have a time slice here at > > end of 2015 that enables us to release an RC2) , we then could merge > > into this one some well-selected security patches, f.e, some that are > > *low* classified , aka that can't get trigerred remotely by user > > payload. > > Generally, if we publish security patch we should release ASAP, as > having public unpatched security issue is bad. Fortunately, the issue > disclosed is not that bad, I'd even doubt it is security issue per se, > as I see no real way to trigger it without code access (it may be I miss > something though). > > Accelerating the schedule is OK with me (as is keeping the current one, > too) but please do not forget to merge pending patches (or please tell > me when you want me to merge them). > > Thanks, > -- > Stas Malyshev > smalyshev@gmail.com > so Anatol already tagged 7.0.1, I'm waiting with the 5.6.17 tag for Julien to tag 5.5.31. Julien what is the status there? --047d7bf0d96621cde30527051fd4--