Repository? -- How many lines of development?

joe darcy joe.darcy at
Fri Nov 18 16:33:25 UTC 2016


On 11/18/2016 5:50 AM, Aleksey Shipilev wrote:
> Hi,
> It is very exciting to see the JDK 10 mailing list!
> When can we expect open forests (or maybe a monorepo that was discussed
> at jdk9-dev some time ago [1]) for JDK 10? :)
> Thanks,
> -Aleksey
> [1]

And thus will commence the first thread in jdk10-dev, how many lines of 
development where "line is development" means either a forest or a monorepo.

For a few reasons including not holding up the start of JDK 10 
development for further discussion about and administrative advancement 
of JEP 296 and to give more time to work on internal-only details of the 
repo consolidation (such as how the various closed repos are handled), 
the JDK 10 lines of development won't start out as monorepos. They will 
at least initially use the existing multi-repo structure as in JDK 9. 
However, we'll return to JEP 296 later in the release.

Regardless of many repos used for a line of the development, there is a 
larger question of how many lines of development to have. For JDK 10 I 
propose three lines of development:

* A master forest, serving the roles master and dev play today in 9.

With a few exceptions, in JDK 9 master was just time-delayed copy of dev 
so we can implement recording the  information about which set of 
sources correspond to a promoted build without using a whole other forest.

Rather than using a separate line of development for client-libs work as 
in 9, I think this should be done in the same line of development as all 
other libs work in 10.

* Single HotSpot forest.

Over of the course of JDK 9, the HotSpot team went from using multiple 
forests for their work to using a single one.

* Sandbox

The JDK 9 sandbox ( allows 
collaboration and publication of sources of small projects outside the 
main line of development. This ability should continue in JDK 10.




More information about the jdk10-dev mailing list