> On 10.04.2017, at 00:01, Oleg Nenashev <o.v.nenas...@gmail.com> wrote: > > I think that the minimal requirement from the community side is to have the > Security fixes applicable on the last Jenkins LTS with security fixes in the > core.
Strictly speaking, this is up to maintainers, but I would be surprised if anyone decided on a Jenkins dependency more recent than current LTS for security fixes. > So de-listing of plugins for older releases IMHO does not worth efforts, > especially since there is an administrative warning for unsafe core/plugins. > The instance admins will be warned. Only since 2.40 and 2.32.2, so in my example in the original email, there's plenty of instances without a warning, that still would get the plugin. -- You received this message because you are subscribed to the Google Groups "Jenkins Developers" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-dev+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-dev/30E4F7B3-A328-41BF-A638-520036503D69%40beckweb.net. For more options, visit https://groups.google.com/d/optout.
