Pushing a little for added clarity, see inline, while totally fine with this approach.
Then we release the next C* version; for sake of illustration let's assume > a new JDK LTS 12: > > - C* 2.0 / 12 / 12 / 12 > - C* 1.0 / 11 / 11+12 / 11 > > How did jdk12 suddenly appear ? How did that happen in trunk ? While 2.0 was trunk, it must have started off as jdk11 only. During trunk dev jdk12 was worked on, and the runtime aspect of jdk12 backported to 1.0. This means that jdk12 runtime support was added to 1.0 before 2.0 was branched or released. And then, will the confidence of jdk12 in trunk be complete before its merge, and at what point can jdk11 safely be dropped ? The action of dropping jdk11 in trunk is just a one-liner in build.xml (actually code removal can happen later), but it's a commitment from us that jdk12 will be production ready. If attaining that confidence happens post-merge then there's a window where there is a chance we end up having to cut 2.0 with 11+12 ? It's a minor detail thick in the weeds, and maybe easily addressed if/when we hit it, but we should be realistic to our dev input being not always constant and reliable.
