2019年02月05日:
The Maintenance Leads moved the JSR to JCP 2.11.
2018年04月09日:
Section 2.18 has been updated to include links to these Dashboards:
- JEPs: https://bugs.openjdk.java.net/secure/Dashboard.jspa?selectPageId=17668
- CSRs: https://bugs.openjdk.java.net/secure/Dashboard.jspa?selectPageId=17669
Original Java Specification Request (JSR)
Identification |
Request |
Contributions
Section 1. Identification
Submitting Member: Oracle
Name of Contact Person: Iris Clark
E-Mail Address: iris.clark
Telephone Number: +1 408 276 3909
Fax Number: -
Specification Lead Members:
Specification Leads: Iris Clark, Brian Goetz
E-Mail Addresses: iris.clark
Telephone Numbers: +1 408 276 3909
Fax Number: -
Initial Expert Group Membership:
Oracle
Azul Systems, Inc.
Red Hat
SAP SE
Supporting this JSR:
Oracle
Azul Systems, Inc.
Red Hat
SAP SE
Section 2: Request
The Java Platform, Standard Edition ("Java SE") is the core Java platform for general-purpose computing. In this release of the platform, Java SE 11 (18.9), we intend to address a number of areas based upon trends in the programming community, trends in hardware architectures, and above all our continued commitment to ensuring the broadest possible success of core Java technology for years to come.
The Java SE 11 (18.9) Platform Specification will build upon the Java Language Specification, the Java Virtual Machine Specification, and the Java SE APIs defined in Java SE 18.3. As a Platform Specification, this document will directly specify most of the features, enhancements, clarifications, and bug fixes that are part of this release. It may also specify changes to other Specifications which are revised in Maintenance Releases of existing Component JSRs.
Features for inclusion will be proposed by the Specification Leads to the Expert Group during the course of this JSR as they approach a suitable level of completeness in their design, specification, and implementation.
This JSR defines a release of the Java SE platform targeted at embedded, desktop, server, and cloud environments.
This JSR defines version 11 (18.9) of Java SE.
Continued evolution of Java SE, including evolution of the Java Virtual Machine, Java Language, and Java SE APIs, is essential to the ongoing vibrance of the Java ecosystem.
The set of VM, language, and library features that is relevant to today's developers is ever-growing.
Potential features known at the time of filing this Request are listed in section 3.1.
The Java SE platform itself does not have a single package name. All of its requirements are reflected in the packages of its constituent Java SE APIs.
No
None are known at this time.
None are known at this time.
The Java Language Specification, the Java Virtual Machine Specification, the Java Native Interface, and other elements of the Java SE Platform Specification may be revised by this JSR.
Expert Group formation: Nov 2017
Early Draft Review: Jan-Feb 2018
Public Review: Apr-May 2018
Proposed Final Draft: Jul-Aug 2018
Final Release: Sep 2018
The Expert Group will communicate primarily via e-mail, using a publicly-readable mailing list. The Expert Group may additionally hold conference calls, the minutes of which will be made public on the mailing list.
As the Specification Leads notify the Expert Group of features to be potentially included, the EG is expected to review the proposed specification for quality and implementability, and to promptly raise any concerns. We hope that additionally, the EG members will review the RI implementation, and comment on its quality and readiness.
Is the schedule for the JSR publicly available, current, and updated regularly?
We intend for this to be the case.
Can the public read and/or write to a wiki for the JSR?
We do not plan to have a wiki, but there will be a well-known public home page for the JSR, and the public can use the mailing lists to submit comments on the specification.
Is there a publicly accessible discussion board for the JSR that you read and respond to regularly?
No; discussion will take place on mailing lists (see 2.18).
Have you spoken at conferences and events about the JSR recently?
Yes.
Are you using open-source processes for the development of the RI and/or the TCK?
The source code for the RI will be developed in the JDK Project in the OpenJDK Community. Weekly early-access builds will be available for anyone to test and review.
What are the Terms of Use required to use the collaboration tools you have prepared to use with the Expert Group, so that prospective EG members can judge whether they are compatible with the JSPA?
What is the location of your publicly-accessible Issue list? In order to enable EC members to judge whether Issues have been adequately addressed, the list must make a clear distinction between Issues that are still open, Issues that have been deferred, and those that are closed, and must indicate the reason for any change of state.
What is the mechanism for the public to provide feedback on your JSR?
The public "comments" list (see 2.18)
Where is the publicly-accessible document archive for your Expert Group?
See 2.20
Does the Community tab for my JSR have links to and information about all public communication mechanisms and sites for the development of my JSR?
We intend this to be the case
Do you have a Twitter account or other social networking feed which people can follow for updates on your JSR?
Yes
Which specific areas of feedback should interested community members (such as the Adopt-a-JSR program) provide to improve the JSR (please also post this to your Community tab)?
Feedback in all areas is welcome
The RI will be the Java Development Kit (JDK), version 11 (18.9). The TCK will be the Java Compatibility Kit (JCK), version 11 (18.9).
Not applicable.
These are the licenses for the Specification and the TCK. They are similar to those for Java SE 18.3 (JSR 383: Specification, TCK).
Similar to Java SE 18.3, the RI will be made available under the GNU General Public License, version 2 for the virtual machine and the GNU General Public License, version 2, with the Classpath Exception for class libraries and portions of the virtual machine that expose public APIs.
We will implement a trio of mailing lists in an approach already used by earlier JSRs, including that for Java SE 9 (JSR 379) and Java SE 18.3 (JSR 383):
The archives of all of these lists will be publicly readable.
The public may log issues to the Issue Tracker, http://openjdk.java.net/projects/jdk/18.9/spec/issues, by sending mail to the public "comments" lists (see 2.18).
http://openjdk.java.net/projects/jdk/18.9/spec
Section 3: Contributions
This JSR builds on and may update the Java Language Specification, the Java Virtual Machine Specification, the Java SE APIs, the Java Native Interface, as well as additional specifications incorporated into the SE APIs such as the Serialization Specification, the JAR file specification, etc.
Most features incorporated in this specification will be specified directly by this JSR. Features are primarily designed and developed in the OpenJDK Community, and are described by JDK Enhancement Proposals (JEPs) or by bug reports or enhancement requests in the OpenJDK Issue Tracker.
Most features will be explored, designed, prototyped, and implemented in the OpenJDK Community before being brought to the Expert Group for inclusion in Java SE 11 (18.9).