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. For more options, visit https://groups.google.com/d/optout.
