Newsgroups: php.internals Path: news.php.net Xref: news.php.net php.internals:89320 Return-Path: Mailing-List: contact internals-help@lists.php.net; run by ezmlm Delivered-To: mailing list internals@lists.php.net Received: (qmail 32504 invoked from network); 23 Nov 2015 09:35:38 -0000 Received: from unknown (HELO lists.php.net) (127.0.0.1) by localhost with SMTP; 23 Nov 2015 09:35:38 -0000 Authentication-Results: pb1.pair.com header.from=derick@php.net; sender-id=unknown Authentication-Results: pb1.pair.com smtp.mail=derick@php.net; spf=unknown; sender-id=unknown Received-SPF: unknown (pb1.pair.com: domain php.net does not designate 82.113.146.227 as permitted sender) X-PHP-List-Original-Sender: derick@php.net X-Host-Fingerprint: 82.113.146.227 xdebug.org Linux 2.6 Received: from [82.113.146.227] ([82.113.146.227:57681] helo=xdebug.org) by pb1.pair.com (ecelerity 2.1.1.9-wez r(12769M)) with ESMTP id 83/65-01565-6EDD2565 for ; Mon, 23 Nov 2015 04:35:37 -0500 Received: from [10.214.79.213] (unknown [185.69.145.196]) by xdebug.org (Postfix) with ESMTPSA id 587C0E20DC; Mon, 23 Nov 2015 09:35:28 +0000 (GMT) User-Agent: K-9 Mail for Android In-Reply-To: <5652D782.40601@lerdorf.com> References: <112FFBCD-8445-40BC-B92F-3A97D3E97C4C@zend.com> <56523F74.9040708@lerdorf.com> <06a601d125c0$99d5cfd0$cd816f70$@belski.net> <5652D782.40601@lerdorf.com> MIME-Version: 1.0 Content-Transfer-Encoding: 8bit Content-Type: text/plain; charset=UTF-8 Date: Mon, 23 Nov 2015 10:35:25 +0100 To: Rasmus Lerdorf ,Phil Sturgeon ,Xinchen Hui CC: Joe Watkins ,Anatol Belski ,Anthony Ferrara ,Zeev Suraski ,PHP internals Message-ID: Subject: Re: [PHP-DEV] INDRECT in arrays causes count() to become unpredictable From: derick@php.net (Derick Rethans) On November 23, 2015 10:08:18 AM GMT+01:00, Rasmus Lerdorf wrote: >On 11/23/2015 09:49 AM, Phil Sturgeon wrote: >> The "There will always be bugs" argument is a strawman, nobody is >> saying wait until it's perfect. >> >> People in this thread are consistently conflating "there will always >> be bugs" with "lets just ignore this bug which is 'around critical' >> and crack on because yolo." > >You seem to be confused Phil. Nobody is arguing that this bug shouldn't >be fixed. The question is all about how severe it is and whether it >should trigger another release candidate. > Do I understand that you'd like to release 7.0.0 as 7.0.0RC7 + the count fix on Thursday? I don't think we should push out 7.0.0 without the count fix, but I also don't think it warrants another RC. If people think it needs another RC, then perhaps do one on Thu 26th with just RCA+ count fix, plus final on Thu Dec 3rd? cheers, Derick