How to host HS14 stable? (Was: RFC: Change name of default HotSpot to 'default')

Andrew John Hughes gnu_andrew at
Fri Feb 20 10:17:27 PST 2009

2009/2/20 James Melvin <James.Melvin at>:
> Hi Andrew,
> 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.
> - Jim
> Andrew John Hughes wrote:
>> 2009/2/17 Volker Simonis <volker.simonis at>:
>>> 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

Hi Jim,

I quite agree with the reasons for the branch, that in itself is a
very sensible approach.  My issue was with why the stable branch, when
created, was not simply done publicly.  It's not like anyone can just
commit anything they want to it anyway, and a stable HotSpot is
valuable for others outside Sun.
Andrew :-)

Free Java Software Engineer
Red Hat, Inc. (

Support Free Java!
Contribute to GNU Classpath and the OpenJDK

PGP Key: 94EFD9D8 (
Fingerprint: F8EF F1EA 401E 2E60 15FA  7927 142C 2591 94EF D9D8

More information about the distro-pkg-dev mailing list