Incubation Feature Clarifications

[Brian Goetz]

Note that that *particular* dashboard only tracks JEPs for 10 right now 
-- but it will probably be revised soon for 11.  But, it is easy to see 
the queries behind the dashboard, and make your own.

On 2/5/2018 11:15 PM, Manoj Palat wrote:
>
> Thanks Brian, Alan for the clarifications.
> The JEP tracking query is quite useful for us - thanks!
>
> Regards,
> Manoj
>
>
> Inactive hide details for Brian Goetz ---02/05/2018 08:24:57 PM---Part 
> of the goal of the Incubating JEP is to make the incubaBrian Goetz 
> ---02/05/2018 08:24:57 PM---Part of the goal of the Incubating JEP is 
> to make the incubation-vs-permanent difference as small a
>
> From: Brian Goetz <brian.goetz at oracle.com>
> To: Manoj Palat <manoj.palat at in.ibm.com>, jdk-dev at openjdk.java.net
> Date: 02/05/2018 08:24 PM
> Subject: Re: Incubation Feature Clarifications
>
> ------------------------------------------------------------------------
>
>
>
> Part of the goal of the Incubating JEP is to make the
> incubation-vs-permanent difference as small as possible.  For almost
> anything not explicitly spelled out in the JEP, the answer is usually
> "no different than any other feature."  In that light:
>
> > Hi,
> >   I am Manoj from the Eclipse Java Development Tools (JDT) and from 
> Eclipse
> > JDT Dev, we have a couple of clarifications regarding the incubation
> > features:
> >
> >      Mandatory or Optional: We understand that when an incubation 
> feature is
> >     included in a release, it should be of production quality. 
> However, do
> >     we, as spec/compiler implementers have the freedom to omit an 
> incubation
> >     feature? In Other words, would we be termed non-compliant if we 
> do not
> >     implement a particular incubation feature?
>
> This one is spelled out in the JEP, but the answer is: no different than
> any other feature.  It's part of the spec, so its part of what the
> ecosystem should support.  (This further underscores the fact that
> incubating features are not for experimental or risky features.)
>
> >      Timeline:  How much minimum time (in weeks/months) before the 
> release
> >     can we expect a feature to be categorized as incubation? If it 
> depends
> >     on the feature, what could be a ballpark estimate?
> >
>
> No different than any other feature.  For any feature, incubating or
> not, the key milestone is Propose To Target; at this point, a JEP owner
> should consider whether including such a feature at this point in the
> cycle is the best choice.  (Incubating or not, integrating a risky
> feature near the close of the development cycle is not a good idea;
> there's another train coming soon.)
>
> JEPs that affect the platform specification are tagged as Scope: SE.
> Language features are tracked in component specification:language; VM
> features in specification:vm.  It is easy to create queries that track
> JEPs by filtering on these fields; this dashboard, used by the SE 10 EG
> (https://urldefense.proofpoint.com/v2/url?u=https-3A__bugs.openjdk.java.net_secure_Dashboard.jspa-3FselectPageId-3D17511&d=DwIDaQ&c=jf_iaSHvJObTbx-siA1ZOg&r=A51zLdywEjS50U7u2UMWvsDIrUGEJ5IDXskL5MxIEjA&m=aCW-RWU7-HcE0JNBM5QlTzx-z5oUoU_DWzw9WcCB42Y&s=3eEz0LblF0_PZQIwUtXP4B0_OdAq2DEG-c80Lp4ZNTM&e=), 
>
> is one such example -- you can customize as you like.  So it is easy to
> track the lifecycle of JEPs that will affect the language and which will
> ultimately need IDE support.
>
>
>
>