| Issue | Fix Version | Assignee | Priority | Status | Resolution | Resolved In Build |
|---|---|---|---|---|---|---|
| JDK-2177022 | 7 | Vladimir Kozlov | P3 | Closed | Fixed | b19 |
| JDK-2171987 | 6u4 | Vladimir Kozlov | P3 | Resolved | Fixed | b03 |
| JDK-2151957 | hs10 | Vladimir Kozlov | P2 | Resolved | Fixed | b16 |
HotSpot VM now has own release train: Hotspot Express.
Therefore it should have own version separated from JDK version:
<major version>.<minor version>-b<nn>
The first version will be "10.00-b15" which is currently
"1.6.0_03-ea-b02" since we forked current VM after b14.
Current VM will be "11.00-b03" which is 1.7.0-ea-b17 now
or "11.00-b04" for b18.
The <minor version> will be used for already released VM which
needs a point fix for our big customers.
Therefore it should have own version separated from JDK version:
<major version>.<minor version>-b<nn>
The first version will be "10.00-b15" which is currently
"1.6.0_03-ea-b02" since we forked current VM after b14.
Current VM will be "11.00-b03" which is 1.7.0-ea-b17 now
or "11.00-b04" for b18.
The <minor version> will be used for already released VM which
needs a point fix for our big customers.
- backported by
-
JDK-2151957 HotSpot VM should have own version separate from JDK version
-
- Resolved
-
-
-
- Resolved
-
-
-
- Closed
-
- relates to
-
JDK-6581408 Most of serviceability tools fail in 6u3b01 due to version check
-
- Resolved
-