English Original:Java Community Process Reacts to Release Cycle Announcement
InfoQ recently reported about OracleJava release model and timeline statementThe The statement is widely welcomed by the majority of Java ecosystem participants, but the Java standardization process and the role of the Java Standardization Organization (JCP) in future releases remain questionable.
In addition to the release of Java 9, Oracle has not yet clear how the new release rhythm and JCP work together. The JCP is usually running longer than the Oracle's new proposed 6-month release cycle. This raises a question, and if there is a Java specification proposal (JSR) for each feature version.
If this is the case, then Oracle needs to explain how the short version release is integrated with the JCP process. So far, very few JSR can be handled in such a short time, and no one is platform-level JSR (defined Java SE or Java EE new version).
Oracle spokesman said:
Oracle has been working with JCP to meet the fast-growing release rhythm. In the next few weeks, details of the plan may be fully supported.
Simon Ritter, a member of the JCP Executive Committee, commented:
Indeed, in the past JSR processing time than 6 months long, mainly because the platform development speed is relatively slow, so there is no need to such a fast pace of development.
In theory, although the JCP process may have some changes, but in this time to complete the Java SE JSR without any problems.
Simon Ritter also commented on Oracle's statement that it was necessary to compete faster with other programming platforms.
All along, the development of the platform is how to meet the two orthogonal user groups. Java supports many enterprises as well as some mission-critical systems; stability and compatibility are the most important factors in the deployment and maintenance of these systems.
However, now developing a new application faster and faster, developers want to use the new language and API features faster.
Oracle decided to use the 6-month release cycle and provide three years of long-term support, which seems to be the best solution for both parties.
inRecent JCP EC meetingsIn the report, Oracle plans to submit Java SE 10 JSR (now known as Java 18.3) as soon as possible, ideally released in September and freeze the release date in December. This shows that Oracle is willing to participate in the JCP process.
However, there are some known issues with the JCP process in conjunction with the SE version. In particular, there is a problem with the current process and the construction of third-party beta versions, mainly because these third parties are targeted by Java specifications that have not yet been released or are being developed.
Oracle has confirmed that these challenges will also be part of the discussion with JCP, and referred to the JCP OpenJDK Working Group andParticipants of the relevant partiesThe
The leader of the London Java Community (LJC), also a spokesperson for LJC at the JCP EC conference, Martijn Verburg, commented on this:
The JCP Executive Committee, Oracle and OpenJDK management agencies are working to streamline the standardization process to facilitate faster releases.
Eclipse Foundation Executive Director and JCP EC member Mike Milinkovich, atOne of his blog postsWrote:
Ultimately, Java will no longer use explicit and implicit usage restrictions that have plagued it since its invention. Developers can use Java on any device without any additional license or other permissions.
The Java 9 release has been delayed for more than a week, and the industry is very concerned about whether the proposed release cycle is expected to be fully implemented.