What kinds of changes need a JEP?

Erik Helin erik.helin at oracle.com
Mon Nov 6 12:11:24 UTC 2017

On 11/06/2017 10:14 AM, mark.reinhold at oracle.com wrote:
>                                    * * *
> Here's a proposed new list of criteria that incorporates these changes.
> A JEP should be drafted for a body of work when at least one of the
> following is true:
>    - It makes a significant or risky change to the JDK,
>    - It has a broader impact on developers and users than can reasonably
>      be communicated in an ordinary enhancement or CSR issue, or
>    - It is in high demand by developers or users.
> Comments?

For me, as primarily a HotSpot developer, this would be fantastic. There 
are a lot of work that takes longer than two weeks in HotSpot but 
doesn't really "fit" the JEP process today. This is particularly true 
for performance enhancements and internal refactorings (as you already 
have noticed).

So two thumbs up from me, great update to the process!


> - Mark
> [1] http://openjdk.java.net/jeps/1#Overview

More information about the jdk-dev mailing list