From iris.clark at oracle.com Wed Sep 3 19:06:38 2025 From: iris.clark at oracle.com (Iris Clark) Date: Wed, 3 Sep 2025 19:06:38 +0000 Subject: JSR 401 (Java SE 26): JEP Proposed to Target: 517: HTTP/3 for the HTTP Client API Message-ID: The following JEP with scope "SE" has been proposed to target JDK 26: 517: HTTP/3 for the HTTP Client API https://openjdk.org/jeps/517 Summary: Update the HTTP Client API to support the HTTP/3 protocol, so that libraries and applications can interact with HTTP/3 servers with minimal code change. The announced deadline for feedback to jdk-dev is Wed 10 Sep 20:00 UTC: https://mail.openjdk.org/pipermail/jdk-dev/2025-September/010384.html If there are no unresolved objections at that time, then the JEP will be moved to the Targeted state, indicating that the feature is expected to appear in the specified release of the JDK Project. For more information about states, see the JEP Process document: https://openjdk.org/jeps/1 A dashboard that lists JEPs with "SE" scope may be found via a link on this page: https://openjdk.org/projects/jdk/26/spec/ Thanks, Iris From iris.clark at oracle.com Wed Sep 10 01:31:19 2025 From: iris.clark at oracle.com (Iris Clark) Date: Wed, 10 Sep 2025 01:31:19 +0000 Subject: JSR 400 (Java SE 25) Final Release Message-ID: Hi. The JCP EC approved the Final Release Specification on 26 August. The Final Release version of the JSR 399 Specification, with instructions on how to find the RI and the TCK, is here: ? ?https://jcp.org/aboutJava/communityprocess/final/jsr400/index.html I've updated the primary web page for the JSR accordingly: ? ?https://openjdk.org/projects/jdk/25/spec/ Thank you for your support and participation! ?The 400 EG is now disbanded. Iris From iris.clark at oracle.com Thu Sep 11 18:33:11 2025 From: iris.clark at oracle.com (Iris Clark) Date: Thu, 11 Sep 2025 18:33:11 +0000 Subject: New candidate JEP: 524: PEM Encodings of Cryptographic Objects (Second Preview) Message-ID: The following JEP with scope "SE" has been moved to the Candidate state: 524: PEM Encodings of Cryptographic Objects (Second Preview) https://openjdk.org/jeps/524 Summary: Introduce an API for encoding objects that represent cryptographic keys, certificates, and certificate revocation lists into the widely-used Privacy-Enhanced Mail (PEM) transport format, and for decoding from that format back into objects. This is a preview API. A JEP in the Candidate state is a feature deemed worthy of consideration by the JDK Project, but with no commitment to deliver the feature in any particular release of the JDK Project. Later, the JEP may be moved to the Targeted state, which indicates that the feature is expected to appear in a specific release of the JDK Project. For more information about states, see the JEP Process document: https://openjdk.org/jeps/1 A JEP with "SE" scope that reaches the Targeted state will be listed in the Specification of the Java SE Platform JSR which corresponds to the targeted JDK Project release. A dashboard that lists JEPs with "SE" scope may be found via a link on this page: https://openjdk.org/projects/jdk/26/spec/ Thanks, Iris From iris.clark at oracle.com Tue Sep 16 19:49:44 2025 From: iris.clark at oracle.com (Iris Clark) Date: Tue, 16 Sep 2025 19:49:44 +0000 Subject: New candidate JEP: 500: Prepare to Make Final Mean Final Message-ID: The following JEP with scope "SE" has been moved to the Candidate state: 500: Prepare to Make Final Mean Final https://openjdk.org/jeps/500 Summary: Issue warnings about uses of deep reflection to mutate final fields. These warnings aim to prepare developers for a future release that ensures integrity by default by restricting final field mutation, which will make Java programs safer and potentially faster. Application developers can avoid both current warnings and future restrictions by selectively enabling the ability to mutate final fields where essential. A JEP in the Candidate state is a feature deemed worthy of consideration by the JDK Project, but with no commitment to deliver the feature in any particular release of the JDK Project. Later, the JEP may be moved to the Targeted state, which indicates that the feature is expected to appear in a specific release of the JDK Project. For more information about states, see the JEP Process document: https://openjdk.org/jeps/1 A JEP with "SE" scope that reaches the Targeted state will be listed in the Specification of the Java SE Platform JSR which corresponds to the targeted JDK Project release. A dashboard that lists JEPs with "SE" scope may be found via a link on this page: https://openjdk.org/projects/jdk/26/spec/ Thanks, Iris From iris.clark at oracle.com Mon Sep 22 16:27:10 2025 From: iris.clark at oracle.com (Iris Clark) Date: Mon, 22 Sep 2025 16:27:10 +0000 Subject: New candidate JEP: 525: Structured Concurrency (Sixth Preview) Message-ID: The following JEP with scope "SE" has been moved to the Candidate state: 525: Structured Concurrency (Sixth Preview) https://openjdk.org/jeps/525 Summary: Simplify concurrent programming by introducing an API for structured concurrency. Structured concurrency treats groups of related tasks running in different threads as single units of work, thereby streamlining error handling and cancellation, improving reliability, and enhancing observability. This is a preview API. A JEP in the Candidate state is a feature deemed worthy of consideration by the JDK Project, but with no commitment to deliver the feature in any particular release of the JDK Project. Later, the JEP may be moved to the Targeted state, which indicates that the feature is expected to appear in a specific release of the JDK Project. For more information about states, see the JEP Process document: https://openjdk.org/jeps/1 A JEP with "SE" scope that reaches the Targeted state will be listed in the Specification of the Java SE Platform JSR which corresponds to the targeted JDK Project release. A dashboard that lists JEPs with "SE" scope may be found via a link on this page: https://openjdk.org/projects/jdk/26/spec/ Thanks, Iris From iris.clark at oracle.com Mon Sep 29 20:08:51 2025 From: iris.clark at oracle.com (Iris Clark) Date: Mon, 29 Sep 2025 20:08:51 +0000 Subject: New candidate JEP: 526: Lazy Constants (Second Preview) Message-ID: The following JEP with scope "SE" has been moved to the Candidate state: 526: Lazy Constants (Second Preview) https://openjdk.org/jeps/526 Summary: Introduce an API for lazy constants, which are objects that hold immutable data. Lazy constants are treated as true constants by the JVM, enabling the same performance optimizations that are enabled by declaring a field final. Compared to final fields, however, lazy constants offer greater flexibility as to the timing of their initialization. This is a preview API. A JEP in the Candidate state is a feature deemed worthy of consideration by the JDK Project, but with no commitment to deliver the feature in any particular release of the JDK Project. Later, the JEP may be moved to the Targeted state, which indicates that the feature is expected to appear in a specific release of the JDK Project. For more information about states, see the JEP Process document: https://openjdk.org/jeps/1 A JEP with "SE" scope that reaches the Targeted state will be listed in the Specification of the Java SE Platform JSR which corresponds to the targeted JDK Project release. A dashboard that lists JEPs with "SE" scope may be found via a link on this page: https://openjdk.org/projects/jdk/26/spec/ Thanks, Iris