Find JSRs
Submit this Search


Ad Banner
 
 
 
 

JCP Procedures
Overview

JCP 2.9 |  JCP 2.8 |  JCP 2.7 |  JCP 2.6 |  JCP 2.5 |  JCP 2.1 |  JCP 2.0 |  JCP 1.0  
 
Once you learn the overall process of the JCP, it's easy to understand where and how you might fit in and contribute. Here are several topics to help you with the procedures.
 

JCP 2 Procedures
On June 2, 2000, JCP 2.0 replaced the previous JCP 1.0 version for new submissions. Further refinements to the voting rules resulted in JCP 2.1, introduced on July 10, 2001. A major revision of the licensing rules for the Spec, RI and TCK as well as IP policy changes and process changes was put in place by JCP 2.5, launched on October 29, 2002. The process was revised in May 2006 with the release of JCP 2.6, in May 2009 with JCP 2.7, and again in October 2011 with JCP 2.8. The current version of the process is JCP 2.9, introduced in August 2012. The program's complete rules can be found in the JCP 2: Process Document.
 

 
The Four Major Steps in the Java Community Process
Learn how a Java Specification Request (JSR) moves through its four essential steps to become a final specification and potentially become part of the Java platform, from the Initial Proposal to the Early Draft to the Public Draft and Maintenance.  

 
A specification is initiated by community members and approved for development by the Executive Committee. At times, there are new JSRs being accepted every week.
 
See the list of new JSRs recently submitted to the JCP here.
Definition of Terms for Submitting a New or Revised JSR
 
Learn the language of the JCP procedures as a first step.
 
JSR Submission Template

Members may submit a new JSR. If you are a JCP Member, use the JSR Proposal form to submit your JSR with all of the required information. If you are not a Member, read the instructions on how to become a member.

New JSRs are posted for JSR Review for 2 or 4 weeks, during which time the public can provide feedback on the proposed specification and licensing/business terms. The JSR Review period is followed by a 2-week JSR Approval Ballot, when the Executive Committee votes to approve or reject the proposal.

2. Early Draft Review (jcp.org/en/procedures/jcp2#3.2):
 
Once a JSR is approved, a group of experts is formed to develop a first draft of the specification that both the community and the Executive Committee review. Members who have signed a JSPA and wish to nominate an Expert to serve on one or more of the Expert groups can do so by submitting a nomination request.

When an Expert Group completes the first draft of their specification, they will make it available to the public for Early Draft Review. The Expert Group uses the feedback from the review to revise and refine the draft.

Current draft specifications available for Early Draft Review can be found here:

http://jcp.org/en/jsr/stage?listBy=community  

 
The JSR draft goes out for review by the public where anyone with an Internet connection can read and comment on the draft. At the end of the review, the Executive Committee decides if the draft should proceed to the next step. The Expert Group uses the public feedback to further revise the document into a Proposed Final Draft. The leader of the Expert Group then sees that the reference implementation and its associated Technology Compatibility Kit are completed before sending the specification to the Executive Committee for final approval. Once approved, the final specification, reference implementation and Technology Compatibility Kit are published.

Current Public Reviews can be found on the Public Reviews page.

Current Proposed Final Drafts can be found on the Proposed Final Drafts page.

JSRs that have posted their final materials can be found on the Final Releases page.  

 
The completed specification, reference implementation, and Technology Compatibility Kit are updated in response to ongoing requests for clarification, interpretation, enhancements, and revisions. The Executive Committee votes to approve all proposed changes to a specification to be carried out immediately or reject the changes and thus either require the Maintenance Lead to submit a revised list of changes, or defer the changes until the specification can be revised by an expert group in a new JSR. Challenges to one or more tests in a specification's Technology Compatibility Kit are ultimately decided by the Executive Committee if they cannot be otherwise resolved.
 
Current Maintenance Reviews can be found on the Maintenance Reviews page.
 
JSR Voting Results
 
JSR Voting results can be seen here.
 
JCP Background
 
Read a quick overview on how and why the JCP was begun.
 
Translations/Changes between JCP versions
 
Understand the differences between the old and new versions of the JCP process.