Newsgroups: php.internals Path: news.php.net Xref: news.php.net php.internals:70617 Return-Path: Mailing-List: contact internals-help@lists.php.net; run by ezmlm Delivered-To: mailing list internals@lists.php.net Received: (qmail 96252 invoked from network); 13 Dec 2013 06:56:42 -0000 Received: from unknown (HELO lists.php.net) (127.0.0.1) by localhost with SMTP; 13 Dec 2013 06:56:42 -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 209.85.128.49 as permitted sender) X-PHP-List-Original-Sender: tyra3l@gmail.com X-Host-Fingerprint: 209.85.128.49 mail-qe0-f49.google.com Received: from [209.85.128.49] ([209.85.128.49:39204] helo=mail-qe0-f49.google.com) by pb1.pair.com (ecelerity 2.1.1.9-wez r(12769M)) with ESMTP id 7E/D9-32587-7AFAAA25 for ; Fri, 13 Dec 2013 01:56:39 -0500 Received: by mail-qe0-f49.google.com with SMTP id w7so1259378qeb.36 for ; Thu, 12 Dec 2013 22:56:37 -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=KzR//mr0Y7I08kXsOrHva3PqVE8xetrq08BCFzYfM1U=; b=y1Qwq/iwoWgAhdbVsF6HyuwgPPjnNljwWpB8yf0u5uUnctFM650RtYlDEVdDwczNad fFIyzil+Szd8JtUNgXn9hr96ExsZUURXgI+EbYtKrwZh6DvFZtMBsimY1V5F9xrlViDg o3/gGGxafMBreFdzbAZluFwp5847K84fjRiuqjMLB0dwHP49rwuyLKTd3q6D5coh9y6W p3azZ9XezMC0WaYk8a1nz5lEEq5ZlVo8SYN8m0PyBy9MeSJNhh50LQOvxZRMAFIGHkZF 5KN6aBcYQVMwmtJe5EiW0fYqum5c5Jt/dOOPzgLITJjIHTmV30VQ/YBJJgA22wqy5v/G f52Q== MIME-Version: 1.0 X-Received: by 10.224.28.72 with SMTP id l8mr1663234qac.35.1386917797401; Thu, 12 Dec 2013 22:56:37 -0800 (PST) Sender: tyra3l@gmail.com Received: by 10.140.37.179 with HTTP; Thu, 12 Dec 2013 22:56:37 -0800 (PST) Received: by 10.140.37.179 with HTTP; Thu, 12 Dec 2013 22:56:37 -0800 (PST) In-Reply-To: References: Date: Fri, 13 Dec 2013 07:56:37 +0100 X-Google-Sender-Auth: Fjp1X937tiw3kSfJBjVfSXpcnOw Message-ID: To: Adam Harvey Cc: PHP Internals , David Soria Parra , julien pauli Content-Type: multipart/alternative; boundary=001a11c1c9a6a59c5204ed64f649 Subject: Re: [PHP-DEV] Proposed timetable for PHP 5.6.0 From: tyrael@php.net (Ferenc Kovacs) --001a11c1c9a6a59c5204ed64f649 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: quoted-printable 2013.12.12. 19:48, "Adam Harvey" ezt =C3=ADrta: > > On 12 December 2013 04:23, Ferenc Kovacs wrote: > > As you probably all remember the first beta usually means feature freeze, > > so no new additions are allowed, only fixes, so the code can stabilize in > > the beta and RC phase. > > Learning from the past we would also like to introduce a new rule about not > > accepting new RFCs targeting 5.6.0 after the first alpha is shipped, > > because given the discussion and voting period it can force us into a spot > > where we have to chose between > > I like this: +1. > > If it works well, then we probably want to announce the calendar a > little earlier for the 2015 release, since there's now a pretty narrow > window to propose an RFC and have it voted on before January 16. By my > estimation, an RFC will have to enter "in discussion" by December 26 > (hope nobody has plans over the holidays) to be accepted for PHP 5.6, > assuming minimal two week discussion and one week voting periods. Nope, you can introduce RFCs until the first alpha, RFCs under discussion or under voting are allowed to be added (until the first beta). Ofc. this still leaves with only a month, which also includes chirstmas/new year so not that much time, but we are already a bit behind schedule. > > Adam "Christmas Grinch" Harvey > > PS: You'll all note how careful I was to avoid assigning a version > number to the 2015 release. :) --001a11c1c9a6a59c5204ed64f649--