Newsgroups: php.internals Path: news.php.net Xref: news.php.net php.internals:89323 Return-Path: Mailing-List: contact internals-help@lists.php.net; run by ezmlm Delivered-To: mailing list internals@lists.php.net Received: (qmail 45012 invoked from network); 23 Nov 2015 11:22:23 -0000 Received: from unknown (HELO lists.php.net) (127.0.0.1) by localhost with SMTP; 23 Nov 2015 11:22:23 -0000 Authentication-Results: pb1.pair.com smtp.mail=julienpauli@gmail.com; spf=pass; sender-id=pass Authentication-Results: pb1.pair.com header.from=julienpauli@gmail.com; sender-id=pass Received-SPF: pass (pb1.pair.com: domain gmail.com designates 74.125.82.50 as permitted sender) X-PHP-List-Original-Sender: julienpauli@gmail.com X-Host-Fingerprint: 74.125.82.50 mail-wm0-f50.google.com Received: from [74.125.82.50] ([74.125.82.50:33758] helo=mail-wm0-f50.google.com) by pb1.pair.com (ecelerity 2.1.1.9-wez r(12769M)) with ESMTP id F4/27-01565-FE6F2565 for ; Mon, 23 Nov 2015 06:22:23 -0500 Received: by wmec201 with SMTP id c201so155396879wme.0 for ; Mon, 23 Nov 2015 03:22:20 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:sender:in-reply-to:references:from:date:message-id :subject:to:cc:content-type:content-transfer-encoding; bh=I9Sd6R44b9xLCnijpmKB1X/zDkigVMN7C5Wi1V3NGOU=; b=E51syQIBOukpfydF8d6PhjYA+rNBllaBLLXqjfnTHSOZ81Itc8Spox0MTN71VAhfRj FSx+SS2i6rtyBlvG20l4UsYeHiMRxi6TFLLO/EhCsS3bzAHWOSlNgT5eSGaxBVMEbxwW syDna+Kh0Wfk6o52ywxNxIGlRLiQ80WD7Rc37Z1YiBHzWYFpyEhQ0CZ2eKufA7nprWCz gCi8yh2AtG+6NWWmhFDGjjd7dwpNazF4scPDjCxjpVsYXnfzfp6FSfPCwiawDVosZDoc Sm5r6vUCxh4QtZA5p53ykBBLCg9ZvTJa5Kq69g6HROyRc01xz4jW8u50g3/+XZRcaRxp vmiQ== X-Received: by 10.194.175.194 with SMTP id cc2mr29826506wjc.121.1448277740245; Mon, 23 Nov 2015 03:22:20 -0800 (PST) MIME-Version: 1.0 Sender: julienpauli@gmail.com Received: by 10.194.7.105 with HTTP; Mon, 23 Nov 2015 03:21:40 -0800 (PST) In-Reply-To: References: <112FFBCD-8445-40BC-B92F-3A97D3E97C4C@zend.com> <56523F74.9040708@lerdorf.com> <06a601d125c0$99d5cfd0$cd816f70$@belski.net> <5652D782.40601@lerdorf.com> Date: Mon, 23 Nov 2015 12:21:40 +0100 X-Google-Sender-Auth: zV12-d224CQWs8z4g-GesF32lHI Message-ID: To: Rasmus Lerdorf Cc: Derick Rethans , Phil Sturgeon , Xinchen Hui , Joe Watkins , Anatol Belski , Anthony Ferrara , Zeev Suraski , PHP internals Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: quoted-printable Subject: Re: [PHP-DEV] INDRECT in arrays causes count() to become unpredictable From: jpauli@php.net (Julien Pauli) On Mon, Nov 23, 2015 at 11:17 AM, Rasmus Lerdorf wrote= : > On Nov 23, 2015, at 10:35, Derick Rethans wrote: >> >>> 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? > > Yes > >> 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 wit= h just RCA+ count fix, plus final on Thu Dec 3rd? > > I am ok with either. I don't think the count fix is destabilizing enough = to warrant another RC. The fix seems simple and localized to me, but either= people are confused, or they genuinely feel strongly enough that this is i= ndicative of further problems and another RC will provide us with more time= to find similar issues or perhaps just give everyone a sense of confidence= in the release. > > There is also the fact that a lot of us are in Paris this week and and at= least some of us will be in transit on the 26th so a one-week delay might = be a good idea for that reason alone. I'am balanced. We discovered a bug, we have a fix , the fix is easy, self contained, reviewed by many eyes. So, we have all we need for a GA now, this week, no ? Pushing another RC is all right, but if we find new bugs in this RC, some that could be critical, then we'll postpone GA to January, because we'll then fall in mid-December, etc... We all have eyes, we all can spot bugs whenever we want to. Why another RC = now ? With another RC, we have time to concentrate on the code, OK, but we still have this time if we are in GA, as we'll have anyway a 7.0.1 coming shortly after... I'm not really +1 for another RC this week, but better for a GA. But that's my opinion... Julien.P