Hmm, maybe we're talking past one another here? I'm assuming a developer of an extension who is interested in testing a new release - if we have a version that has things deprecated vs completely removed, that allows a quick check to see if the deprecated code affects them without going back into their own code (which may have been developed partly by somebody else so just reading release notes wouldn't clue them in that there might be a problem).
Arthur
On Mon, Aug 31, 2020 at 1:23 PM Daniel Kinzler dkinzler@wikimedia.org wrote:
Am 31.08.20 um 18:52 schrieb Arthur Smith:
So the alpha release would have to be tested in a separate environment, withdevelopment
warnings enabled, and someone actually looking at the log.Typically, people
only look at logs after things break.Is that true? I thought deprecation warnings appeared directly when
viewing a
page that used the deprecated code - that was my recent experience of
this with
the WikiPage/Revision stuff that is deprecated in 1.35 - I was
experimenting
with an extension (in development mode) that hadn't fixed that issue,
and the
warnings appeared right there on every page.
Yes, in development model ($wgDeveloperWarnings = true), deprecation warnings are visible.
But very commonly, people don't actively work on this "hidden code" any more. They wrote it once, it's working, and they will not look at it again until it breaks. I'm not blaming them, that's what I do for "one off" code.
If they are actively developing features, then sure. But then they are likely to read release notes, or tests against master.
-- Daniel Kinzler Principal Software Engineer, Core Platform Wikimedia Foundation