This "fix" is causing a long list of current plugins to not load. Please revert this "fix" until plugin maintainers are able to keep up with this so called improvement. #nothappyjan
Whatever you're experiencing is unrelated to this documentation fix. Notably this change only replaces one "this will be broken" warning with a more correct one. If you relied on the previous behavior, that was a pretty terrible idea anyway (an unfortunate side effect of how our update site infra works that we will need to tackle some time, but not really a priority: we expect users to either update frequently or run LTS releases, in which case the situation referred to in the warning isn't even a problem).
My crystal ball says you're upset about
JENKINS-21486, which has been released half a year ago in Jenkins 2.16. It's extremely unlikely that this will be reverted (only improved), as it trades impossible to investigate errors at random times during runtime for clearly logged errors on startup. It's also (mostly) unrelated to anything maintainers could be doing, but rather is about invalid configurations, having plugins disabled that are dependencies of other plugins, or in incompatible versions, etc.
Please file a new issue, describing in detail what you're doing, what versions of Jenkins you're running now and before, what plugins are installed in what versions, what happens, and why it's a problem. Reopening unrelated (or even related issues) saying "this is terrible" doesn't help.