Future jdk9u updates & 9-critical-request

[dalibor topic]

On 06.02.2018 00:17, Andrew Hughes wrote:
>> I don't think that the clean slate is as important in this Project as it was
>> for 7, when several dozens of patches could accumulate for many months in
>> the open forest before a final release.
>>
> 
> I don't follow you here, because the timing between update releases hasn't
> changed; they still occur on a quarterly cycle.

The number of patches that can accumulate in an update release Project's 
development forest prior to a release can be seen as a function of both 
time and the bar necessary to meet in order to enter the forest.

For most of its development time, that bar for issues entering jdk7u-dev 
was at effectively at P5 or higher, while the bar for this Project is 
effectively at P1. So while the timing hasn't changed between 7u and 9u, 
the bar necessary to pass to enter the forest has.

> What's not clear to me at present how any patches would even make their
> way into a release.

They can do so using the process outlined at 
http://openjdk.java.net/projects/jdk-updates/approval.html

> The problem here occurred because this release was performed behind
> the scenes and then the code for it dumped in the repository afterwards.
Indeed, every CPU release has been and will be developed in the same 
way. The scenery and actors may change, thanks to the Vulnerabilty 
Group, but the happy end won't. ;)

> There was no opportunity for anyone in the OpenJDK community to test
> it before release.

That's not correct. The OpenJDK 9.0.4 release was tested by developers 
at Oracle. Judging by http://db.openjdk.java.net/people it seems that 
Oracle employees represent at least a small part of the overall OpenJDK 
Community. ;)

> My concern is that the process from request
> to approval is not transparent. 
Push requests can be tracked here: 
https://bugs.openjdk.java.net/issues/?jql=labels%20%3D%209-critical-request%20ORDER%20BY%20updated%20DESC

When they get approved, they appear here:
https://bugs.openjdk.java.net/browse/JDK-8194739?jql=labels%20%3D%209-critical-approved%20ORDER%20BY%20updated%20DESC

When they get pushed, they appear here:
http://hg.openjdk.java.net/jdk-updates and also at
http://mail.openjdk.java.net/pipermail/jdk-updates-changes/

For example, Martin's recent push is listed at 
http://mail.openjdk.java.net/pipermail/jdk-updates-changes/2018-January/000017.html

> With 8u, I've been able to search for the mails on a backport and discovered why
> it was approved and why changes were made in the backport. How is the same
> achieved for 9u and on?

It is much easier to search JBS than mailing lists.

For example, https://bugs.openjdk.java.net/browse/JDK-8194739 is 
Severin's push approval for Zero fixes - it contains a justification, a 
link to the review thread (on the wrong mailing list, though: posts to 
jdk9-dev are unlikely to be seen by reviewers once the release reaches 
GA), and a 9-critical-approval label.

cheers,
dalibor topic
-- 
<http://www.oracle.com> Dalibor Topic | Principal Product Manager
Phone: +494089091214 <tel:+494089091214> | Mobile: +491737185961
<tel:+491737185961>

ORACLE Deutschland B.V. & Co. KG | Kühnehöfe 5 | 22761 Hamburg

ORACLE Deutschland B.V. & Co. KG
Hauptverwaltung: Riesstr. 25, D-80992 München
Registergericht: Amtsgericht München, HRA 95603

Komplementärin: ORACLE Deutschland Verwaltung B.V.
Hertogswetering 163/167, 3543 AS Utrecht, Niederlande
Handelsregister der Handelskammer Midden-Niederlande, Nr. 30143697
Geschäftsführer: Alexander van der Ven, Jan Schultheiss, Val Maher

<http://www.oracle.com/commitment> Oracle is committed to developing
practices and products that help protect the environment