The JVM Advent Calendar: JCP.NEXT, Streamlining the JCP Program

DZone 's Guide to

The JVM Advent Calendar: JCP.NEXT, Streamlining the JCP Program

This holiday season, we look at changes being made to the stages of the JSR lifecycle.

· Java Zone ·
Free Resource

JCP Executive Committee

Java Community Process (JCP) version 2.11, with a focus on streamlining the JCP program takes effect December 14th.

This blog post is on the latest JCP.Next effort to streamline the JCP program JSR lifecycle in response to feedback from the Java development community and the faster release cadence introduced in 2017.

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 December 14th, JCP 2.11 will be in effect. I serve as the Director and Chairperson of the JCP program and Specification Lead for JSR 387, Streamlining the JCP Program.  We are excited to introduce the latest version of the JCP program to the community. In 2017, the EC started working group meetings around how to streamline and evolve the JCP program to meet the needs of the changes in the Java development ecosystem. We decided to initiate JSR 387 to streamline the JSR lifecycle process to bring it in line with the way Java technology is developed today. I think the community will be excited about the changes introduced for their continued participation and feedback in the JCP program.

JCP 2.11 includes the following updates:

  • Modification and addition of language around code first, collaborative RI development.
  • Changes to the stages of a JSR lifecycle as a result of a more open and collaborative development process (see section 3.3, 3.4, 3.5 of the Process document), and to be in keeping with a more agile and continuous delivery software development model.
  • The ability to allow automated renewals for multiple versions of JSRs, especially for the Java Standard Edition (Java SE) Platform JSRs, which continue to be developed under the JCP program and OpenJDK.
  • Modifications to Renewal Ballots and Dormant JSRs.
  • Changes to the Maintenance process, including the addition of an errata release.
  • Changes to the JCP Executive Committee (see section 3.7 of the Process document) and EC Standing Rules regarding EC Member participation.

We will have our last public EC Meeting of 2018 on December 11th. It will be recorded for those who cannot participate live – anyone is welcome to attend to learn more about the latest version of the JCP or ask questions of the JCP EC.

Tuesday, December 11, 20189:00 am Pacific Standard Time (GMT-08:00)

WebEx Link

Meeting number: 740 136 406
Meeting password: 123456
Join by phone: 
Primary Dial-in Number: 1-866 682 4770 (US) 
Alternate Dial-in Number: 1-408 774 4073 (US)
Global numbers
Conference Code: 138 683 3 
Password: 123456

For more information regarding the new version of the JCP Program, please refer to JSR 387 . The JCE EC will continue to evolve the JCP program to meet the needs of Java developers. The EC work is public on JCP.org.

java, jcp, jcp program, jcp.next, jvm, jvm advent calendar

Published at DZone with permission of Heather Vancura . See the original article here.

Opinions expressed by DZone contributors are their own.

{{ parent.title || parent.header.title}}

{{ parent.tldr }}

{{ parent.urlSource.name }}