hsx and jdk9 (was Re: CFV: New Project: JDK 9)

John Coomes John.Coomes at oracle.com
Thu Oct 31 23:23:17 UTC 2013

Volker Simonis (volker.simonis at gmail.com) wrote:
> Hi Mark,
> ...
> And how does the creation of the JDK 9 project affect the HotSpot
> development. I recall from various discussions that you wanted to
> abandon the HotSpot Express model. So will the JDK 9 still use the
> latest and greatest HotSpot from hsx/hotspot-main or do you plan to
> have another model? ...

Hi Volker,

Note that I've changed the subject and BCC'd discuss, since I think
this is best handled on the hotspot-dev mailing list.

We (hotspot) will at some point start integrating sources from
hsx/hotspot-main into the jdk9 master repos; the process will be
similar to what we have done during jdk8 development.  In other words,
hsx/hotspot-main (and the related hsx/hotspot-{group} repos) will
remain our "ongoing-development" repos.

Note that currently the repos are targeting jdk8, so *only* jdk8 fixes
should be pushed to hsx/hotspot-main and friends.

> ...                 I you still use the one from hsx/hotspot-main,
> will the HotSpot version number be bumped to 26 once the JDK 9
> repositories have been created.

We actually want to drop the separate version number for hotspot.
There was some thought of doing that for jdk8, but it was rather late
in the release.  When the jdk9 repos open and hsx/hotspot-main
switches to jdk9 development (or soon after), we want to change the
sources so that 'java -version' simply reports the jdk version.
Here's an example of what a promoted build of the Oracle JDK might
look like:

	java version "1.8.0-ea"
	Java(TM) SE Runtime Environment (build 1.9.0-ea-b01)
	Java HotSpot(TM) Server VM (build 1.9.0-ea-b01, mixed mode)

Builds by developers would most likely not have the build number set,
so instead of a build number we would substitute something like a
mercurial hash if available, or a timestamp if not.  Here's one
possible example (note that this has not finalized by any means):

	java version "1.8.0-ea"
	Java(TM) SE Runtime Environment (build 1.9.0-ea-b01)
	Java HotSpot(TM) Server VM (build 1.9.0-ea-b01+d8eaf13402cd, mixed mode)

Which means it's based on 1.9 b01, but has additional changesets
beyond that, and the 'tip' changeset is d8eaf13402cd.


> On Wed, Oct 30, 2013 at 11:30 PM,  <mark.reinhold at oracle.com> wrote:
> > I hereby propose the creation of the JDK 9 Project, with me as the Lead
> > and the Governing Board as the sponsoring Group.
> >
> > The goal of this Project will be to produce an open-source reference
> > implementation of the Java SE 9 Platform, which will be specified in a
> > corresponding JSR, yet to be submitted, in the Java Community Process.
> >
> > The Project's repositories will initially be open for bug fixes and
> > small enhancements only.  Features for the release will be proposed
> > and tracked via the existing JEP Process [1].
> >
> > Anyone who holds the Author, Committer, or Reviewer role in the JDK 8
> > Project [2] and has contributed at least one changeset to JDK 8 will
> > be granted the same role in the JDK 9 Project.
> >
> > Votes are due by 23:59 UTC on Wednesday, 13 November [3].
> >
> > Only current OpenJDK Members [4] are eligible to vote on this motion.
> > Votes must be cast in the open on the discuss list.  Replying to this
> > message is sufficient if your mail program honors the Reply-To header.
> >
> > For Lazy Consensus voting instructions, see [5].
> >
> > - Mark
> >
> >
> > [1] http://openjdk.java.net/jeps
> > [2] http://openjdk.java.net/census#jdk8
> > [3] http://www.timeanddate.com/worldclock/fixedtime.html?msg=OpenJDK+JDK+9+CFV&iso=20131113T2359
> > [4] http://openjdk.java.net/census#members
> > [5] http://openjdk.java.net/projects/#new-project-vote

More information about the discuss mailing list