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.
-- 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/CAFwNDjoCH9orjtO1NaA94gFzF5gz7AuEKa-Kn4RNP50yBqyJYw%40mail.gmail.com.
