Go to JSR:
Print Format
JCP Procedures
Overview
 
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, the current version of the process 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 is put in place by JCP 2.5, launched on October 29, 2002. The program's complete rules can be found in the JCP 2: Process Document.
 
The Four Major Steps in the Java Community Process 2.5
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 Initiation Draft to the Community Draft to the Public Draft and Maintenance.
 
1. Initiation (jcp.org/procedures/jcp2/index#1):
 
A specification is initiated by community members and approved for development by the Executive Committee. At this time, there are new JSRs being accepted every week.
 
See the list of new JSR's 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

Use the JSR Proposal form to submit your JSR with all of the required information.
2. Community Draft (jcp.org/procedures/jcp2/index#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 for Community Review. The Expert Group uses the feedback from the review to revise and refine the draft. At the end of the review, the Executive Committee decides if the draft should proceed to the next step. During this phase, the Executive Committee can preview the licensing and business terms.
 
Current draft specifications available for Community Review can be found here.
 
3. Public Draft (jcp.org/procedures/jcp2/index#3):
 
The JSR draft goes out for review by the public where anyone with an Internet connection can read and comment on the draft. The Expert Group uses the public feedback to further revise the document. 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.
 
Current Public Reviews can be found here.
 
4. Maintenance (jcp.org/procedures/jcp2/index#4):
 
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 can review all proposed changes to a specification and indicate which ones can be carried out immediately and which will require the specification to be revised by an expert group. 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 here.
 
JCP Background
 
Read a quick overview on how and why the JCP was begun.
 
Translations from JCP 1 to JCP 2
 
Understand the differences between the old and new versions of the JCP process.
 
 
Sun Microsystems
What's New
JSRs
JCP Procedures
Community Resources
Participation
Press & Success
What is the JCP