Newsgroups: php.internals Path: news.php.net Xref: news.php.net php.internals:70606 Return-Path: Mailing-List: contact internals-help@lists.php.net; run by ezmlm Delivered-To: mailing list internals@lists.php.net Received: (qmail 46766 invoked from network); 12 Dec 2013 18:48:16 -0000 Received: from unknown (HELO lists.php.net) (127.0.0.1) by localhost with SMTP; 12 Dec 2013 18:48:16 -0000 Authentication-Results: pb1.pair.com smtp.mail=adam@adamharvey.name; spf=pass; sender-id=pass Authentication-Results: pb1.pair.com header.from=adam@adamharvey.name; sender-id=pass Received-SPF: pass (pb1.pair.com: domain adamharvey.name designates 209.85.223.170 as permitted sender) X-PHP-List-Original-Sender: adam@adamharvey.name X-Host-Fingerprint: 209.85.223.170 mail-ie0-f170.google.com Received: from [209.85.223.170] ([209.85.223.170:48340] helo=mail-ie0-f170.google.com) by pb1.pair.com (ecelerity 2.1.1.9-wez r(12769M)) with ESMTP id 1F/91-32587-FE40AA25 for ; Thu, 12 Dec 2013 13:48:16 -0500 Received: by mail-ie0-f170.google.com with SMTP id qd12so1271505ieb.15 for ; Thu, 12 Dec 2013 10:48:12 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=adamharvey.name; s=google; h=mime-version:sender:in-reply-to:references:from:date:message-id :subject:to:cc:content-type; bh=/7kB25hEvZpUVX+LxV8D5qcvOZXzvTLBrpURpCxh+E4=; b=raOedXAIhnszxWUaboKeILUON4IrcsxEbTueovDy0+ZYP7NKs7G9URsoL+C6Zvq+8S kb7wO1WOEFw+kV86IcBEZkV/nfBN/jTstxQODB3+8/A4Aa0ylI7kgrHLiU1X2fpqVYWv xR9GW5n+xcK+mE2/IyNFKtCHQNWFMCFwnXcNk= X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20130820; h=x-gm-message-state:mime-version:sender:in-reply-to:references:from :date:message-id:subject:to:cc:content-type; bh=/7kB25hEvZpUVX+LxV8D5qcvOZXzvTLBrpURpCxh+E4=; b=aPodX333MDw8yz4DqO1ith16+sPq4/LP6VuysM/t40AoKGX5eY3nelljPFt+Ir05d8 D50VSH0jDAv2an1/5VqBA7DuJYce3y+Orl41LWnPFWDNkMTNytOKSv5DEAPzUze/S5+p BFVM7iZTkdsx0wTBPPl3r+mBVvHQEls/XUMLeiSqTnEicNRb0+ALYs0GJnQNuQy8Lj9K aMsMhqBTFmlqbqYyXcl+HUVI5M3rhq4FTmcD7h14Ed/5VspL0i5ZLan2TUFbpL19SE2m X43HaZ1pWiOqQO7Pvgl3ls0pGDP9GrCP2vqIbJdcer+4X38/QQjfCC5XTiyIdTMiN1al K1WQ== X-Gm-Message-State: ALoCoQmwaOv2b2zsXlbl7uDOXWoGoLeaL6Dwm0OHtYIf8HDKDHkUU93vKD2sdPXjIIm6Yx14xUfi X-Received: by 10.43.170.130 with SMTP id nq2mr7210613icc.69.1386874092505; Thu, 12 Dec 2013 10:48:12 -0800 (PST) MIME-Version: 1.0 Sender: adam@adamharvey.name Received: by 10.42.206.208 with HTTP; Thu, 12 Dec 2013 10:47:39 -0800 (PST) In-Reply-To: References: Date: Thu, 12 Dec 2013 10:47:39 -0800 X-Google-Sender-Auth: HHjryUjTGuG3Gjra67yDZuhs1Yc Message-ID: To: Ferenc Kovacs Cc: PHP Internals , julien pauli , David Soria Parra Content-Type: text/plain; charset=UTF-8 Subject: Re: [PHP-DEV] Proposed timetable for PHP 5.6.0 From: aharvey@php.net (Adam Harvey) 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. Adam "Christmas Grinch" Harvey PS: You'll all note how careful I was to avoid assigning a version number to the 2015 release. :)