Return to the top of the Spec Lead Guide
Listen to the audio tutorial on the JSR Maintenance process.
Maintenance Review is for making minor changes to the Final Release specification. The Maintenance Review is an optional stage. You may choose to leave your JSR as FR or choose to present major changes to the specification as a new JSR instead.
For a Maintenance Review, you will need to submit all of the following to the PMO (spec-submit@jcp.org) via e-mail, specifying the JSR number, and "Maintenance Review" in the subject line:
- The length of the Review (30, 45, 60 or 90 calendar days).
- the full text of your Issue log (a document that lists all the suggestions you received for the spec from the public, as well as your rationale for including or excluding these suggestions from your Change Log)
- The current URL for your Change Log, or the list of proposed changes for posting on jcp.org. IMPORTANT: if supplying the list of changes for posting on jcp.org, make sure that you provide just the list of changes - the PMO posts these changes in a table labeling them as proposed, accepted, or deferred. At the close of review, the list of proposed changes will be moved automatically to the approved/deferred sections as appropriate, so including your own label of the list of changes as proposed would be confusing for the community.
- 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.
- The final Spec, in pdf or zip format (be aware that Javadoc files must be zipped). This will be used to post your Maintenance Release following the successful conclusion of your Maintenance Review, unless further changes are inserted during the review (in which case, a new final spec would have to be provided).
- The answer to the following questions for the specification document.
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
The PMO will use this information to update the Export Classification Control Number (ECCN) for you.
- The name and contact information of the Maintenance Lead.
- Where is the Reference Implementation posted for Maintenance Release?
- Where is the Technology Compatibility Kit posted for Maintenance Release?
- A description of the process by which qualified individuals and educational or not for profit organizations can access the TCK at no cost.
The PMO takes the information you provide and posts it to the web site. When it is ready, the Maintenance Review is announced to the community and the Executive Committee. After the close of review, proposed changes are automatically approved unless deferred by the Executive Committee by an Item Exception Ballot. No resubmission of the change log is necessary, unless you have new items to add to the proposed section of the change log. If there was no Item Exception Ballot, the specification, RI and TCK you provided will be posted as Maintenance Release. If there was an Item Exception Ballot which voted to defer any of the proposed changes, the PMO will contact you for the revised Maintenance Release materials or Final Reconsideration Ballot materials.
Turnaround time: When you post a Change Log for Maintenance Review, the PMO should have the web site updated with the Maintenance Review within 2 business days of receiving all of the above materials.
NOTE: these are the requirements for posting a Change Log alone. If you wish, you may also submit a draft version of the specification that illustrates the proposed changes. If you wish to do this, you will also need to submit all of the following:
- 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. Note that any license must be an evaluation-only license for Maintenance Review, since the changes you are proposing have not been approved by the Executive Committee at this stage.
- 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
The PMO will use this information to update the Export Classification Control Number (ECCN) for you.
Turnaround time: With any public posting of a spec to jcp.org, the PMO will post the spec and related materials within 10 business days of receiving all the above materials at spec-submit@jcp.org.
At the close of review you will have a list of changes that have been approved and a list of changes that have been deferred to a major revision (requires a new JSR).
Grandfathered JSRs (Specifications that have been developed outside the JCP) that are coming into the JCP enter at this stage and are assigned a 9xx number. If you are the Maintenance Lead for one of these Grandfathered JSRs you are responsible to provide the above listed materials.
Updating a JSR's Change Log during review: as the Maintenance Lead receives feedback on the proposed changes, sometimes changes to the list of proposed changes need to be made. Such updates are submitted just as the original review materials were submitted and will be posted to the Change Log up to the final week of the review, when the change log cannot be changed (as there is the potential Item Exception Ballot there). If the turnaround time to post the submission means that the update cannot be made before that deadline, Maintenance Leads have two options: extend the length of the review (from 30 to 45 days, 45 to 60, or 60 to 90) or to hold a second Maintenance Review shortly after the first completes.
Changes submitted after the completion of a Maintenance Review are always proposed changes. They must go through another Maintenance Review and be approved by the Executive Committee before they can be listed as approved.
The PMO welcomes suggestions and requests from the Spec Leads for improvements of this guide and the process: pmo@jcp.org
|
