Proposed schedule change for JSR 376

[Tim Ellison]

mark.reinhold at oracle.com wrote on 01/12/2015 22:39:41:
> 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

So you would not rule out design changes after the modularity feature has 
been
implemented and integrated into the master forest?

To be clear, I'm not suggesting we delay progress on the JSR, but it would 
be good
to declare the expected timescales for completing the modularity design 
and getting
the JSR materials out for public review well before the code is feature 
complete in
Java 9 and any subsequent modifications or changes to the approach may be 
disruptive. 

Regards,
Tim