Personally I'm not the biggest fan of edge I'd rather get a clear error that the Java version has been removed or a deprecation error in my build than the Java versions has been randomly changed to another major version.
I think that we would want a deprecation period after 20 is out (and maybe some batch automated PRs to update consumers as they should be easily searchable), then removing 19, i.e. not keeping a non LTS version forever. On Thu, 8 Dec 2022 at 19:52, '[email protected]' via Jenkins Developers <[email protected]> wrote: > +1 for the edge approach, to not create "superficial" tech debt > > On Thursday, December 8, 2022 at 8:34:12 AM UTC-8 slide wrote: > >> I think the edge idea is a good one. This reduces the churn on >> Jenkinsfile changes to support building on the latest. It would be nice if >> we, as plugin developers, could opt in to failures on the edge or not, >> meaning that a build failure on the latest jdk would not cause the build to >> fail, unless an option was set to true. >> >> On Thu, Dec 8, 2022 at 9:18 AM Damien Duportal <[email protected]> >> wrote: >> >>> > Given this is the first time (I think) that a non-LTS JDK is provided, >>> what are the plans around supporting this? >>> >>> We did not have any plan as we did not thought that much. Interesting >>> point! >>> >>> > Will it be removed once JDK 20 exists? >>> >>> I guess yes. That would break pipelines using JDK19 though. Would that >>> make sense to provide a support policy in the infra that would explain we >>> follow the JDK lifecycles? >>> >>> Also, would that make sense to, instead, provide a "jdk-edge" that would >>> be always the latest non LTS JDK instead (intermediate status: if there are >>> no version AND it's name edge, we make it explicit that it could break at >>> any time)? >>> Le jeudi 8 décembre 2022 à 17:09:34 UTC+1, [email protected] a écrit : >>> >>>> On Thu, Dec 8, 2022 at 11:02 AM 'Stephane Merle' via Jenkins Developers >>>> <[email protected]> wrote: >>>> >>>>> Hello dear developers, >>>>> >>>>> I’m happy to announce that in order to allow contributors to prepare >>>>> the future of Jenkins by working in advance with new JDK, we’ve added >>>>> JDK19 >>>>> on ci.jenkins.io. >>>>> >>>> >>>> Given this is the first time (I think) that a non-LTS JDK is provided, >>>> what are the plans around supporting this? Will it be removed once JDK 20 >>>> exists? Once JDK 21 (next LTS) exists? Will it be supported indefinitely? >>>> >>> -- >>> 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/ba7929ca-ae1e-4619-a31b-4b01be0068a3n%40googlegroups.com >>> <https://groups.google.com/d/msgid/jenkinsci-dev/ba7929ca-ae1e-4619-a31b-4b01be0068a3n%40googlegroups.com?utm_medium=email&utm_source=footer> >>> . >>> >> >> >> -- >> Website: http://earl-of-code.com >> > -- > 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/091d8d5b-8164-420c-b5fc-b6b86583bf2en%40googlegroups.com > <https://groups.google.com/d/msgid/jenkinsci-dev/091d8d5b-8164-420c-b5fc-b6b86583bf2en%40googlegroups.com?utm_medium=email&utm_source=footer> > . > -- 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/CAH-3BidX2WwL1v5GFmGLhKrmq1iMMG1%3DmT6o6LFN4TS-3mLppQ%40mail.gmail.com.
