Newsgroups: php.internals Path: news.php.net Xref: news.php.net php.internals:89310 Return-Path: Mailing-List: contact internals-help@lists.php.net; run by ezmlm Delivered-To: mailing list internals@lists.php.net Received: (qmail 12896 invoked from network); 23 Nov 2015 07:56:37 -0000 Received: from unknown (HELO lists.php.net) (127.0.0.1) by localhost with SMTP; 23 Nov 2015 07:56:37 -0000 Authentication-Results: pb1.pair.com header.from=pthreads@pthreads.org; sender-id=unknown Authentication-Results: pb1.pair.com smtp.mail=pthreads@pthreads.org; spf=permerror; sender-id=unknown Received-SPF: error (pb1.pair.com: domain pthreads.org from 209.85.160.178 cause and error) X-PHP-List-Original-Sender: pthreads@pthreads.org X-Host-Fingerprint: 209.85.160.178 mail-yk0-f178.google.com Received: from [209.85.160.178] ([209.85.160.178:34792] helo=mail-yk0-f178.google.com) by pb1.pair.com (ecelerity 2.1.1.9-wez r(12769M)) with ESMTP id AC/D1-01565-4B6C2565 for ; Mon, 23 Nov 2015 02:56:36 -0500 Received: by ykfs79 with SMTP id s79so230138005ykf.1 for ; Sun, 22 Nov 2015 23:56:33 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=pthreads-org.20150623.gappssmtp.com; s=20150623; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type; bh=c4auIbzKdl7hKWQd/riFAk/Gzli3EscCNkOjV4LLvcU=; b=lHxRioc5udLqlOMIXnrhq36qnSNUuYU0O0FyNwzOBuoCQgvvfBSQCnXL2fyX1/5Fxx v9BqUnX8r2IzOkM/gourVpg112XeoV2qkFTc9q3yVaOSseTkUpMGv/ZOEskIR1NW0O7y AW9okHNjBvI3PVsTyLYJqjLt/D9to6hGHfJBtCFJtk6qdi0hW6eOJDWO+7bv1PSIcPd5 Cu9EVzlk5AzAnTdXlJI5H8NRAQ8A+34ZPMC1dymckZm8f7Y/G3CjGehvOWnNCg9m1Y4a 2vqRH6ARZwvym2Z2ohWcuikD0BHNZ4i9zOT0H9Amnfm1bEv6vkBF79ATJO7lQkQaQXfA 0qTQ== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20130820; h=x-gm-message-state:mime-version:in-reply-to:references:date :message-id:subject:from:to:cc:content-type; bh=c4auIbzKdl7hKWQd/riFAk/Gzli3EscCNkOjV4LLvcU=; b=FiTbVsOoqJ0NiPGwH8YXRzNG3RXfCjOPAZnSYxhefT/Fzpv9poFJMBdTXWE2XnjnGz mbKRNeRYYNLHMwctx68d5rmu4PzohiFR/9H5zKDUrGUizY6132ReNkHgsH/CcaWB2U4D Jhkw9AUpiSGz9cmBOEHfwYRxwl1SAIGl5NZSPoggyVZBznSwz/V6DshuTSSbVegwZqV0 NwN42nRTjtYxEmqyL00SeRgK/yooisMPS0isi7E/XbHD0XgLGwWvLmsMY1PynnKO2Eae 7GGs5m9UG3/qLD/hQ0eHGY8nKjg9prLnTZr/WDKhFjgCEpqTYEYZQSQ58NXxmM8Jmn1o 6rlA== X-Gm-Message-State: ALoCoQmu7msjHS7V9/imzNPhtcdOPY23DRmCSlihm/yPnab1PH8ltCi/CioXAs1cV9L8rb4s/mIh MIME-Version: 1.0 X-Received: by 10.13.209.199 with SMTP id t190mr26132699ywd.265.1448265393709; Sun, 22 Nov 2015 23:56:33 -0800 (PST) Received: by 10.13.218.1 with HTTP; Sun, 22 Nov 2015 23:56:33 -0800 (PST) X-Originating-IP: [165.120.229.121] In-Reply-To: References: <112FFBCD-8445-40BC-B92F-3A97D3E97C4C@zend.com> <56523F74.9040708@lerdorf.com> <06a601d125c0$99d5cfd0$cd816f70$@belski.net> Date: Mon, 23 Nov 2015 07:56:33 +0000 Message-ID: To: Anatol Belski Cc: Rasmus Lerdorf , Anthony Ferrara , Zeev Suraski , PHP internals Content-Type: multipart/alternative; boundary=001a114e48c055554b05253090ba Subject: Re: [PHP-DEV] INDRECT in arrays causes count() to become unpredictable From: pthreads@pthreads.org (Joe Watkins) --001a114e48c055554b05253090ba Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: quoted-printable I may have misunderstood, will this be fixed before GA or not ? Cheers Joe On Mon, Nov 23, 2015 at 7:52 AM, Joe Watkins wrote: > Morning Anatol, > > > People that don't test RC won't start to test any later RC anyway. > > This wasn't reported by "people", this was found by one of us. > > The problem isn't only that we have a bug in symbol tables, the problem i= s > that the bug was found so very late in the process. > > We cannot reasonably have confidence that no other such bugs exist. > > I think it doesn't make sense to push forward with the current release > time table now. I think it makes sense to do another RC and give *us* a > little bit longer to test. > > Please reconsider. > > Cheers > Joe > > > On Mon, Nov 23, 2015 at 7:28 AM, Anatol Belski > wrote: > >> Hi, >> >> > -----Original Message----- >> > From: Rasmus Lerdorf [mailto:rasmus@lerdorf.com] >> > Sent: Sunday, November 22, 2015 11:20 PM >> > To: Anthony Ferrara ; Zeev Suraski >> > Cc: internals@lists.php.net >> > Subject: Re: [PHP-DEV] INDRECT in arrays causes count() to become >> > unpredictable >> > >> > On 11/22/2015 06:18 AM, Anthony Ferrara wrote: >> > > Zeev, >> > > >> > > On Sat, Nov 21, 2015 at 11:52 PM, Zeev Suraski wrote= : >> > >> >> > >>> On 22 =D7=91=D7=A0=D7=95=D7=91=D7=B3 2015, at 0:47, Anthony Ferrar= a >> wrote: >> > >>> >> > >>> I think this is significant enough to be a blocker to gold and tha= t >> > >>> we should fix it prior to release. >> > >>> >> > >>> Thoughts? >> > >>> >> > >> >> > >> IMHO, unless we think fixing this would require breaking binary >> compatibility >> > (which I don't think is the case) - this shouldn't block 7.0.0. 7.0.0 >> is a lot more >> > about getting people to start paying attention to 7.0 and start testin= g >> their >> > codebase against it - finding both the incompatibilities in their code >> and, >> > undoubtedly - the bugs we failed to find. I wish we could say this >> would be the >> > last issue we find in 7.0, but I think we can all agree it's wishful >> thinking... >> > > >> > > Consider that Distros may very well pick whatever we call stable for >> > > LTS releases. Meaning that non-critical (crash/security) bugs that w= e >> > > miss may wind up living on for a VERY long time. If we don't intend = .0 >> > > to be stable, then what's the point of versioning in the first place= ? >> > > >> > > Xinchen, >> > > >> > > Very interesting on the fix. I do think it's important for this to >> > > land with 7, but at least we can have the discussion. >> > >> > I agree with Zeev here and I had a chat with Anatol about this tonight= . >> > This is a .0.0 release. Nobody is going to take a .0.0 and push it >> straight to >> > production. And it is not going to part of any sort of LTS distro >> either. It's not like >> > LTS distros don't pick up point releases. >> > There is no way we will go 2 weeks without finding something for quite >> a while >> > still which can drag things out indefinitely. The question is whether >> this is >> > significant enough to postpone further. Personally I don't think it is= . >> Let's get >> > 7.0.0 out the door and get ourselves on track for regular point >> releases without >> > any of this "perfect-release" >> > stress. >> > >> From what I was merging for 7.0.0, I see that there are quite some >> primitive bug fixes, a couple of non critical 7.0 bugs and 2 bugs merged= up >> from 5.6. The issue with the symtable counter stands at some point aroun= d >> the critical border. I personally would see it as not crossing that bord= er. >> >> So based on this, I'd rather go by releasing. The bug list after RC7 >> looks pretty much like a regular patch release, or even better. Comparin= g >> to RC6 where it was started to be tested obviously some more intensively= , >> RC7 looks more like lost attention. We could go with more RC, sure. Howe= ver >> in that case IMO we would catch bugs at very low speed with no guarantee= we >> have a good thing at the end when we "think" it's good. This will cause = us >> to defer things for much longer time. Releasing on 26th (or on 3rd with >> respect to Thanksgiving, if there are still strong concerns) were IMHO >> convenient for this reasons. >> >> People that don't test RC won't start to test any later RC anyway. Peopl= e >> that don't test RC will start to use GA and that will lead to bug repor= ts, >> in any case. So IMHO at this point we are good enough to do the first >> release with all the known bugs fixed, with the knowledge that no critic= al >> bugs are present, with the knowledge that community projects like Drupal= 8, >> Symfony, etc. report the green tests, and with intention to get people >> waiting for GA involved. >> >> Regards >> >> Anatol >> >> >> >> >> -- >> PHP Internals - PHP Runtime Development Mailing List >> To unsubscribe, visit: http://www.php.net/unsub.php >> >> > --001a114e48c055554b05253090ba--