New hotspot project repos

[Paul Hohensee]

In addition, if you want the latest jdk8 hotspot master, just get it from
jdk8/jdk8/hotspot.  It'll be pretty stable, having gone through our
rigorous test process before integration. :)  I.e., it'll be as stable as
jdk7/jdk7/hotspot used to be, which historically was pretty reliable.

Paul

On 7/20/11 6:39 PM, Erik Trimble wrote:
> On 7/20/2011 1:59 PM, Dr Andrew John Hughes wrote:
>> On 13:17 Wed 20 Jul     , 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.
>>>
>> Yeah, I noticed and was going to ask about this.   Looks like my
>> assumption about it was correct :-)
>>
>>> 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
>>>
>> Ok, so this is earlier than usual.  I only saw hs21 appear recently.
>> Should we still stick with hs21 for now, as far as a stable release 
>> goes?
>
> Yes, stick with HS21 as the latest stable one.
>
> The "new" process will be to create a hsN/hotspot repository (note, 
> that for now, it's just the Hotspot stuff, not a full forest) as soon 
> as we fork.  That is, going forward, HS22 is created now. Only the 
> Hotspot gatekeeper has push permission to it right now - it, in 
> effect, is the promotion snapshot repository.
>
> For instance, this weekend, when I'm doing the HS22 b01 snapshot, I'll 
> wrap up hsx/hotspot-main/hotspot, run it through dev testing, then 
> push into hsx/hsx22/hotspot. SQE will then use those bits to test, 
> before I push from hsx/hsx22/hotspot to jdk8/jdk8/hotspot (assuming 
> SQE give me a thumbs up).
>
> At sometime in the future, we'll be forking HS22 for final 
> stabilization into another 7Update release (likely 7u2).  When that 
> stabilization fork happens, a new HS23 repo will be created, and it 
> will now serve as the promotion candidate repository for hsx/hotspot-main
>
> HS22 will become an integration repo, where developers working on 
> stabilization directly push their work, before it goes through PIT to 
> be pushed into jdk7u/jdk7u/hotspot  (or something similar).
>
> From the "outside" perspective, this new scheme means that the latest 
> STABLE Hotspot version can always be found in the hsx/hsx(N-1) 
> repository, where N = the highest number out on hg.openjdk.java.net.