On Friday, May 10, 2024 at 12:51:46 PM UTC-6 Basil wrote:
Based on my prototyping in JENKINS-73120, there is quite a bit of work to support Jetty 12 (even just EE 8 with javax imports), blocked on the requirement of Java 17. From my perspective the sooner we require Java 17, the better. Perhaps we can require Java 17 in weeklies two weeks earlier than planned, acknowledging that this creates two fewer choices for LTS selection. Thoughts? I like the idea. It would mean that the LTS baseline selected for the last Jenkins LTS to support Java 11 would need to be two weeks earlier, but we've chosen LTS baselines that were not the most recent weekly before. 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 jenkinsci-dev+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-dev/450e7eff-2c7b-4aba-a10a-979aa7dba9a2n%40googlegroups.com.
