Newsgroups: php.internals Path: news.php.net Xref: news.php.net php.internals:52144 Return-Path: Mailing-List: contact internals-help@lists.php.net; run by ezmlm Delivered-To: mailing list internals@lists.php.net Received: (qmail 555 invoked from network); 9 May 2011 08:04:20 -0000 Received: from unknown (HELO lists.php.net) (127.0.0.1) by localhost with SMTP; 9 May 2011 08:04:20 -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; domainkeys=bad Received-SPF: pass (pb1.pair.com: domain gmail.com designates 209.85.215.42 as permitted sender) DomainKey-Status: bad X-DomainKeys: Ecelerity dk_validate implementing draft-delany-domainkeys-base-01 X-PHP-List-Original-Sender: tyra3l@gmail.com X-Host-Fingerprint: 209.85.215.42 mail-ew0-f42.google.com Received: from [209.85.215.42] ([209.85.215.42:40603] helo=mail-ew0-f42.google.com) by pb1.pair.com (ecelerity 2.1.1.9-wez r(12769M)) with ESMTP id 7D/B1-20726-400A7CD4 for ; Mon, 09 May 2011 04:04:20 -0400 Received: by ewy2 with SMTP id 2so1465059ewy.29 for ; Mon, 09 May 2011 01:04:17 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:mime-version:sender:in-reply-to:references:date :x-google-sender-auth:message-id:subject:from:to:cc:content-type; bh=tmN+MVofEJ9w/spvbRxXizAvmWvTLTzjLiKgsHGkw5M=; b=O9TvzRlPgHDubzFfq9V5JQTqgQ2xenCdxKy8XOrJ0YdEwg9z9JdhnjjhRLns3Qd9Rr xFLqFa3Bj3FO3c8vtgU8F0wPuTjxzxmI9aa1Mora5LIbto7uR/Aabj2jdu7vV6rteVu1 Grw0dEg9Bt0sg8brPvveaxo4OeWGr5gyamwWs= DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=mime-version:sender:in-reply-to:references:date :x-google-sender-auth:message-id:subject:from:to:cc:content-type; b=vPDNNGhUU3V98bXm0rtwg8gALyGntIAdRLXYFNvrNtbIO2nLbnknnSwiEn57KNlLdQ TKDmtHbgNGkWwA+M7xWaVqpqcEFu598OyZWysftHYsxEfU+/n5r8KpKvqWhSWbGgOMXc Jbq4HUzcArByK/yv/1qvySJuKT9LunuMJlAew= MIME-Version: 1.0 Received: by 10.14.15.15 with SMTP id e15mr534093eee.231.1304928257124; Mon, 09 May 2011 01:04:17 -0700 (PDT) Sender: tyra3l@gmail.com Received: by 10.14.127.79 with HTTP; Mon, 9 May 2011 01:04:17 -0700 (PDT) In-Reply-To: <4D53AF3A-BAFA-4816-9C06-694C0435D88A@stefan-marr.de> References: <4DC729EE.9090600@sugarcrm.com> <4DC75FFF.40008@lerdorf.com> <4DC79CB9.6090201@sugarcrm.com> <4D53AF3A-BAFA-4816-9C06-694C0435D88A@stefan-marr.de> Date: Mon, 9 May 2011 10:04:17 +0200 X-Google-Sender-Auth: IVCzSAM3euqX_q8v0obLRR7lSLE Message-ID: To: Stefan Marr Cc: Stas Malyshev , PHP Internals Content-Type: multipart/alternative; boundary=0016e65a0f983928ff04a2d34953 Subject: Re: [PHP-DEV] 5.4 again From: info@tyrael.hu (Ferenc Kovacs) --0016e65a0f983928ff04a2d34953 Content-Type: text/plain; charset=UTF-8 On Mon, May 9, 2011 at 10:00 AM, Stefan Marr wrote: > Hi: > > On 09 May 2011, at 09:50, Stas Malyshev wrote: > > > I'm all for this idea, but the question is - can we have a good design & > implementation in next 2 months? If we can, great, if we can't - I'd rather > have 5.4 than wait for it. E.g., if we have somebody ready to commit for > certain timeframe to come up with it, then it makes sense to discuss it in > this context. > > Can't we just draw this arbitrary line in the sand, and say from now on, > controversial things are taken out and nothing new is added anymore? > > Everything which is not yet in trunk and is not required to round up the > release should go into the release after 5.4? > > For me it seems there is no progress because there is still to much > opportunity to improve things... > So, instead of allowing to nominate new features, it might be best to stick > to what we have now, and restrict ourselves to sort out the controversial > stuff. > > I think that it would be nice to have a short timeframe before feature freeze. Tyrael --0016e65a0f983928ff04a2d34953--