On Mon, 17 Jun 2019, 09:57 Gunnar Morling, wrote:
> > I thought that the next LTS was going to be JDK 17. Did the plans change?
>
> It could be both actually.
>
> LTS is not a notion of OpenJDK itself; instead, individual build providers
> can support LTS for any release they want. The three year
> I thought that the next LTS was going to be JDK 17. Did the plans change?
No, you're probably right. It looks like my information was outdated. Sorry
for the confusion.
It wouldn't hurt to try and stay compatible, though... :)
Yoann Rodière
Hibernate NoORM Team
yo...@hibernate.org
On Mon, 17
> I thought that the next LTS was going to be JDK 17. Did the plans change?
It could be both actually.
LTS is not a notion of OpenJDK itself; instead, individual build providers
can support LTS for any release they want. The three years cadence (i.e.
11, 17 etc.) is what Oracle indicated they'd p
On Mon, 17 Jun 2019 at 08:17, Yoann Rodiere wrote:
>
> Hello team,
>
> Following the notification above, I updated CI to use the latest JDK13.
>
> I also configured JDK14 so you can use in your builds. It's named,
> unsurprisingly, "OpenJDK 14 Latest". Please set up Jenkins jobs as
> appropriate f
Hello team,
Following the notification above, I updated CI to use the latest JDK13.
I also configured JDK14 so you can use in your builds. It's named,
unsurprisingly, "OpenJDK 14 Latest". Please set up Jenkins jobs as
appropriate for your projects.
Please be aware that JDK14 will be an LTS relea
