New hotspot project repos

[Kelly O'Hair]

On Jul 20, 2011, at 12:59 PM, Paul Hohensee wrote:

> On 7/20/11 3:39 PM, Kelly O'Hair wrote:
>> A few questions:
>> 
>> Q1: Will the old jdk7/hotspot-* forests be deleted at some point to avoid confusion?
> 
> Possibly, but that decision is above my pay grade.

If they are no longer used, and contain nothing over and above what is in the other repos,
I think you have the power to ask that they be deleted, regardless of your pay grade. ;^)

The only reason I can see for keeping them would be to preserve any possible http
links to the changesets in them, but that's a weak excuse in my book compared to the
benefit of uncluttering the main repo list page.

> 
>> Q2: I assume these hsx/hotspot-* repositories are just single hotspot repositories, not forests?
> 
> They are actually repo forests because they each include JDK8 repo forests, in the
> same way that each jdk7/hotspot* repo included a JDK7 repo forest.  That's because
> there are some jvm features that are co-developed with the JDK libraries.

Good to know. Thanks.

> 
>> Q3: I assume that jdk8/hotspot still exists and is related to hsx/hotspot-main, can you explain the
>>       process of how you will deliver changes into jdk8/hotspot?
> 
> jdk8/hotspot doesn't exist, but jdk8/jdk8/hotspot does.  The latter is the JDK8

I did mean jdk8/jdk8/hotspot.

> master version of hotspot, just as jdk7/jdk7/hotspot was the JDK7 master version
> of hotspot.  We plan to promote hotspot builds from hsx/hotspot-main through
> hsx/hsx22 to jdk8/jdk8/hotspot.  hsx/hsx22 will hold the snapshot of
> hsx/hotspot-main that we run through PIT testing.

Understood, thanks for the clarification.

> 
>> Q4: It appears that jdk8/hotspot is out of date (jdk7-b143 vintage instead of b147), will that be fixed soon?
>> 
> 
> Yes.  Erik Trimble tells me he plans to push hs22 to jdk8 at the end of this week.

Good. It has been causing some problems in other jdk8 team forests.

> 
> 
>> Q5: I assume that the same jcheck extension rules apply to these repositories:
>>        - No duplicate bugids in changesets
>>        - Same changeset comment syntax conventions
>>        - Whitespace rules on sources (no TABs allowed) etc.
> 
> Yes.  jcheck will be run on every push to any hotspot repo, just as always.

Great.

---

Thanks for the answers.

-kto

> 
> Paul
> 
>> -kto
>> 
>> On Jul 20, 2011, at 10:17 AM, Paul Hohensee wrote:
>> 
>>> Some may have noticed new Hotspot repos on hg.openjdk.java.net.  We've
>>> made the Hotspot project independent of any particular JDK project because Hotspot
>>> delivers into multiple JDKs.  These new repos replace the ones under the jdk7
>>> project for Hotspot development going forward.  They are
>>> 
>>> hsx/hotspot-main
>>> 
>>> This is the Hotspot integration repo and replaces jdk7/hotspot.
>>> 
>>> hsx/hotspot-gc
>>> hsx/hotspot-rt
>>> hsx/hotspot-comp
>>> 
>>> These are the Hotspot group repos and replace jdk7/hotspotgc, jdk7/hotspot-rt
>>> and jdk7/hotspot-comp.
>>> 
>>> We've also changed when we create repos for specific Hotspot versions.  For update
>>> releases, we used to do it just before delivery into b01 of the update.  Now, we'll
>>> do it when we bump the version number.  The version-specific repos will be used
>>> as flow-through repos during promotion into various JDK master hotspot repos,
>>> so when development on a version is done the corresponding version-specific repo
>>> will contain the definitive source for that version.  The current Hotspot version repo
>>> for hs22 was created just yesterday and is
>>> 
>>> hsx/hsx22
>>> 
>>> Paul
>>>