Right, jdk9/hs is closed as we are ramping down and the number of Hotspot changes in JDK 9 is fairly small at this point.
jdk10/jdk10 (a.k.a. 10/10) is the main JDK 10 forest. jdk10/hs (10/hs) is a child of 10/10. 10/hs is where JDK 10 Hotspot changes should be pushed. These changes will go through an extra layer of testing before being integrated to 10/10.
Currently changes are frequently pulled from 10/10 to 10/hs to keep 10/hs in sync, but so far we have not started to push changes from 10/hs to 10/10. Pushing 10/hs to 10/10 would complicate the forward ports currently being done on a weekly basis from JDK 9 so we are holding off with hs integrations until the frequency of changes in JDK 9 goes down.
> On 15 May 2017, at 16:49, Andrew Haley <[hidden email]> wrote:
> Looks like nothing is going into jdk9 / hs / hotspot. Everything now goes into
> jdk9 / dev / hotspot. I guess this is normal during rampdown?
> But with JDK 10, jdk10 / hs / hotspot is live, and so is jdk10 / jdk10 / hotspot.
> How does this work? Is there a two-way merge going on?