Repository? -- How many lines of development?
david.holmes at oracle.com
Mon Nov 28 21:47:59 UTC 2016
Sorry Joe this got forgotten ...
On 19/11/2016 2:33 AM, joe darcy wrote:
> On 11/18/2016 5:50 AM, Aleksey Shipilev wrote:
>> 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 ) for JDK 10? :)
>>  http://openjdk.java.net/jeps/296
> 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
> 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.
I agree with the description, but how does someone get a stable snapshot
of master at a given "level"? How will the tagging work?
I also think the name "master" (due to historical usage) suggests a
level of stability that won't actually be present. Maybe it is better to
call it "dev"?
> 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 (http://hg.openjdk.java.net/jdk9/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