As the Java Community Process evolves through different versions and revisions, changes in the terms, milestones and even the mechanics of the process itself are introduced. This page summarizes the differences between the different JCP versions over the life of the Java Community Process Program.
JCP 2.10 introduced several JCP Membership classes (Full Membership, Associate Membership, Partner Membership) and created the Employer Contribution Agreement so that individuals could participate as Full Members with IP grants from their Employers. Durations of some reviews and various associated ballots have changed.
JCP 2.9 merged the two Executive Committees (Standard/Enterprise Edition and Micro Edition) into one single Executive Committee. The merged Executive Committee votes on all JCP 2.x JSRs now, regardless of which JCP 2.x version it is.
JCP 2.8 introduced a JSR Review separate from and preceding the JSR Approval Ballot, moved the Public Draft Approval Ballot out of the Public Review period, required that the Final licenses be provided with the initial proposal, and established several transparency requirements: a public communications channel for feedback and also for the public to review Expert Group communications, a public archive of all Expert Group working documents, an Issue Tracker for logging and following open issues with the specification, and transparency into the Expert Group nomination process. All Maintenance Reviews are followed by a Maintenance Review ballot in JCP 2.8, and the standing rules for the Executive Committee were specified as part of JCP 2.8.
| 2.7 item | replaced by 2.8 |
|---|
| - | JSR Review |
| Item Exception Ballot | Maintenance Review Ballot |
| Change Log | Issue Tracker |
JCP 2.7 introduced new requirements for communicating the progress of a JSR with a transparency checklist and making the final licenses for new JSRs available from the initial proposal. It also changed the process for Final Approval Ballots, Final Releases, Maintenance Reviews, Maintenance Releases and Item Exception Ballots.
JCP 2.6 replaced the Community Review milestone with the Early Draft Review, and moved the draft approval ballot to the Public Review, rather than the first (Early Draft) review. It also made some corrections to the EC voting rules.
| 2.5 stage | replaced by 2.6 stage |
|---|
| Community Review | Early Draft Review |
| Community Draft Approval Ballot | Public Draft Approval Ballot |
JCP 2.5 introduced changes to the licensing requirements for the outputs of a JSR: the Specification, RI and TCK, and also changed how IP is handled in an Expert Group.
JCP 2.1 uses different voting rules to approve JSRs as they flow through the process. Ballots after July 10, 2001 are subject to the JCP 2.1 voting rules.
Previous ballots for JCP 2 JSRs used the JCP 2.0 rules to determine if a JSR was approved.
As the Java Community Process evolves, some of the terms used in the older versions of the process have changed.
This brief guide to the changes from JCP 1.0 is provided to ease the adjustment for anyone who had become accustomed to the terms in JCP 1.0.
To find out more about the changes from JCP 1.0 to JCP 2, please refer to the JCP 2.1 document.
| 1.0 Terminology | |
2.0 Terminology |
| Participants | --> | Members |
| Participant Review | --> | Community Review |
| Participant Draft | --> | Community Draft |
| Compatibility Test Suite (CTS) | --> | Technology Compatibility Kit (TCK) |
| Interpretation Guru (IG) | --> | Maintenance Lead (ML) |
| First Release | --> | Proposed Final Draft |
|
