We were thinking of renaming jdk19 to jdk-edge and have this version following all new jdk versions almost automatically. And in the same time, modifying the buildpluging to build on this one too but without failing ... just informative (except if a specific flag is set to true, like failonedge: true for example). That way seems interesting for developers to see how there plugin behave also on the last jdk (not lts).
What do you think? On Thu, Dec 8, 2022 at 10:15 PM Basil Crow <m...@basilcrow.com> wrote: > What Tim said. I am not the biggest fan of an edge label either as > this goes against the principle of reproducible builds. The Java 19 > agent label can be deprecated in the agent documentation when Java 20 > is released (which is minimal effort on the operational side). In > general consumers of non-LTS versions of Java should realize that by > signing up to consume a non-LTS version they will need to soon move to > the next non-LTS version soon or else risk being out of luck when > upstream drops support for that non-LTS version. > > -- > 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/CAFwNDjpYJKTE%3D-zZT3uUfDV2_vsEf40AUs9TaC2JG6D%2BSd40MA%40mail.gmail.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 jenkinsci-dev+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-dev/CAO%2B-N1p9AqH8htOFCfHwaxKoWaFS475vkqNz_Dyeq7%3DF8u4G6Q%40mail.gmail.com.
