Newsgroups: php.internals Path: news.php.net Xref: news.php.net php.internals:50514 Return-Path: Mailing-List: contact internals-help@lists.php.net; run by ezmlm Delivered-To: mailing list internals@lists.php.net Received: (qmail 11971 invoked from network); 25 Nov 2010 10:40:27 -0000 Received: from unknown (HELO lists.php.net) (127.0.0.1) by localhost with SMTP; 25 Nov 2010 10:40:27 -0000 X-Host-Fingerprint: 217.114.211.68 unknown Date: Thu, 25 Nov 2010 05:40:26 -0500 Received: from [217.114.211.68] ([217.114.211.68:4078] helo=localhost.localdomain) by pb1.pair.com (ecelerity 2.1.1.9-wez r(12769M)) with ESMTP id AA/15-20008-81D3EEC4 for ; Thu, 25 Nov 2010 05:40:26 -0500 To: internals@lists.php.net References: User-Agent: slrn/0.9.9p1 (SunOS) Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Message-ID: X-Posted-By: 217.114.211.68 Subject: Re: Hold off 5.4 From: dsp@php.net (David Soria Parra) On 2010-11-23, Felipe Pena wrote: > --001636eef065b3eaf30495ae5198 > Content-Type: text/plain; charset=UTF-8 > > Given the current state of trunk, I think 5.4 release process should > not begin tomorrow (alpha or whatever other status). There are > numerous identified issues that we need to fix before even think to > begin with a release. For example: > > - type hinting (or strict hinting) > - no consensus > - the RFCs are unclear > - BC break introduced > . classes named as any of the type hint scalar types > do not work anymore > aka class int {} As Matthew pointed out, I consider this a pretty grave BC break. > - Traits may not be ready yet for pre-release > - see http://svn.php.net/viewvc?view=revision&revision=298348 > - APC support > > - There are many changes not BC with 5.x, as we allowed them for the > development tree, before 5.4 was even a topic > > - APC is not yet bundled. Having the opcode bundle can raise issues by > one or another, we should have it in from the very 1st release > > - pecl/http was planned to be bundled. What's the status? > > We also have no plan about what will or will not be 5.4. This looks > familiar, this is exactly how we begun 5.3 and it tooks literally > years to be released. There is also actually no agreement to begin > with 5.4 now. > > 5.4 should be hold off until we solved the listed issues and the > release management RFC gets discussed and hopefully approved. +1, I agree. We should hold 5.4 off until we have at least a sane release process and solve the type hinting question.