Newsgroups: php.internals Path: news.php.net Xref: news.php.net php.internals:106753 Return-Path: Delivered-To: mailing list internals@lists.php.net Received: (qmail 35901 invoked from network); 28 Aug 2019 19:28:45 -0000 Received: from unknown (HELO mail-wr1-f46.google.com) (209.85.221.46) by pb1.pair.com with SMTP; 28 Aug 2019 19:28:45 -0000 Received: by mail-wr1-f46.google.com with SMTP id y19so560759wrd.3 for ; Wed, 28 Aug 2019 10:00:56 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=date:user-agent:in-reply-to:references:mime-version :content-transfer-encoding:subject:cc:from:message-id; bh=otYCY846xy8S217dibxFaoaJmhoPOBctLy8LKhfSGlc=; b=aRK5+QurP0DMaGNSrTmK/hBb1zmUa+xAQpds48uQ+WBSc5IbhaOZdt/SKjK+l9kcJ3 u1fYEhm4nOU06qj8h3tThUw6pUj76VOL79kyFhcSIwsAAnqSNgmOtyb7/SLepFHvJP02 suK8rTLDeXrs5+oa6ZL1wECdEN3WmT238TGRaGz2AxInvR9KuKl7mZ6imOCrx0hycQV2 p54jqL/onJn+U6tF+ofFcq+vUyX+yAEJL79u2+/BAzO6N6hHUHwNNww2kmOY3PjydEQc FcHg86UagULkcuYJgr6XePVLedoHNPu9JhIOtOUTfHQpx46/2+2+CgjAnZ2cBIgRt6FT w9Mw== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:date:user-agent:in-reply-to:references :mime-version:content-transfer-encoding:subject:cc:from:message-id; bh=otYCY846xy8S217dibxFaoaJmhoPOBctLy8LKhfSGlc=; b=O04OuyhtSkqZqSQZ+zRroxq+8ngXnCuResRG/6I0SatFdq4MhNBZWJLwriW9iKhTg1 sF2bBFda63is1+PlivJSoG7it2Q2jgj48KPDdRLp2uqOJd32NK+viBisFQl60WtbI7oi bpRAmnKHvjZu1PDaOC9QFieV1rxWk4JATAsmlMGR2C2T+nLx5VI5xQC6FLSz1+QlFAC1 Nwt8turESpr8Eo8YtWQTxEQgXc4169BQ0Q28GFpB3g2hijtoSkfi6ezdA3+3nhf3kMlS G/HQU9l1PJ0TQ0Tpe3f4lrchzVRxXhlATB3/R6AO649+MrzOGMEVsfFv5ZCXjmRHrG+3 l3ng== X-Gm-Message-State: APjAAAXoOKblq1UtVFZ/o85ZsXU7w7yvAAwsAMTGlmO9Clljvas4dKw5 epGGmqVJF9N4XCkvrn6Ep2Eywlyk X-Google-Smtp-Source: APXvYqwneNKu7C7NLJC4Kb7mHXKyiwPR7DK2Mi72aG11h78r3IGwO7zX0bsbbGxRKRr3nJGP18Jv0w== X-Received: by 2002:adf:f18c:: with SMTP id h12mr5612571wro.47.1567011655721; Wed, 28 Aug 2019 10:00:55 -0700 (PDT) Received: from [10.237.221.169] (188.29.164.15.threembb.co.uk. [188.29.164.15]) by smtp.gmail.com with ESMTPSA id a7sm947707wra.43.2019.08.28.10.00.54 for (version=TLS1_2 cipher=ECDHE-RSA-CHACHA20-POLY1305 bits=256/256); Wed, 28 Aug 2019 10:00:55 -0700 (PDT) Date: Wed, 28 Aug 2019 18:00:52 +0100 User-Agent: K-9 Mail for Android In-Reply-To: References: <203FFB9C-BB5A-43C7-B51B-036ECBC5557A@gmail.com> MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: quoted-printable CC: PHP Internals List Message-ID: Subject: Re: [PHP-DEV] [RFC] Reclassifying engine warnings From: rowan.collins@gmail.com (Rowan Collins) On 28 August 2019 17:45:50 BST, Marco Pivetta wrote: >The point is that "some organisations do X" is always used as an excuse >for >turning language design mistakes into BC boundaries=2E No=2E Things that break compatibility are compatibility breaks=2E It doesn= 't matter if they were mistakes or fashions, if code will break, it will br= eak=2E We can't change that by arguing about workflows and tools=2E Our job= is to decide if and how to make those breaks=2E So, firstly, we need to agree that their is value to this particular break= =2E I think there probably is, but people may have different opinions=2E Secondly, we need to think of a sensible way to introduce it=2E Is it resp= onsible to put a note in an upgrading page and hope everyone spots it? Is t= here a way we can flag it more loudly? What is the best time frame to roll = it out? Is there a way those who want to get it earlier can do so? Does that sound reasonable? Regards, --=20 Rowan Collins [IMSoP]