Re: [RFC] Reclassifying engine warnings
| From: | Marco Pivetta | Date: | Wed, 28 Aug 2019 15:05:13 +0000 |
| Subject: | Re: [RFC] Reclassifying engine warnings | ||
| References: | 1 2 3 | Groups: | php.internals |
| Request: | Send a blank email to internals+get-106738@lists.php.net to get a copy of this message | ||
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/