Return to the top of the Spec Lead Guide
In some instances, JSRs are operating under older versions of the JCP, which may involve different sorts of stages than those laid out in the rest of the guide. You may read about those on this page.
If your JSR is operating under JCP 2.1 or earlier versions of the process, your first stage will be Community Review. Please inform the PMO (email@example.com) as soon as possible of the approximate date for the Community Review to allow preparation time.
Once the EG agrees that you are ready for Community feedback on the draft of your spec please submit it to the PMO (firstname.lastname@example.org) via e-mail with the JSR number and "Community Review" or "CR" in the subject line. When submitting the draft please provide the following:
Turnaround time: The Community Review should be posted within 2 business days of the PMO receiving all of the above materials.
- The Spec, in pdf or zip format (please note that Javadoc files must be zipped).
- The alias for comments. You need to share all comments received during the review with your EG. It is also very important that you acknowledge these comments.
- The length of the Review (30, 45, 60 or 90 calendar days). During the review until the the draft goes on the Community Review Ballot you can increase the length to the next increments. (Note that the final week of review is the draft approval ballot which may result in a slight extension of your review in order to accommodate the ballot.)
- A draft of the anticipated Business Terms. These terms are made available to the voting EC as part of the draft approval ballot. Please provide the draft of the business terms to the PMO. At the minimum this draft needs to include the licensing model and the anticipated licensing fees that you expect to apply to the Final Release versions of the RI, TCK and specification. Your Marketing Department can help you with this part of the requirements. Please look in the "Writing a JSR" section above for licensing templates. You can use one of these templates or any other licensing model provided that the compatibility requirements in the appropriate JCP document are addressed. The lastest version is JCP 2.8 found at: http://jcp.org/en/procedures/jcp2
- The answer to the following 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
At this point the PMO recommends you begin with the scheduling and planning of your RI and TCK. A stable RI and well planned TCK require careful scheduling.
Please note that you cannot enter any Review period until all of your deliverables are submitted.
During Community Review you may receive good suggestions that you wish to incorporate into the Spec. You and the EG may revise the Spec. In the case of major revisions to the draft during Community Review, you should send the revised draft, along with a synopsis of the changes, to the PMO (email@example.com) at any time up until the last 7 days of the review period. (The draft is frozen during the last 7 days of Community Review in order for the EC to complete their Draft Specification Approval Ballot). The PMO will notify Members of any updated drafts and change synopses received via the jcp-interest alias, and make them available for download.
If your draft is not approved by the EC, the EG has 30 calendar days to revise the draft for a reconsideration ballot. If you plan on submitting a revised draft, please notify the PMO (firstname.lastname@example.org) as soon as possible. If 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: http://jcp.org/en/participation/committee
The PMO welcomes suggestions and requests from the Spec Leads for improvements of this guide and the process: email@example.com