Date: Fri, 29 Mar 2024 05:20:02 +0000 (UTC) Message-ID: <1064328143.1269.1711689602652@34fc92c9345b> Subject: Exported From Confluence MIME-Version: 1.0 Content-Type: multipart/related; boundary="----=_Part_1268_524586681.1711689602651" ------=_Part_1268_524586681.1711689602651 Content-Type: text/html; charset=UTF-8 Content-Transfer-Encoding: quoted-printable Content-Location: file:///C:/exported.html
A number of fields are common between the CSR issue type and nor= mal bug/RFE issue types and between the CSR issue type and the JEP issue ty= pe. Unless otherwise noted, by default the fields in common among different= issue types are used in analogous ways in each issue type with the field.<= /p>
If a field has not been set, the field may not be displayed. To set such=
a field, when logged in hit the "Edit" button of the CSR issue.
Assignee: the engineer who is currently=
the person primarily responsible for advancing the proposal. The assignee =
may change over time as different people work on the request.
=
Labels: Free-form text
Component &=
Subcomponent: the technological area of the proposal; same classi=
fication scheme as used in the JDK project. If the proposal spans multiple =
areas, choose the area comprising the largest fraction of the proposal or b=
reak the proposal into multiple CSR issues.
Status & Re=
solution: State of the proposal in the CSR process. There are seve=
n basic states captured in the Status and resolution fields:
Compatibility-related fields:
Scope: Selection of SE, JDK, and =
Implementation. This field is shared with JEPs.
Reviewed by: The other engineers who have reviewed the =
request. At least one reviewer is required. The reviewers must include one =
or more engineers familiar with the components being modified by the reques=
t. CSR group members may serve as reviewers, but it is not mandatory to hav=
e a CSR member as a reviewer.
Interface Kind: Java=
API, System or security property, Language construct, ..., add/remove comm=
and line option, ...
Check the boxes for which kinds of interfaces are affected by this request.=
Fix Version/s: The versions the proposal is target=
ed to change. For update releases, it is accepted to use one of the "pool" =
pseudo-release values such as "8-pool" to indicate some yet-to-be-determine=
d release in the 8 update family. If known, a particular update release ver=
sion may also be given.
Attachments: Files related=
to the proposal, such as webrev.zip of specdiff representing the changes. =
Engineers are strongly encouraged to put bug numbers into into the fi=
le names that are attached. For example, for JDK-8123456 instead of attachi=
ng "webrev.zip" attach "8123456-webrev.zip". If the request is updated, lea=
ve any old attachments in place and attach updated versions (8123456-webrev=
.1.zip, etc.). The CSR members may want to compare versions of the proposal=
s and verify requested changes were made.