Plugin change logs not being updated

[John Mellor]

Is it possible to alter the commit rules to prevent plugin commits unless accompanied by a reasonable description of the change?

 

I’m seeing lots of changes lately with no idea of the nature or danger of the change, and therefore no idea of why I  need to install it or maybe hold off on a poorly tested change.  E.g this morning, the GitHub API plugin is listing an upgrade from 1.72.1 to 1.75 with absolutely no description of what is different.  Similarly, there is no description of the changes in the Translation Assistance plugin between 1.12 and the latest 1.14 release.

[Mark Waite]

I'm not sure that's blocking plugin commits without a changelog posting to the wiki page is the best way to address your concern, or maybe I'm misunderstanding your proposal.

For me, at least, a plugin release is typically composed of multiple commits.  Many of those commits are not relevant to the changelog that is posted to the wiki site.  For example, describing new tests is not useful on the changelog on the wiki page.  Another example, minor updates to dependencies are probably not worth mentioning on the changelog on the wiki page.

As an alternative, since the wiki pages can be edited by anyone with a login, when you detect a changelog is missing from a plugin that is important to you, you could review the github commits and provide a changelog entry to meet your needs and to help others who may be searching a changelog entry.

Thanks,

Mark Waite 

On Tue, Apr 26, 2016 at 7:26 AM John Mellor <John....@esentire.com> wrote:

Is it possible to alter the commit rules to prevent plugin commits unless accompanied by a reasonable description of the change?

 

I’m seeing lots of changes lately with no idea of the nature or danger of the change, and therefore no idea of why I  need to install it or maybe hold off on a poorly tested change.  E.g this morning, the GitHub API plugin is listing an upgrade from 1.72.1 to 1.75 with absolutely no description of what is different.  Similarly, there is no description of the changes in the Translation Assistance plugin between 1.12 and the latest 1.14 release.

--
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-use...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-users/9cc3b5e2313d4ba8b166a097f6fdc908%40mbx01cmb01p.esentire.local.
For more options, visit https://groups.google.com/d/optout.