OpenJ9 has defined a number of different labels for managing issues.
Many of the labels are of the form {category}:{subcategory}
.
The labels are defined below along with notes about their intended usage.
Describe the priority of the particular issue.
pri:high
pri:medium
pri:low
Indicate if this issue is specific for a given JDK level, such as JDK8.
jdk8
jdk9
jdk10
jdk11
jdk12
Indicate the likely component for this issue. Separating by component helps to keep the list of issues to review managable and to guide contributors for a particular area to the relevant items.
comp:vm
comp:jit
comp:test
comp:doc
comp:gc
comp:build
comp:port
comp:infra
OpenJ9 builds with several other projects: 'Eclipse OMR' & an 'OpenJDK extensions for OpenJ9' repo for each JDK level. These labels help to identify dependent changes to ensure they are merged together or in the correct order:
depends:omr
depends:openjdk(8, 9, 10, 11, 12)
depends:EclipseCQ
: Indicate a change needs a Contributor Questionnaire
Labels for issues related to OpenJDK projects and JEPs:
project:panama
project:valhalla
JEP
Labels for issues that affect performance or footprint.
perf
footprint
Label to indicate that a PR or issue requires external documentation (new feature / change in behavior / limitation).
doc:externals
Note: When you use this label, you must open an issue in the OpenJ9 documentation repo.
To indicate an issue has been raised by an end user or affects the User-experience rather than being a developer-centric issue.
userRaised
svtRaised
: Indicate an issue was raised for an Adoptium third party issue or the OpenJ9 system verification test (svt).