> 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, db...@cloudbees.com a écrit : > On Thu, Dec 8, 2022 at 11:02 AM 'Stephane Merle' via Jenkins Developers < > jenkin...@googlegroups.com> 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 jenkinsci-dev+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-dev/ba7929ca-ae1e-4619-a31b-4b01be0068a3n%40googlegroups.com.
