Hi Thomas,
The updates to the release note look fine.
Usually they are brief, containing just enough information to quickly
recognize the function and feature that has changed.
The complete information can be found in the original Jira issue.
Sorry about the lack of an external release note guide, one is needed.
Release notes use Markdown making them a bit more readable.
Looking at release notes from any prior release [1] will give you a good
idea
as to the typical scope and wording.
Closing the release note as "Delivered" marks it ready for an
editorial pass made before the release notes are published
with the GA release.
Thanks, Roger
[1]
https://www.oracle.com/technetwork/java/javase/11-relnote-issues-5012449.html
On 11/30/2018 01:23 AM, Thomas Stüfe wrote:
Hi all,
I updated the Release note, please have a look.
Note that the linked style guide under [3] was not accessible to me
outside Oracle. So I did my best by mimicking the release notes Iris
send me.
Especially, it was not clear to me if we should clearly mark
experimental features as such.
Cheers, Thomas
On Thu, Nov 29, 2018 at 8:54 PM Roger Riggs <roger.ri...@oracle.com> wrote:
Hi Thomas,
We'll also need a retroactive CSR for JDK 12 to change its status in JDK 12 to
be documented.
Can you take a swing at that?
On the Jira issue[2] there is a "More" menu with a 'Create CSR' button.
It comes pre-filled with a template that should be pretty straightforward to
fill out.
A CSR will also be needed for JDK 11 (pretty much a copy).
In the compatibility section, point out that it does not change the default.
I created a draft release note for JDK 12 [1].
Please review and comment or edit it directly with suggestions.
Thanks, Roger
[1] https://bugs.openjdk.java.net/browse/JDK-8214454
[2] https://bugs.openjdk.java.net/browse/JDK-8212828
On 11/28/2018 11:56 AM, Thomas Stüfe wrote:
On Wed, Nov 28, 2018 at 5:39 PM Alan Bateman <alan.bate...@oracle.com> wrote:
On 28/11/2018 15:36, Thomas Stüfe wrote:
Hi all,
I would like to have this patch in 11u too, so I just did a 11u
downport request.
Our agreement was that launchMechanism=POSIX_SPAWN would stay as
optional non-default value for jdk12, and at the start of JDK13
development we would switch the default to posix_spawn.
I would like to see this non-default-but-possible-to-set option in 11u
too, just to broaden the test surface. We'd get more testers that way.
What do you think, does that make sense?
It would be nice to have gotten feedback from people trying it out with
JDK 12 EA builds but I don't know if that is possible.
If it is backported then a CSR will be required as it will be adding a
new supported value. A release note or other documentation updates might
be needed too.
Oh, you are right. Do we have a release note/documentation for jdk12?
..Thomas
-Alan
