Future jdk9u updates & 9-critical-request

[dalibor topic]

On 29.01.2018 19:26, Andrew Hughes wrote:
> If Oracle want to leave
> future maintainers
> with a "clean slate", there needs to be a concluding feature release
> i.e. something we
> can openly contribute to, as we did under 7 and 8. 

The role that feature releases used to play in the update release series 
now falls squarely onto the shoulders of the major releases. Update 
releases are strictly limited to fixes of security issues, regressions, 
and bugs in newer features.

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.

In the case of the updates in this Project, I think one can expect at 
most a handful or two of additional changes to be requested and approved 
in the two months between the last release and the next major release.

Given that the requests and approvals and commits [0] can all be easily 
tracked, they shouldn't come as a huge surprise to a potential future 
maintainer.

cheers,
dalibor topic

[0] 
http://mail.openjdk.java.net/pipermail/jdk-updates-changes/2018-January/thread.html
-- 
<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