Drop 2.375.x support from plugin bom

[Mark Waite]

I've submitted a pull request to the plugin bill of materials that proposes to stop updating the 2.375.x line of the plugin BOM.

I think we should stop updating the 2.375.x BOM line because:

• Over 15% of the plugins in the bill of materials already require a core version newer than 2.375.4
  
• The last two releases of the plugin bill of materials included no plugin version changes in the bom-2.375.x set. One plugin version was pinned to 2.375.x, and multiple maven plugins were updated, but no plugin versions were updated
  
• Relatively few plugins require Jenkins 2.375.x.  Plugins that use a test jar file are commonly needing to require Jenkins 2.387.r or newer because the test jar they are consuming is coming from a plugin with that minimum Jenkins version
  

I think that is a first step.  

I think that we may also want to consider dropping support in the plugin pom for Jenkins versions older than 2.387.3.  I don't feel like I have especially strong arguments when we should reduce the range of Jenkins versions supported by new releases of the plugin pom, but would like to hear from others if they think we should continue with tooling support for Jenkins core versions older than 2.387.3.

Mark Waite

[Basil Crow]

No strong feeling one way or another from me. When we began requiring
2.361.x or newer, there was a strong technical reason; namely, it was
prohibitively difficult to support Java 11 as a first-class citizen in
the toolchain alongside Java 8. There is no similar technical
justification in this case, since the relevant changes to bring the
2.375.x BOM line up to feature parity with the 2.387.x BOM line with
regard to the plugin parent POM and test harness (i.e., the HtmlUnit
migration) could be backported if desired. So the question comes down
to whether we feel the benefit justifies the cost. If I were doing
this work myself, I would try to retain support for 2.375.x since
there is some minor inconvenience in dropping support for 2.375.x and
since I think the cost of backporting is relatively low. But since I
believe the people doing the work should make the decisions, it is not
up to me.

[Tim Jacomb]

+1 from me.

--
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-de...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-dev/CAFwNDjoCH9orjtO1NaA94gFzF5gz7AuEKa-Kn4RNP50yBqyJYw%40mail.gmail.com.

[Alexander Brandes]

+1