-
Enhancement
-
Resolution: Fixed
-
P4
-
13
-
b20
Issue | Fix Version | Assignee | Priority | Status | Resolution | Resolved In Build |
---|---|---|---|---|---|---|
JDK-8234716 | 11.0.7-oracle | Yoshiki Sato | P4 | Resolved | Fixed | b01 |
JDK-8236589 | 11.0.7 | Erik Joelsson | P4 | Resolved | Fixed | b01 |
JDK-8303463 | 11.0.0.1 | Erik Joelsson | P4 | Resolved | Fixed | b01 |
13-internal+0-jdk13-jdk.844
With some recent improvements to our internal infrastructure and tracking system, I would like to change that to this:
13-ea+0-844
Basically, the only relevant part of the OPT string is the CI build number. Also, if this was a project sandbox, like panama or valhalla, then the PRE string would be the project name, like this:
13-panama+0-844
(Later we expect to start putting the correct promotion build numbers in there too)
This change is going into jib-profiles.js and will not affect anyone outside Oracle.
- backported by
-
JDK-8234716 Improve version string for Oracle CI builds
- Resolved
-
JDK-8236589 Improve version string for Oracle CI builds
- Resolved
-
JDK-8303463 Improve version string for Oracle CI builds
- Resolved
- relates to
-
JDK-8269415 [11u] Remove ea from DEFAULT_PROMOTED_VERSION_PRE in OpenJDK 11u
- Resolved
-
JDK-8283911 DEFAULT_PROMOTED_VERSION_PRE not reset to 'ea' for jdk-17.0.4
- Resolved
-
JDK-8223627 jdk-13+20 bundle name contains null instead of ea
- Resolved
-
JDK-8223748 JDK 13 ea b20 version string returns null as embedded
- Closed