Ancillary to this this specific issue, it is a general frustration of mine (and presumably others) for the many plugins we depend on seem to present the change information differently. Some display the information on the Jenkins Plugins Index page, some display on a child page on Jenkins Wiki https://wiki.jenkins.io/display/JENKINS/Plugins, (which I understand to be deprecated in favor of https://jenkins.io/, some display on their github CHANGELOG.md or README.md markdown pages, and some simply appear to make a release, leaving it to the user to decipher what changed.This is all very confusing.
Is there any way to encourage the community to move to a consistent model as the plugins get updated? It would seem the most elegant style is similar to kubernetes, with links to the github CHANGELOG as well as another to the README, detailing the inner workings of the plugin. That, along with a brief overview / background / purpose of the plugin, as well as the rest of the administrivia, eliminates duplication and still conveys the necessary information.
Any thoughts on a consistent documentation model and how to get to one?