These are the instructions for Public Review under JCP 2.11, which is somewhat different than in previous JCP versions.
In JCP 2.11, Public Review is the final review of the specification before Final Release. The Public Review is followed by the Public Review Final Approval Ballot, in which the Executive Committee votes to determine whether the JSR is approved to continue to Final Release.
Once you and your Expert Group feel that the specification is ready for Final Release, you should submit all materials as described below to the PMO (spec-submit
The PMO will host the review on jcp.org and provide the export classification for you. The materials posted for review will remain on the site as a record of the specification's development and will not be removed.
The Public Review Final Approval Ballot will start on the first Tuesday after the end of your Public Review, unless you choose to defer it so as to post an updated specification for another Public Review first. If you wish to post an update to the specification based on feedback, or just wish to work on another Public Review before going to the ballot, either inform the PMO when you submit the materials for Public Review, or notify the PMO before the close of your JSR's Public Review period: spec-submit
The following should be submitted to spec-submit
- The Spec, in pdf or zip format (be aware that Javadoc files must be zipped). The PMO will provide a standard evaluation license unless you choose to provide your own.
Please note: Any drafts posted for review must remain on the site as a record of the spec's development and will not be removed. - the desired length of the Review, anywhere from 30 - 90 days. If you do not specify a length, it will default to the normal 30 day minimum. During the review you can request to extend the length of the review by sending mail to admin
@ jcp.org at least two days before the scheduled end date. A Public Review is not to exceed 90 days. - The answer to the following questions, submitted separately for each file you want posted (.zip archives should be considered as one file for the purposes of these questions).
A. Does the specification include software codes in the following format: Binary : Yes _______ No __________ Source (compilable) : Yes _______ No __________ Javadocs : Yes _______ No __________ B. Do the codes or the spec call on, contain, use or demonstrate encryption technology? Yes _________ No ________ If yes, please describe in detail
- Either confirmation that the full license text you provided at JSR Review for the Final Release spec, RI and TCK are unchanged, or the new license texts if they have changed from what was provided previously.
- An anticipated date after the Public Review when the PMO will receive the Final Release materials (Final specification, RI, TCK, Appeals process, TCK Coverage Document, etc.).
- The version number of the specific specification document you are submitting, the anticipated release date, and the full corporate name and address of the Spec Lead Member. This will be used to produce the evaluation license for the posting. If you would like to include this in your download bundle, please send this information to admin
@jcp.org at least 2 business days before the rest of your materials. - The checklist for transparency, with specific answers for your JSR. Provide URLs if you use other sites or services.
- Confirmation that the Expert Group agrees that the specification is ready to go to Public Review.
- A determination that you either wish the Public Review Final Approval Ballot to start immediately after the Public Review, or choose to defer the Public Review Final Approval Ballot because you plan to post an additional Public Review after this one.
You may choose to have more than one Public Review, though be advised that each Public Review under JCP 2.6 through JCP 2.10 will have its own Public Draft Approval Ballot. If your JSR is operating under JCP 2.11, your Public Review will be followed by a Public Review Final Approval Ballot unless you notify the PMO that you choose to defer the ballot until after a later Public Review.
Updating the materials during the review: You may receive good comments and suggestions during the Public Review (PR) that you wish to incorporate into the Spec. You and the EG may revise the Spec. In the case of revisions that you want posted as part of the in-progress Public Review, you should send the revised draft, along with a synopsis of the changes, to the PMO (spec-submit
The PMO will notify Members of any updated drafts and change synopses received via the usual communications mechanisms, and make them available for download.
Public Review Final Approval Ballot
As soon as your Public Review ends (if you have not deferred the ballot until after another Public Review), the Executive Committee will be prompted to vote on a Public Review Final Approval Ballot, in which they vote on the merits of the Public Review materials to go to Final Release. You do not need to provide any additional materials for this ballot.
Approved ballot: If the Executive Committee votes to approve your Public Review Final Approval Ballot, you will continue on to submitting the materials for your JSR's Final Release.
Rejected ballot:
If your draft is not approved by the EC, you and the Expert Group will have 30 calendar days to revise the draft for a Public Review Final Approval Reconsideration ballot. If you plan on submitting a revised draft, please notify the PMO (pmo@jcp.org) as soon as possible after the ballot closes. If, during the Public Review Draft Approval Ballot, you have reason to believe that your draft may not be approved, you might want to start on revising the draft earlier. Working with your EG and lobbying the voting EC members reduces the risk of "no" votes. You can find information on the current voting EC Members for your draft at https://jcp.org/en/participation/committee.
The PMO welcomes suggestions and requests from the Spec Leads for improvements of this guide and the process: pmo
