Proposal to revise forest graph and integration practices for JDK 9

[Alan Bateman]

On 23/11/2013 16:34, Joe Darcy wrote:
> Hello,
>
> The current arrangements of sets of integration forests for a JDK 
> platform release, like JDK 8, impose high overheads on development. 
> I'm proposing we use an alternate forest arrangement for JDK 9 that 
> will dramatically reduce the propagation time of fixes across the set 
> of forests. More details below.
>
Good to see this, the lag getting fixes and changes involving hostpot + 
another repository into specific integration forests has been a bugbear 
in the system for a long time.

It would really nice to get the new structure into a diagram along with 
a summary of the testing that happens at each node or directed edge. At 
least for the short term, then does the weekend pre-integration testing 
on hotspot still happen before the changes push to dev?

I haven't see any comments yet from folks that currently push to 
jdk8/awt and jdk8/2d but one thing that is an unknown (to me at least) 
is whether there is any non-automatic testing that needs to happen 
before the changes go into master. If there is then I just wonder what 
this means for a weekly or bi-weekly integration from dev to master. 
Maybe it's no different to today, at least in the short term.

Probably a separate discussion but one thing that is not clear to many 
of us is the relationship between the hsx and jdk8 projects (some people 
have different roles in one vs. the other). Are hsx roles applicable in 
the JDK 9 project and the proposed structure? I'm just thinking of 
someone pushing to hotspot + jdk at the same time and whether they need 
to wear more than one shirt.

-Alan.