JDK 11 enters Rampdown Phase One next week

[Daniel D. Daugherty]

 > Please update the fix version in JBS before pushing.

If folks do that then, the hgupdater will auto create a
JDK11 backport until the updater is switched to JDK12.
It is better to manually update the 'fix version' for
these pushes from '11' to '12'. Then we don't have to
deal with errant/premature JDK11 backports...

Dan


On 6/28/18 12:54 PM, jesper.wilhelmsson at oracle.com wrote:
> My earlier wording was a little too strict. jdk/jdk is always open and changes can be pushed even now before the tag is in there. Please note however that changes pushed to jdk/jdk now will be pushed to JDK 12. They will not go into JDK 11 unless manually backported. Please update the fix version in JBS before pushing.
>
> There will also not be any automatic testing done on these changes until after the tag has been pushed, so personally I think it would be nice not having a large number of new changes in the first JDK 12 build.
>
> Current status is that tier 1 passed with no failures. In tier 2 there is a build failure on windows-x64-slowdebug. This will need a fix.
>
> Thanks,
> /Jesper
>
>> On 28 Jun 2018, at 17:23, jesper.wilhelmsson at oracle.com wrote:
>>
>> Testing has been started.
>> The last changes that made it in before JDK 11 FC was JDK-8137164, JDK-8206004, JDK-8205956.
>>
>> No new builds will be produced from jdk/jdk until after the jdk-12+0 tag and corresponding version string changes etc has been put in place.
>>
>> Thanks,
>> /Jesper
>>
>>> On 28 Jun 2018, at 15:54, jesper.wilhelmsson at oracle.com wrote:
>>>
>>> Just a reminder that this happens in just over one hour from now.
>>>
>>> We will pick a build just after the deadline and run a series of tests on it (tiers 1-3) before adding the tag jdk12+0. Once that is done the JDK 11 stabilization repo will be created. Running the tests will take a few hours so have patience and please do not push any changes intended for JDK 12 until the tag has been pushed. I will keep you updated of our progress.
>>>
>>> Thanks,
>>> /Jesper
>>>
>>>> On 22 Jun 2018, at 18:42, mark.reinhold at oracle.com wrote:
>>>>
>>>> JDK 11 enters Rampdown Phase One next week, on Thursday, 28 June.
>>>> Changes intended for JDK 11 should be in the main-line repository
>>>> (http://hg.openjdk.java.net/jdk/jdk) or the client repository
>>>> (jdk/client), by 15:00 UTC on that day [1].
>>>>
>>>> At that time we’ll fork jdk/jdk to the JDK 11 stabilization repository,
>>>> jdk/jdk11, and promote next week’s build (jdk-11+20) and all remaining
>>>> JDK 11 builds from there.
>>>>
>>>> We'll semi-automatically merge changes pushed to jdk/jdk11 into the
>>>> main-line jdk/jdk repository, as we did for the transitions from 9
>>>> to 10 and 10 to 11.  This means that:
>>>>
>>>> - If you make a change in JDK 11 then you needn't do any extra
>>>>   work to get it into the main line, though if a merge conflict
>>>>   arises then you might be asked to help resolve it.
>>>>
>>>> - If you need to make a change in both JDK 11 and the main line
>>>>   then just push it to JDK 11, and wait for the automatic merge
>>>>   to complete.
>>>>
>>>> Changes pushed into the jdk/jdk or jdk/client repositories after 15:00
>>>> UTC next Thursday will be destined for JDK 12 unless they're back-ported.
>>>>
>>>> The jdk/submit repo will continue to be for main-line (jdk/jdk) work.
>>>> We’ll set up a jdk/submit11 repo for jdk/jdk11 work.
>>>>
>>>> The Rampdown Phase One process will be similar to that of JDK 10,
>>>> as proposed in JEP 3 [2].
>>>>
>>>> - Mark
>>>>
>>>>
>>>> [1] https://www.timeanddate.com/worldclock/fixedtime.html?msg=JDK+11+Rampdown+Phase+One&iso=20180628T15
>>>> [2] http://openjdk.java.net/jeps/3