[10u-communication] jdk10u forest & process changes

[Rob McKenna]

As we move into the second update release in the JDK Updates Project
we'd like to apply some of the lessons learned over the past couple of
months.

The first, of course, was the changes to the maintainership process [1].

Also, from now on fixes pushed to the jdk-updates repo will have a fix
version in the following format: <release>u-open. I.e. 10u-open in the
case of jdk10u. Once the fix has been approved for inclusion in an update
release, a corresponding bug record with the correct update release
version will be created. (e.g. 10.0.1)

In addition to this we would like to bring the critical request process
inline with the JDK project. As such we will be adopting the convention
for RDP2 critical requests from that project [2]. I.e. instead of
10-critical-request / 10-critical-approved we'll move to
jdk10u-fix-request / jdk10u-fix-yes. [3]

So, without further ado, the JDK 10 Updates forest is now available at:

http://hg.openjdk.java.net/jdk-updates/jdk10u/

On a side note, you can find information on Oracle's plans for changes
to the security algorithms and associated policies/settings in JDK 10
updates at https://java.com/en/jre-jdk-cryptoroadmap.html, along with
instructions enabling users to proactively test/enable these changes before
they are enabled by default. Please do keep in mind that such information
is subject to change.

    -Rob

[1] http://mail.openjdk.java.net/pipermail/jdk-updates-dev/2018-February/000064.html
[2] http://openjdk.java.net/projects/jdk/10/fix-request-process
[3] http://openjdk.java.net/projects/jdk-updates/approval.html