Proposed schedule for JDK 18.3

[Seán Coffey]

> Given the shorter stabilization period there likely won't be time for
> every bug fix to percolate from the main line into the release repo, so
> I expect that some (most?) fixes will go directly into the release repo.
> We'll try to automate merges of such fixes back into the main line, as
> we did for JDK 9.

I'm not sure if this is the best model to adopt. The JDK 8 Updates 
Project has been
using a critical-request model for some time now. It works well. Before 
accepting a
patch into an upcoming production release (stabilization forest), we 
know that the
patch has been soaked in the mainline where EA binaries are available 
and where
more test infrastructure/cycles might also be available.

Pulling a patch from the mainline also reduces concerns about avoiding a 
possible
regression in a future release if a patch gets accidentally dropped or 
doesn't get ported
in time for the next JDK release (which would be less than 6 months away)

Given the regular 6 monthly release cycle, I'm hoping the bar will be 
real high for
acceptance of such patches into a release post ramp-down.

Regards,
Sean.


On 13/10/2017 01:43, mark.reinhold at oracle.com wrote:
> 2017/10/12 0:59:18 -0700, volker.simonis at gmail.com:
>> On Wed, Oct 11, 2017 at 10:17 AM, mark.reinhold at oracle.com wrote:
>>> ...
>>>
>>> There's no "Feature Complete" milestone since, in the six-month model,
>>> every feature must be complete before it's integrated.  The main
>>> development line is, in effect, always feature complete.  The set of
>>> features in the release contains all, and only, those features that
>>> are integrated ahead of Rampdown Phase One.
>> does this mean that the jdk-18.3 repository will be created (i.e.
>> forked) just before "Rampdown Phase One" is entered?
> Yes.
>
>> What will be the working model after the fork of jdk-18.3? Will bug
>> fixes for 18.3 have to go to jdk-dev first and then backported to
>> jdk-18.3 or can they be pushed right into jdk-18.3? In the latter
>> case, will there be an automatic integration process of fixes from
>> jdk-18.3 into jdk-dev?
> Given the shorter stabilization period there likely won't be time for
> every bug fix to percolate from the main line into the release repo, so
> I expect that some (most?) fixes will go directly into the release repo.
> We'll try to automate merges of such fixes back into the main line, as
> we did for JDK 9.
>
> - Mark