PS JDK 11 b02 bits now available for download:
http://jdk.java.net/11/
Cheers,
-Joe
On 2/21/2018 5:47 PM, joe darcy wrote:
On 2/21/2018 12:54 PM, Martin Buchholz wrote:
On Tue, Feb 20, 2018 at 11:09 PM, Abhijit Saha <abhi.s...@oracle.com>
wrote:
It's a retroactive review request. Fix has been integrated after
reviewed
internally.
jdk11+1 (first build of jdk11) was promoted with incorrect Release
Date.
Need to be updated with correct GA date as per internal release
roadmap.
Where are my shiny jdk11+1 binaries for download ?!
It would be nice if version information was always correct, which would
mean part of the checklist of creating a release repo would be
setting the
release date of jdk/jdk/ 6 months later and marking it "ea" and updating
the version to self-identify as java N+1. jdk binaries built from
jdk/jdk
have been misidentifying themselves since the jdk 10 repo was created.
Certainly it would be preferable if the version update occurred sooner.
However, binaries build from jdk/jdk have been correctly identifying
themselves as "JDK 11" since David Holmes pushed the fix for 8173401:
"Update VERSION_FEATURE for JDK 11" on February 6, 2018.
There are about half a dozen distinct changes that need to occur for a
full conceptual version update going from JDK N to JDK (N+1). Besides
the actual version update, there are -source/-target changes to javac,
minor API changes, etc.
Some of the changes made in JDK 11 b01 were done specifically to ease
future version updates. This included hardening various tests against
version updates. Since the version updates are happening more often
now, there is more motivation to streamline the process
(https://xkcd.com/1205/).
-Joe
