HotSpot development trees
paul.hohensee at oracle.com
Thu Oct 27 08:21:07 PDT 2011
Good summary, Dave.
The mainline hotspot development train is tagged as hs23 because back in
we changed our process so that the hotspot major version number bump happens
when we start development on a new major version rather than when we end it.
That's so we can deliver the same version into multiple under-development
JDK versions at the same time. Before August, we bumped the major version
number each time we delivered into a new JDK, which can cause a nasty
hs23 is currently being promoted into both the jdk7u train and the jdk8
on a (semi-)regular basis.
On 10/26/11 10:35 PM, David Holmes wrote:
> On 27/10/2011 8:49 AM, Dr Andrew John Hughes wrote:
>> I see three HotSpot trees have appeared at hg.openjdk.java.net since
>> I last imported one into OpenJDK6:
>> hsx/hsx21/baseline and hsx/hsx21/master
>> Which of these can be regarded as stable and can be integrated into
> I think they are all "stable" (hs23 the least) but possibly the answer
> for OpenJDK6 is "none of the above".
> hs20.X is used in our currentJDK6 update train (and hs19.X for earlier
> hs21 was jdk7
> hs22 is 7u2
> hs23 is current version for mainline and for next 7u after 7u2 (not
> sure why it's already forked off)
>> The nomenclature also appears to have changed from baseline/master
>> trees to just one called 'hotspot'. Why is this?
> The mainline tree is now hsx/hotspot-main, we then fork off hsx/hsxNN
> as needed. This started with hs22 IIRC.
More information about the hotspot-dev