upcoming merge

[Mandy Chung]

Adding one more to the complexity, the jigsaw jdk depends on a new 
hotspot entry point.  To avoid the flag day, the jigsaw hotspot change 
has to be integrated to jdk7 one build before the jigsaw jdk change to 
go in.

Mandy

Jonathan Gibbons wrote:
> Jigsaw folk,
>
> What are the expected mechanics for the upcoming merge of the Jigsaw 
> code into JDK?
>
> First, I guess, what is the expected integration area for the merge?   
> tl, I presume?
>
> Second, I presume we cannot simply push from the jigsaw forest into 
> the tl forest, because of the wild and sundry nature of the individual 
> changesets in the jigsaw forest -- jcheck will prevent that. 
> So, how is it expected that we will review and push the bits? I'm not 
> seeing much evidence of any formal or auditable review process for 
> jigsaw at this point.
>
>
> For my part, in langtools, I would prefer to stage the work into the 
> integration area via a (small) number of formally reviewed changesets. 
> Is it practical to make that happen?  Does the overall merge have to 
> happen somewhat atomically, or can we stage work into the integration 
> area (e.g. tl) providing that at each stage we pass a basic set of 
> quality tests (e.g. full build cycle, pass standard regression tests, 
> etc)
>
> -- Jon