Newsgroups: php.internals
Path: news.php.net
Xref: news.php.net php.internals:106738
MIME-Version: 1.0
References: <CAF+90c9Kc6m_bv=aJxbD3-RmnNXXLqv6mPjHp7U7qxX_ck27qw@mail.gmail.com>
 <CAKuGYLQC2z+GmOgbqxFWbAGS6B2z=mXTp72c6Be53ju4D6pNRw@mail.gmail.com> <B6913F25-2859-4BA5-906F-8F6B245BA8E8@gmail.com>
In-Reply-To: <B6913F25-2859-4BA5-906F-8F6B245BA8E8@gmail.com>
Date: Wed, 28 Aug 2019 17:05:13 +0200
Message-ID: <CADyq6s+Q_-E6GchkmPdV0Ps=AVifGsAjy70bNW1-715qcgA-Gw@mail.gmail.com>
To: Rowan Collins <rowan.collins@gmail.com>
Cc: PHP Internals List <internals@lists.php.net>
Content-Type: multipart/alternative; boundary="000000000000f9fd9305912eb7c6"
Subject: Re: [PHP-DEV] [RFC] Reclassifying engine warnings
From: ocramius@gmail.com (Marco Pivetta)

--000000000000f9fd9305912eb7c6
Content-Type: text/plain; charset="UTF-8"

On Wed, Aug 28, 2019 at 4:56 PM Rowan Collins <rowan.collins@gmail.com>
wrote:

> On 28 August 2019 15:22:22 BST, Matthew Brown <matthewmatthew@gmail.com>
> wrote:
> >Looking at our notice logs, I estimate (fairly roughly) that it would
> >require about a week's worth of my time to fix these issues
>
> I honestly thought you were posting that as an argument against. A week of
> resource (plus the accompanying QA impact etc) is a significant investment
> for many organisations. That's why it has the potential to delay adoption
> of a new version, and why a long lead-in via deprecation or opt-in is
> necessary.
>

A week for 700KLOC is *impressively low*.
Many organisations spend more time on *deciding* whether to upgrade a patch
version of a dependency, and the tooling that vimeo has provided to detect
these issues is technically impressive, and very much usable by other orgs
too.

Marco Pivetta

http://twitter.com/Ocramius

http://ocramius.github.com/

--000000000000f9fd9305912eb7c6--