Java Community Process (JCP) version 2.11, with a focus on streamlining the JCP program takes effect 17 December
As part of the JCP.Next effort, the fourth JSR to be released as part of the JCP program reforms, JSR 387, Streamline the JCP program, will take effect as JCP 2.11. The first in the effort was JSR 348, which increased JSR Expert Group transparency, took effect as JCP 2.8 in 2011. The second in the effort was JSR 355, EC Merge, which merged the two Executive Committees into one, took effect in 2012, and was finished being implemented in 2013. The third JSR, JSR 364, Broadening the JCP Membership took effect in 2016 and was updated in 2017.
The EC serves as the Expert Group for these efforts. EC members guide the evolution of the Java technologies by approving and voting on all technology proposals (Java Specification Requests, or JSRs). They are also responsible for defining the JCP's rules of governance and the legal agreement between members and the organization. They provide guidance to the Program Management Office (PMO) and they represent the interests of the JCP to the broader community.
As of 17 December, JCP 2.11 will be in effect.
JCP 2.11 includes the following updates:
For more information regarding the new version of the JCP Program, please refer to JSR 387. The JCP EC will continue to evolve the JCP program to meet the needs of Java developers. The EC work is public on JCP.org.