I don't think that failure to write a changelog entry should be enough to deny publishing an update to a plugin. Denying publishing of a plugin for lack of a changelog entry seems very "heavy" to me.
It won't prevent publishing plugins when the changelog entry says "no visible changes" or says "something that no one understands". It requires that the changelog is written before the plugin is released, when I've found it reasonable to write the changelog immediately after releasing the plugin. Maybe we could have some form of "ratings system" for plugins like we have for Jenkins as a whole (at https://jenkins.io/changelog/) and that would then allow you to "downvote" any plugin that released without a changelog that met your requirements. I suspect user expectations of changelog entries vary depending on how they are using Jenkins, how often they update, which plugins they use, and how they use Jenkins. Mark Waite On Mon, Jun 5, 2017 at 7:29 AM John Mellor <john.mel...@esentire.com> wrote: > This morning I am looking at 2 more plugins that have somehow been > published without a changelog entry. Aside from this being very > unprofessional, we do not install plugin updates without changelog entries > that describe what the change is. These are almost as bad as the stupid > no-user-visible-changes changelog entries that the core engine slips in > once in a while. We have been burned by these poorly thought-through > updates several times in the past. > > > > Is it possible add a rule to just deny a plugin publishing an update that > does not have a usable changelog update? > > > > -- > You received this message because you are subscribed to the Google Groups > "Jenkins Users" group. > To unsubscribe from this group and stop receiving emails from it, send an > email to jenkinsci-users+unsubscr...@googlegroups.com. > To view this discussion on the web visit > https://groups.google.com/d/msgid/jenkinsci-users/5dfcaad218b8442bb4a13194e2fb3e05%40mbx02cmb01p.esentire.local > <https://groups.google.com/d/msgid/jenkinsci-users/5dfcaad218b8442bb4a13194e2fb3e05%40mbx02cmb01p.esentire.local?utm_medium=email&utm_source=footer> > . > For more options, visit https://groups.google.com/d/optout. > -- You received this message because you are subscribed to the Google Groups "Jenkins Users" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-users+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-users/CAO49JtEuRLGDWE9HYEE5mcgwGAZfvBpP2CcbO_FM9pufwdcsVQ%40mail.gmail.com. For more options, visit https://groups.google.com/d/optout.
