Accelerating the JDK LTS release cadence

[Martijn Verburg]

Hi, Mark/Volker/All,


Microsoft believes in the end-user and operator benefits that modern Java brings. Therefore, we would also like to endorse the 2-year LTS proposal for builds of OpenJDK. Since most of the end-user ecosystem prefers to have the extra stability of an LTS, this is a great way to encourage them with their modernization efforts!


Microsoft is willing to commit to helping maintain the various LTS updates projects as they move through their natural lifecycles.


As a side note, .NET has a 2-year LTS cycle, so this makes double sense to us :-).


Cheers,
Martijn (and the MSFT Java Engineering Group)


NOTE: My working day may not be your working day! Please don’t feel obliged to read or reply to this e-mail outside of your normal working hours.

________________________________
From: discuss <discuss-retn at openjdk.java.net> on behalf of Simonis, Volker <simonisv at amazon.de>
Sent: Friday, September 17, 2021 21:07
To: mark.reinhold at oracle.com <mark.reinhold at oracle.com>; discuss at openjdk.java.net <discuss at openjdk.java.net>
Subject: [EXTERNAL] Re: Accelerating the JDK LTS release cadence

Hi Mark,

On behalf of the Amazon Corretto team I’d like to express our support
for the new JDK LTS release cadence proposal. We think this is the
right step forward to keep the OpenJDK project vibrant and relevant
with benefits for both developers and enterprises. The Corretto team
will be happy to help out and take over new responsibilities in the
OpenJDK Updates Project if endorsed by the OpenJDK community.

Thank you and best regards,
Volker & the Amazon Corretto team
________________________________________
From: discuss <discuss-retn at openjdk.java.net> on behalf of mark.reinhold at oracle.com <mark.reinhold at oracle.com>
Sent: Tuesday, September 14, 2021 16:30
To: discuss at openjdk.java.net
Subject: Accelerating the JDK LTS release cadence

Over on my blog today I’ve proposed shifting the JDK LTS release cadence
from three years to two years:

  https://nam06.safelinks.protection.outlook.com/?url=https%3A%2F%2Fmreinhold.org%2Fblog%2Fforward-even-faster&data=04%7C01%7Cmartijn.verburg%40microsoft.com%7C36002d900603493a0b6108d97a16f6c1%7C72f988bf86f141af91ab2d7cd011db47%7C1%7C0%7C637675061328608920%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C1000&sdata=a82dDbMyZoLO%2BlKmySoMZws4oabreSt2k%2BqeWmJSf3A%3D&reserved=0

The LTS release following JDK 17 would thus be JDK 21 (in 2023), rather
than JDK 23 (in 2024).

This change would, if accepted, have no effect on the main-line feature
releases developed in the JDK Project [1].  Every such release is
intended to be stable and ready for production use, whether it’s an LTS
release or not [2].

This change would, however, affect the update releases produced in the
JDK Updates Project [3].  That Project would have to take on a new LTS
release line every two years rather than three, which would be more work,
and also decide for how long to maintain each line.

This change would also affect vendors who offer paid support for LTS
releases, whether or not they participate in the JDK Updates Project.

Given the potential to accelerate the entire Java ecosystem, however,
in my view the additional work would be well justified.

Comments?  Questions?

- Mark


[1] https://nam06.safelinks.protection.outlook.com/?url=https%3A%2F%2Fopenjdk.java.net%2Fprojects%2Fjdk%2F&data=04%7C01%7Cmartijn.verburg%40microsoft.com%7C36002d900603493a0b6108d97a16f6c1%7C72f988bf86f141af91ab2d7cd011db47%7C1%7C0%7C637675061328608920%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C1000&sdata=J5x%2BleQgj9kM3NcI3wjw1TR9JMqHjTLOIEArlxufVgw%3D&reserved=0
[2] https://nam06.safelinks.protection.outlook.com/?url=https%3A%2F%2Fmail.openjdk.java.net%2Fpipermail%2Fjdk-dev%2F2021-May%2F005543.html&data=04%7C01%7Cmartijn.verburg%40microsoft.com%7C36002d900603493a0b6108d97a16f6c1%7C72f988bf86f141af91ab2d7cd011db47%7C1%7C0%7C637675061328608920%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C1000&sdata=sr2Re5Fw%2Bz8iuuHURugDlFZ%2BVB4rR2wgzT500bIh6Jk%3D&reserved=0
[3] https://nam06.safelinks.protection.outlook.com/?url=https%3A%2F%2Fopenjdk.java.net%2Fprojects%2Fjdk-updates%2F&data=04%7C01%7Cmartijn.verburg%40microsoft.com%7C36002d900603493a0b6108d97a16f6c1%7C72f988bf86f141af91ab2d7cd011db47%7C1%7C0%7C637675061328608920%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C1000&sdata=zvuSm1k1D76JViYbCzwkI3zEUnvmuAfHj4mWvclFWUw%3D&reserved=0



Amazon Development Center Germany GmbH
Krausenstr. 38
10117 Berlin
Geschaeftsfuehrung: Christian Schlaeger, Jonathan Weiss
Eingetragen am Amtsgericht Charlottenburg unter HRB 149173 B
Sitz: Berlin
Ust-ID: DE 289 237 879