Proposed schedule change for JSR 376

[Peter Kriens]

Mark,
I am not sure I understand why we need to delay the JSR 376? I think the delay is a great opportunity to deliver the JSR before, or at least aligned with the implementation so the EG can provide its input?

Kind regards,

	Peter Kriens



> On 1 dec. 2015, at 23:39, mark.reinhold at oracle.com wrote:
> 
> 2015/12/1 2:29 -0800, tim_ellison at uk.ibm.com:
>> In the original schedule, the Proposed Final Draft date for this JSR and 
>> the Feature Complete date for Java 9 is December 2015.  The new proposed 
>> schedule has the Public Review (June 2016) one month /after/ the Java 9 
>> proposed Feature Complete date (May 2016) [1].
>> 
>> If Java 9 is Feature Complete before the JSR is ready for Public Review, 
>> and well before the Proposed Final Draft, then it seems there will be 
>> little chance for the reviews to correct any significant problems in the 
>> JSR. 
> 
> "Feature Complete" does not mean "frozen", it just means "complete".
> Here's the definition [1]:
> 
>    All features have been implemented and integrated into the master
>    forest, together with unit tests.
> 
> There are typically several months between FC and the first "rampdown"
> phase.
> 
> - Mark
> 
> 
> [1] http://openjdk.java.net/projects/jdk8/milestones#Feature_Complete