From iris.clark at oracle.com Fri Nov 1 16:37:15 2024 From: iris.clark at oracle.com (Iris Clark) Date: Fri, 1 Nov 2024 16:37:15 +0000 Subject: JSR 399 (Java SE 24): JEP Proposed to Target: 491: Synchronize Virtual Threads without Pinning Message-ID: The following JEP with scope "SE" has been proposed to target JDK 24: 491: Synchronize Virtual Threads without Pinning https://openjdk.org/jeps/491 Summary: Improve the scalability of Java code that uses synchronized methods and statements by arranging for virtual threads that block in such constructs to release their underlying platform threads for use by other virtual threads. This will eliminate nearly all cases of virtual threads being pinnedjep444-pinning to platform threads, which severely restricts the number of virtual threads available to handle an application's workload. The announced deadline for feedback to jdk-dev is Fri 8 Nov 20:00 UTC: https://mail.openjdk.org/pipermail/jdk-dev/2024-November/009600.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/24/spec/ Thanks, Iris From iris.clark at oracle.com Fri Nov 1 16:41:29 2024 From: iris.clark at oracle.com (Iris Clark) Date: Fri, 1 Nov 2024 16:41:29 +0000 Subject: JSR 399 (Java SE 24): JEP Proposed to Target: 491: Synchronize Virtual Threads without Pinning In-Reply-To: References: Message-ID: > The following JEP with scope "SE" has been proposed to target JDK 24: Sorry about this. The scope is "Implementation", not "SE" since there is no impact on SE APIs. Iris ________________________________ From: Iris Clark Sent: Friday, November 1, 2024 9:37 AM To: java-se-spec-experts at openjdk.org Cc: Iris Clark Subject: JSR 399 (Java SE 24): JEP Proposed to Target: 491: Synchronize Virtual Threads without Pinning The following JEP with scope "SE" has been proposed to target JDK 24: 491: Synchronize Virtual Threads without Pinning https://openjdk.org/jeps/491 Summary: Improve the scalability of Java code that uses synchronized methods and statements by arranging for virtual threads that block in such constructs to release their underlying platform threads for use by other virtual threads. This will eliminate nearly all cases of virtual threads being pinnedjep444-pinning to platform threads, which severely restricts the number of virtual threads available to handle an application's workload. The announced deadline for feedback to jdk-dev is Fri 8 Nov 20:00 UTC: https://mail.openjdk.org/pipermail/jdk-dev/2024-November/009600.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/24/spec/ Thanks, Iris -------------- next part -------------- An HTML attachment was scrubbed... URL: From iris.clark at oracle.com Fri Nov 1 23:16:38 2024 From: iris.clark at oracle.com (Iris Clark) Date: Fri, 1 Nov 2024 23:16:38 +0000 Subject: JSR 399 (Java SE 24): JEP Proposed to Target: 486: Permanently Disable the Security Manager Message-ID: The following JEP with scope "SE" has been proposed to target JDK 24: 486: Permanently Disable the Security Manager https://openjdk.org/jeps/486 Summary: The Security Manager has not been the primary means of securing client-side Java code for many years, it has rarely been used to secure server-side code, and it is costly to maintain. We therefore deprecated it for removal in Java 17 via JEP 411 (2021). As the next step toward removing the Security Manager, we will revise the Java Platform specification so that developers cannot enable it and other Platform classes do not refer to it. This change will have no impact on the vast majority of applications, libraries, and tools. We will remove the Security Manager API in a future release. The announced deadline for feedback to jdk-dev is Fri 8 Nov 20:00 UTC: https://mail.openjdk.org/pipermail/jdk-dev/2024-November/009601.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/24/spec/ Thanks, Iris From iris.clark at oracle.com Wed Nov 6 18:20:46 2024 From: iris.clark at oracle.com (Iris Clark) Date: Wed, 6 Nov 2024 18:20:46 +0000 Subject: JSR 399 (Java SE 24): JEP Proposed to Target: 495: Simple Source Files and Instance Main Methods (Fourth Preview) Message-ID: The following JEP with scope "SE" has been proposed to target JDK 24: 495: Simple Source Files and Instance Main Methods (Fourth Preview) https://openjdk.org/jeps/495 Summary: Evolve the Java programming language so that beginners can write their first programs without needing to understand language features designed for large programs. Far from using a separate dialect of the language, beginners can write streamlined declarations for single-class programs and then seamlessly expand their programs to use more advanced features as their skills grow. Experienced developers can likewise enjoy writing small programs succinctly, without the need for constructs intended for programming in the large. This is a preview language feature. The announced deadline for feedback to jdk-dev is Wed 13 Nov 20:00 UTC: https://mail.openjdk.org/pipermail/jdk-dev/2024-November/009617.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/24/spec/ Thanks, Iris From iris.clark at oracle.com Wed Nov 6 18:19:34 2024 From: iris.clark at oracle.com (Iris Clark) Date: Wed, 6 Nov 2024 18:19:34 +0000 Subject: JSR 399 (Java SE 24): JEP Proposed to Target: 494: Module Import Declarations (Second Preview) Message-ID: The following JEP with scope "SE" has been proposed to target JDK 24: 494: Module Import Declarations (Second Preview) https://openjdk.org/jeps/494 Summary: Enhance the Java programming language with the ability to succinctly import all of the packages exported by a module. This simplifies the reuse of modular libraries, but does not require the importing code to be in a module itself. This is a preview language feature. The announced deadline for feedback to jdk-dev is Wed 13 Nov 20:00 UTC: https://mail.openjdk.org/pipermail/jdk-dev/2024-November/009616.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/24/spec/ Thanks, Iris From iris.clark at oracle.com Thu Nov 7 00:10:25 2024 From: iris.clark at oracle.com (Iris Clark) Date: Thu, 7 Nov 2024 00:10:25 +0000 Subject: New candidate JEP: 496: Quantum-Resistant Module-Lattice-Based Key Encapsulation Mechanism Message-ID: The following JEP with scope "SE" has been moved to the Candidate state: 496: Quantum-Resistant Module-Lattice-Based Key Encapsulation Mechanism https://openjdk.org/jeps/496 Summary: Enhance the security of Java applications by providing an implementation of the quantum-resistant Module-Lattice-Based Key-Encapsulation Mechanism (ML-KEM). Key encapsulation mechanisms (KEMs) are used to secure symmetric keys over insecure communication channels using public key cryptography. ML-KEM is designed to be secure against future quantum computing attacks. It has been standardized by the United States National Institute of Standards and Technology (NIST) in FIPS 203. 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/24/spec/ Thanks, Iris From iris.clark at oracle.com Thu Nov 7 00:10:27 2024 From: iris.clark at oracle.com (Iris Clark) Date: Thu, 7 Nov 2024 00:10:27 +0000 Subject: New candidate JEP: 497: Quantum-Resistant Module-Lattice-Based Digital Signature Algorithm Message-ID: The following JEP with scope "SE" has been moved to the Candidate state: 497: Quantum-Resistant Module-Lattice-Based Digital Signature Algorithm https://openjdk.org/jeps/497 Summary: Enhance the security of Java applications by providing an implementation of the quantum-resistant Module-Lattice-Based Digital Signature Algorithm (ML-DSA). Digital signatures are used to detect unauthorized modifications to data and to authenticate the identity of signatories. ML-DSA is designed to be secure against future quantum computing attacks. It has been standardized by the United States National Institute of Standards and Technology (NIST) in FIPS 204. 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/24/spec/ Thanks, Iris From iris.clark at oracle.com Thu Nov 7 18:07:30 2024 From: iris.clark at oracle.com (Iris Clark) Date: Thu, 7 Nov 2024 18:07:30 +0000 Subject: JSR 399 (Java SE 24): JEP Proposed to Target: 492: Flexible Constructor Bodies (Third Preview) Message-ID: The following JEP with scope "SE" has been proposed to target JDK 24: 492: Flexible Constructor Bodies (Third Preview) https://openjdk.org/jeps/492 Summary: In constructors in the Java programming language, allow statements to appear before an explicit constructor invocation, i.e., super(..) or this(..). The statements cannot reference the instance under construction, but they can initialize its fields. Initializing fields before invoking another constructor makes a class more reliable when methods are overridden. This is a preview language feature. The announced deadline for feedback to jdk-dev is Thu 14 Nov 20:00 UTC: https://mail.openjdk.org/pipermail/jdk-dev/2024-November/009627.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/24/spec/ Thanks, Iris From iris.clark at oracle.com Thu Nov 7 20:15:45 2024 From: iris.clark at oracle.com (Iris Clark) Date: Thu, 7 Nov 2024 20:15:45 +0000 Subject: JSR 399 (Java SE 24): JEP Proposed to Target: Message-ID: The following JEP with scope "SE" has been proposed to target JDK 24: 483: Ahead-of-Time Class Loading & Linking https://openjdk.org/jeps/483 Summary: Improve startup time by making the classes of an application instantly available, in a loaded and linked state, when the HotSpot Java Virtual Machine starts. Achieve this by monitoring the application during one run and storing the loaded and linked forms of all classes in a cache for use in subsequent runs. Lay a foundation for future improvements to both startup and warmup time. The announced deadline for feedback to jdk-dev is Thu 14 Nov 20:00 UTC: https://mail.openjdk.org/pipermail/jdk-dev/2024-November/009628.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/24/spec/ Thanks, Iris From iris.clark at oracle.com Thu Nov 7 20:18:26 2024 From: iris.clark at oracle.com (Iris Clark) Date: Thu, 7 Nov 2024 20:18:26 +0000 Subject: JSR 399 (Java SE 24): JEP Proposed to Target: 483: Ahead-of-Time Class Loading & Linking Message-ID: // now with improved "Subject" The following JEP with scope "SE" has been proposed to target JDK 24: 483: Ahead-of-Time Class Loading & Linking https://openjdk.org/jeps/483 Summary: Improve startup time by making the classes of an application instantly available, in a loaded and linked state, when the HotSpot Java Virtual Machine starts. Achieve this by monitoring the application during one run and storing the loaded and linked forms of all classes in a cache for use in subsequent runs. Lay a foundation for future improvements to both startup and warmup time. The announced deadline for feedback to jdk-dev is Thu 14 Nov 20:00 UTC: https://mail.openjdk.org/pipermail/jdk-dev/2024-November/009628.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/24/spec/ Thanks, Iris -------------- next part -------------- An HTML attachment was scrubbed... URL: From iris.clark at oracle.com Thu Nov 7 20:22:36 2024 From: iris.clark at oracle.com (Iris Clark) Date: Thu, 7 Nov 2024 20:22:36 +0000 Subject: JSR 399 (Java SE 24): JEP Proposed to Target: 483: Ahead-of-Time Class Loading & Linking In-Reply-To: References: Message-ID: And now noticing that the Scope is "JDK" instead of "SE". I need to fix a script. Sorry, Iris ________________________________________ From:?Iris Clark Sent:?Thursday, November 7, 2024 12:18 PM To:?java-se-spec-experts at openjdk.org Cc:?Iris Clark Subject:?JSR 399 (Java SE 24): JEP Proposed to Target: 483: Ahead-of-Time Class Loading & Linking ? // now with improved "Subject" The following JEP with scope "SE" has been proposed to target JDK 24: ?483: Ahead-of-Time Class Loading & Linking ? ? ? https://openjdk.org/jeps/483 ?Summary: Improve startup time by making the classes of an application ?instantly available, in a loaded and linked state, when the ?HotSpot Java Virtual Machine starts. ?Achieve this by monitoring the ?application during one run and storing the loaded and linked forms of ?all classes in a cache for use in subsequent runs. ?Lay a foundation ?for future improvements to both startup and warmup time. The announced deadline for feedback to jdk-dev is Thu 14 Nov 20:00 UTC: ? ?https://mail.openjdk.org/pipermail/jdk-dev/2024-November/009628.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/24/spec/ Thanks, Iris From iris.clark at oracle.com Thu Nov 14 18:11:08 2024 From: iris.clark at oracle.com (Iris Clark) Date: Thu, 14 Nov 2024 18:11:08 +0000 Subject: JEP proposed to target JDK 24: 496: Quantum-Resistant Module-Lattice-Based Key Encapsulation Mechanism Message-ID: The following JEP with scope "SE" has been proposed to target JDK 24: 496: Quantum-Resistant Module-Lattice-Based Key Encapsulation Mechanism https://openjdk.org/jeps/496 Summary: Enhance the security of Java applications by providing an implementation of the quantum-resistant Module-Lattice-Based Key-Encapsulation Mechanism (ML-KEM). Key encapsulation mechanisms (KEMs) are used to secure symmetric keys over insecure communication channels using public key cryptography. ML-KEM is designed to be secure against future quantum computing attacks. It has been standardized by the United States National Institute of Standards and Technology (NIST) in FIPS 203. The announced deadline for feedback to jdk-dev is Thu 21 Nov 20:00 UTC: https://mail.openjdk.org/pipermail/jdk-dev/2024-November/009642.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/24/spec/ Thanks, Iris From iris.clark at oracle.com Thu Nov 14 18:11:13 2024 From: iris.clark at oracle.com (Iris Clark) Date: Thu, 14 Nov 2024 18:11:13 +0000 Subject: JEP proposed to target JDK 24: 497: Quantum-Resistant Module-Lattice-Based Digital Signature Algorithm Message-ID: The following JEP with scope "SE" has been proposed to target JDK 24: 497: Quantum-Resistant Module-Lattice-Based Digital Signature Algorithm https://openjdk.org/jeps/497 Summary: Enhance the security of Java applications by providing an implementation of the quantum-resistant Module-Lattice-Based Digital Signature Algorithm (ML-DSA). Digital signatures are used to detect unauthorized modifications to data and to authenticate the identity of signatories. ML-DSA is designed to be secure against future quantum computing attacks. It has been standardized by the United States National Institute of Standards and Technology (NIST) in FIPS 204. The announced deadline for feedback to jdk-dev is Thu 21 Nov 20:00 UTC: https://mail.openjdk.org/pipermail/jdk-dev/2024-November/009643.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/24/spec/ Thanks, Iris From iris.clark at oracle.com Thu Nov 14 18:17:40 2024 From: iris.clark at oracle.com (Iris Clark) Date: Thu, 14 Nov 2024 18:17:40 +0000 Subject: New candidate JEP: 499: Structured Concurrency (Fourth Preview) Message-ID: The following JEP with scope "SE" has been moved to the Candidate state: 499: Structured Concurrency (Fourth Preview) https://openjdk.org/jeps/499 Summary: Simplify concurrent programming by introducing an API for structured concurrency. Structured concurrency treats groups of related tasks running in different threads as a single unit of work, thereby streamlining error handling and cancellation, improving reliability, and enhancing observability. This is a preview API. 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/24/spec/ Thanks, Iris From iris.clark at oracle.com Tue Nov 19 16:55:12 2024 From: iris.clark at oracle.com (Iris Clark) Date: Tue, 19 Nov 2024 16:55:12 +0000 Subject: JSR 399 (Java SE 24): JEP Proposed to Target: 499: Structured Concurrency (Fourth Preview) Message-ID: The following JEP with scope "SE" has been proposed to target JDK 24: ?499: Structured Concurrency (Fourth Preview) ? ? ? https://openjdk.org/jeps/499 ?Summary: Simplify concurrent programming by introducing an API for ?structured concurrency. ?Structured concurrency treats groups of ?related tasks running in different threads as a single unit of work, ?thereby streamlining error handling and cancellation, improving ?reliability, and enhancing observability. ?This is a preview API. The announced deadline for feedback to jdk-dev is Tue 26 Nov 20:00 UTC: https://mail.openjdk.org/pipermail/jdk-dev/2024-November/009659.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/24/spec/ Thanks, Iris