Currently the stable policy in the "What providers should do when removing ResourceLoader modules" section says:
"Developers MAY fix consumers of a module prior to deprecation, but doing so is not required as a precursor to deprecation."
The reasoning here was that developers should be paying attention to the developer console and the deprecation message appearing there should be sufficient to notify maintainers of their responsibility.
When deprecating, do we have more of a responsibility to fix things prior to the deprecation?
One downside of this, is deprecations would take longer and not work as they have traditionally. For example jquery.ui was deprecated 8+ years ago and consumers in Wikimedia production remain. Strengthening this to a SHOULD or MUST might make deprecations substantially more work and slower.
What do people think?