Looking ahead: proposed Hg forest consolidation for JDK 10

Joseph D. Darcy joe.darcy at oracle.com
Thu Oct 13 00:04:00 UTC 2016


On 10/12/2016 2:17 PM, Lindenmaier, Goetz wrote:
> Hi,
> I think Andrew has a good point there.
> Cutting it into two would exactly mirror how we work
> with the licensee code, and it would help hotspot developers.
> Thanks Andrew!
> Best regards,
>    Goetz

Some general comments, there are several hundred engineers regularly 
making changes to the JDK code base. Those engineers work in a wide 
variety of different ways, in different source languages (C/C++, Java), 
with different subsets of the code (just one current repository, changes 
often crossing repositories), at different rates of pushing changes, etc.

Compared to the split repository arrangement today, the consolidated 
repository does make some kinds of operations easier or more natural and 
other operations more difficult. The trick is balancing the relative 
costs and benefits of the two categories of operations of course, which 
can be subtle [1] and one reason we are asking for feedback to get a 
better sense of the trade-offs.

Conversely, I think it is reasonable for engineers making changes to the 
JDK to be wiling to offer some flexibility in adjusting established 
worksflows optimized for the split repositories to accommodate the sort 
of infrastructure changes being proposed here for a consolidated one.



[1] "Norms: How to Measure Size," 

More information about the jdk9-dev mailing list