JEPs proposed to target JDK 10 (2017/11/2)
brian.goetz at oracle.com
Tue Nov 7 16:58:25 UTC 2017
If that’s your conclusion, I think you have a serious misunderstanding of how the JEP process works. Yes ,there are a sequence of milestones, but you’ll notice none of them are “design complete”, “spec complete”, “implementation complete”, “testing complete” as a waterfall process would mandate. In fact, all of the JEP milestones are either related to inception as a project (is this something we want to consider having in the JDK), or tracking steps that all happen *after all the work is done*. For nontrivial projects, you are expected to work iteratively, progressively refining the design, interface, implementation, and test suite together, outside of the main code line, until it is ready, and then — and only then — do you start the process of proposing to target. That’s not waterfall; that’s “get it right before you think about committing any of it.”
While it would surely be possible to cheat and pretend that a project is merely N sub features each small enough to be called a bug/rfe, that would definitely be working outside the spirit of how we work. Surely that’s not what you were suggesting?
> On Nov 6, 2017, at 11:35 AM, Roman Kennke <roman at kennke.org> wrote:
> The biggest issue is that the JEP is a sort of waterfall process
More information about the jdk-dev