On Wednesday, February 23, 2022 at 3:42:50 PM UTC-7 Jesse Glick wrote: Version number to 3.x when we require Java 11 or newer? > > > Rather not, because this implies that the upgrade is incompatible for most > users and a giant change in behavior, whereas it is just a newer version of > a runtime dependency. >
Thanks for the insights. I agree. The change of major version risks that people expect dramatic changes in functionality and this is not dramatically changing functionality. Someone also shared that my examples (JGit, Jetty) were libraries that needed to communicate breaking changes in their API's through a change of major number. We're not making breaking changes in the API's as part of requiring Java 11 or newer, so it does not justify increasing the major number. I'm pulling back from the idea of making the Jenkins version that requires Java 11 be a new major version. I think we should stay with 2.x. Mark Waite -- 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 [email protected]. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-dev/24adde8c-570b-4917-a879-6fc360951400n%40googlegroups.com.
