> > > - As the next LTS/2.32 is already chosen, I guess the 2.32.1 should be > out early January (or late December?) > > Late December
> > - Which means, the next baseline choice should happen around March or > April. > > It will be late February Hence, we could decide to switch to JDK8 baseline for the first weekly of > 2017? Or do you think it's a too short notice? IMHO it's too short. I'd rather make announcement and wait for another 3 months till the new LTS line. I'm still not a big fan about dropping Java 7, but . 2016-11-27 22:43 GMT+03:00 Baptiste Mathus <[email protected]>: > FWIW, after the advice of Tyler, I created a blog entry on jenkins.io > summarizing the numbers I posted previously: https://jenkins.io > /blog/2016/11/22/what-jvm-versions-are-running-jenkins-the-return/ > Seems like there's somehow an agreement, there's potentially some issues > with the maven-plugin, but even there there're apparently workarounds or > solutions. > > So, how do we move forward here? > > Here's a tentative proposal. > > Given: > > - 2.19.4 is going out on very soon supposedly > - As the next LTS/2.32 is already chosen, I guess the 2.32.1 should be > out early January (or late December?) > - Which means, the next baseline choice should happen around March or > April. > > Hence, we could decide to switch to JDK8 baseline for the first weekly of > 2017? Or do you think it's a too short notice? > > This would give us ~12 weeks to check how that works with weeklies before > the first JDK8 LTS is out. > > WDYT? > Oliver, as the LTS King, what do you think? > > Caveat/Warning: this might mean that especially for backportable bugfixes, > for 12-16 weeks, we might want to take extra care about not using JDK8 > features too much. > > BTW, how was all that handled for JDK6 => JDK7 back then? > > 2016-10-31 19:51 GMT+01:00 Jesse Glick <[email protected]>: > >> On Mon, Oct 31, 2016 at 10:22 AM, Arnaud Héritier <[email protected]> >> wrote: >> > I really dislike this feature which is trying magically >> > to do a fix. >> >> I dislike it too, it is just a last resort for people who are too lazy >> to fix their project definitions to use Animal Sniffer, toolchains, >> etc. and thus be independent of the JRE used to run Maven itself. (Or >> of course if you do not rely on other `maven-plugin` features you can >> switch to a freestyle project with a Maven build step, or even >> Pipeline with `docker.image('maven:whatever').inside {…}`). >> >> -- > You received this message because you are subscribed to a topic in the > Google Groups "Jenkins Developers" group. > To unsubscribe from this topic, visit https://groups.google.com/d/to > pic/jenkinsci-dev/fo5nKLhZK5U/unsubscribe. > To unsubscribe from this group and all its topics, send an email to > [email protected]. > To view this discussion on the web visit https://groups.google.com/d/ms > gid/jenkinsci-dev/CANWgJS6EaOKgFQNMJ553szWXT%2BYPiBj- > UD36zLEbCvT8BOGCgA%40mail.gmail.com > <https://groups.google.com/d/msgid/jenkinsci-dev/CANWgJS6EaOKgFQNMJ553szWXT%2BYPiBj-UD36zLEbCvT8BOGCgA%40mail.gmail.com?utm_medium=email&utm_source=footer> > . > > For more options, visit https://groups.google.com/d/optout. > -- 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/CAPfivLD%2BxoLd6ZytoZjOGanH_QwW8kKXsQxWzw2A58LoE26pTw%40mail.gmail.com. For more options, visit https://groups.google.com/d/optout.
