What kinds of changes need a JEP? (original) (raw)

mark.reinhold at oracle.com mark.reinhold at oracle.com
Mon Nov 13 18🔞09 UTC 2017

2017/11/8 17:58:57 -0800, david.holmes at oracle.com:

On 9/11/2017 4:58 AM, Volker Simonis wrote:

...

This would make it clear that a JEP is a more heavy-weight project than a simple enhancement and that we expect a fully working and tested implementation before we consider to integrate it into the "always feature complete" main line. It would also keep people from "cheating" by implementing parts of a JEP incrementally in the main line. It is perfectly reasonable for JEP work to identify cleanups and refactorings that aid the JEP work, but which can be putback to the mainline as a standalone change. Without such enabling changes we would greatly increase the difficulty of integrating the JEP work when it is ready. I don't consider this "cheating".

Agreed. If a preparatory change for a JEP can be justified on its own, without a separate JEP, then you can merge it before that JEP is targeted.

More information about the jdk-dev mailing list