How to host HS14 stable? (Was: RFC: Change name of default HotSpot to 'default')
James.Melvin at Sun.COM
Fri Feb 20 09:42:01 PST 2009
The basic reasoning behind the HS14 fork is two-fold...
1) Lock down HS14 for extensive product-level testing and stabilization
2) Open HS15 for new work, some of which may require extended bake time
Work on the HS14 internal repository is also pushed to the OpenJDK
repository (now HS15). So, this is just a means to isolate one of many
moving parts in Java SE for productization and delivery.
Andrew John Hughes wrote:
> 2009/2/17 Volker Simonis <volker.simonis at gmail.com>:
>> As far as I understand the procedure, the HS14 has been branched at
>> some time in the past and is now "stabilized" in an Sun-internal
>> repository in order to become the next, officially released "Express"
>> VM for JDK6.
> It's quite sad that, here we are, nearly two years after OpenJDK was
> released (and more than two years for HotSpot), yet no-one thought
> that this should have been done in an open and transparent way. What
> exactly is special about this internal tree that this couldn't just
> have been done on hg.openjdk.net?
More information about the hotspot-dev