Oracle is proposing a rapid release model for Java SE
The high points are highlighted below, details of the changes can
be found on Mark Reinhold’s blog  , OpenJDK discussion email list .
Under the proposed release model, after JDK 9, we will adopt a strict, time-based model with a new major release every six months, update releases every quarter, and a long-term support release every three years.The new JDK Project will run a bit differently than the past "JDK $N" Projects:
- The main development line will always be open but fixes, enhancements, and features will be merged only when they're nearly finished. The main line will be Feature Complete  at all times.
- We'll continue to use the JEP Process  for new features and other significant changes. The bar to target a JEP to a specific release will, however, be higher since the work must be Feature Complete in order to go in. Owners of large or risky features will be strongly encouraged to split such features up into smaller and safer parts, to integrate earlier in the release cycle, and to publish separate lines of early-access builds prior to integration.
The JDK Updates Project will run in much the same way as the past "JDK $N" Updates Projects, though update releases will be strictly limited to fixes of security issues, regressions, and bugs in newer features.
Related to this proposal, we intend to make a few changes in what we do:
- Starting with JDK 9 we'll ship OpenJDK builds under the GPL , to make it easier for developers to deploy Java applications to cloud environments. We'll initially publish OpenJDK builds for Linux/x64, followed later by builds for macOS/x64 and Windows/x64.
- We'll continue to ship proprietary "Oracle JDK" builds, which include "commercial features"  such as Java Flight Recorder and Mission Control , under a click-through binary-code license . Oracle will continue to offer paid support for these builds.
- After JDK 9 we'll open-source the commercial features in order to make the OpenJDK builds more attractive to developers and to reduce the differences between those builds and the Oracle JDK. This will take some time, but the ultimate goal is to make OpenJDK and Oracle JDK builds completely interchangeable.
- Finally, for the long term we'll work with other OpenJDK contributors to establish an open build-and-test infrastructure. This will make it easier to publish early-access builds for features in development, and eventually make it possible for the OpenJDK Community itself to publish authoritative builds of the JDK.
Questions , comments, feedback to OpenJDK discuss mailing list 
 https://mreinhold.org/blog/forward-faster  http://mail.openjdk.java.net/pipermail/discuss/2017-September/004281.html  http://openjdk.java.net/projects/jdk8/milestones#Feature_Complete  http://openjdk.java.net/jeps/0  http://openjdk.java.net/legal/gplv2+ce.html  http://www.oracle.com/technetwork/java/javase/terms/products/index.html  http://www.oracle.com/technetwork/java/javaseproducts/mission-control/index.html  http://www.oracle.com/technetwork/java/javase/terms/license/index.html
wildfly-dev mailing list
|Free forum by Nabble||Edit this page|