Newsgroups: php.internals Path: news.php.net Xref: news.php.net php.internals:79596 Return-Path: Mailing-List: contact internals-help@lists.php.net; run by ezmlm Delivered-To: mailing list internals@lists.php.net Received: (qmail 52654 invoked from network); 12 Dec 2014 14:07:57 -0000 Received: from unknown (HELO lists.php.net) (127.0.0.1) by localhost with SMTP; 12 Dec 2014 14:07:57 -0000 Authentication-Results: pb1.pair.com header.from=tyra3l@gmail.com; sender-id=pass Authentication-Results: pb1.pair.com smtp.mail=tyra3l@gmail.com; spf=pass; sender-id=pass Received-SPF: pass (pb1.pair.com: domain gmail.com designates 209.85.212.172 as permitted sender) X-PHP-List-Original-Sender: tyra3l@gmail.com X-Host-Fingerprint: 209.85.212.172 mail-wi0-f172.google.com Received: from [209.85.212.172] ([209.85.212.172:39537] helo=mail-wi0-f172.google.com) by pb1.pair.com (ecelerity 2.1.1.9-wez r(12769M)) with ESMTP id 10/E4-18848-DB6FA845 for ; Fri, 12 Dec 2014 09:07:57 -0500 Received: by mail-wi0-f172.google.com with SMTP id n3so2622114wiv.5 for ; Fri, 12 Dec 2014 06:07:54 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type; bh=pPW8v48uoOhMZtfDXWi9w50TlQYDU8qnZhjsCBVNk1A=; b=PeWPWlAAS9bQIMOQ4v+5JYnA7LM8vsPnoDIyZYbAnMmjJqbtb7ixTQJp1Rd7ZAEpuY X5kKY5JZT+HzBkE40Kv9xANJg7gExfYhuxv+xkoJWwFTKPIVgDGRMPqh6BIHr/Bb3C3m zGB94KWHg0xpCw/15tss0mLku8YLgMEqZPiWURPqI/ICQnF3bMra/AxGOj0gAs1B4pcW SiPVygU/CcqeyGY++a1J5Z81Q4cWbaDcKEFD9dQ7JD+V7/Ol6aYysGexz2jahCs9Cafp fn1fU8gWiXNDax+cuhWAU8M22TSjkK1HItSlemYXUE4xLv1A8zd8V8cEAnPtG0BW5MR0 j7jQ== MIME-Version: 1.0 X-Received: by 10.180.7.198 with SMTP id l6mr8159311wia.26.1418393274548; Fri, 12 Dec 2014 06:07:54 -0800 (PST) Received: by 10.180.88.33 with HTTP; Fri, 12 Dec 2014 06:07:54 -0800 (PST) In-Reply-To: References: Date: Fri, 12 Dec 2014 15:07:54 +0100 Message-ID: To: Julien Pauli Cc: PHP Internals Content-Type: multipart/alternative; boundary=f46d044287c0480a6d050a056b4e Subject: Re: [PHP-DEV] On the road to PHP 5.7 , or not ? From: tyra3l@gmail.com (Ferenc Kovacs) --f46d044287c0480a6d050a056b4e Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: quoted-printable On Fri, Dec 12, 2014 at 2:45 PM, Julien Pauli wrote: > > Hi people. > > Ferenc and I, actual RM of 5.5 and 5.6 , were discussing the calendar tod= ay > on IRC. > > Let's start with facts : > > - We release new PHP versions (major or minor) on summer. Usually, if we > can have it end of June, it is good. > - We may delay that, 5.6 got released end of summer : in september. It is > bad, but acceptable. > Lies, it was released at the end of August. :P > - We always have, from our release process, *2 active versions at the sam= e > time + 1 sec fix version*. Not more, not less. > > > If we release during summer, that means we need to prepare everything > around Christmas. > Tip : Christmax is approaching :-) > > > So the main question is : *What version will we release next year ?* > > Will we have a PHP 5.7, or jump directly to a 7.0 ? > > > Don't forget, that if we go for a 5.7 , then we won't have a 7.0 at least > one year later. > If not : we'll happen having 3 active versions (5.6 , 5.7 and 7.0) and on= e > sec-fix only (5.5) , *this is something we don't want* , because we have > the feeling that it is too much pain to maintain so many versions alive. > > > - If we go for 7.0 : > I wouldn't mind delaying its release to November(2015) if needed, its a > major, extra care should be taken. However, not later : our release proce= ss > status for 2 years of active life , if 7.0 were to be released in 2016, > then we'd have 5.5 lasting for much more than 2 years active. > > - If we go for 5.7 : > We could release it this summer (2015) , but that would mean that 7.0 > wouldn't come before summer 2016. > Releasing a 5.7 will lean the release cycle curve, but it is not mandator= y, > that should be debatted. > > > Decisions should be taken now : aka in 2014. > Taking decisions later than this will lead to a rush in release process, > wich is very bug/error prone, and should be prevented. > > > Thank you. > > Julien.Pauli > it would be also possible to release 5.7 and 7.0 in parallel, and I know that some people were against this, as this would mean less effort going into 7.0, but to be honest, I think that it would only mean that instead of continuing to accept small self contained features to 5.6.x (which we already have a couple and people are we are still have a bunch more requested/worked on already), we would turn 5.5/5.6 into mostly bugfix status and push those small features into 5.7 instead. Given the past trends about the penetration of new major(ish) php versions, I'm fairly sure that when 5.6 gets EOLed, there will be plenty of people/projects who will not be ready to migrate to PHP7 yet, so I think that one way or another, 5.6 won't be the last minor version in the PHP 5 family. If we can agree on that, I think it would make sense to have an 5.7 released a bit before or together with 7.0, which can be used as a stepping stone for migrating 7.0: we could make sure that anything which will be changed/removed in 7.0 is properly deprecated in 5.7, so you will do two smaller steps instead of one big one. --=20 Ferenc Kov=C3=A1cs @Tyr43l - http://tyrael.hu --f46d044287c0480a6d050a056b4e--