Coherent release process

[dalibor topic]

On 12.11.2015 04:42, Quanah Gibson-Mount wrote:
 > if/when the OpenJDK project may develop a more coherent release plan?

You can find the plans for JDK 9 at 
http://openjdk.java.net/projects/jdk9/ . The plans for JDK 8 Updates are 
linked off the Project page of the corresponding JDK 8 Updates Project 
in the OpenJDK Community at http://openjdk.java.net/projects/jdk8u/ .

The corresponding Project's mailing list, jdk8u-dev, is the right place 
to ask questions about JDK 8 Updates in OpenJDK. The JDK 8 Project has 
completed its work with the JDK 8 GA a while ago, so this list is 
largely dormant.

 > The lack of consistency among branches for different releases makes
 > it extremely hard to create a well defined build process for OpenJDK.

The separate Mercurial forests existed for the convenience of developing 
multiple releases with a large number of changes and features in 
parallel within a single OpenJDK Project (just as was the case for the 
JDK 7 Updates Project, fwiw).

For reasons discussed back in July, the JDK 8 Updates Project in OpenJDK 
no longer needs to do that. Accordingly, the jdk8u master and dev 
forests are adequate for our current needs. Please see 
http://mail.openjdk.java.net/pipermail/jdk8u-dev/2015-July/003985.html 
for details.

If for some reason you strive to create your own build process for JDK 8 
Updates, I'd suggest subscribing at least to the jdk8u-dev, jdk9-dev and 
build-dev mailing lists.

Instructions for checking out the code for the latest release developed 
within the JDK 8 Updates Project in OpenJDK can be found on the 
Project's web page. Please keep in mind that CPU releases like 8u51 are 
not developed within OpenJDK Projects.

 > In addition the fact that the bug system is locked down

Please consult the "Account Eligibility" section of 
https://wiki.openjdk.java.net/display/general/JBS+Overview for the facts.

If you are not eligible for an account on JBS, because you're not an 
OpenJDK developer with an adequate role, you may still file issues 
through the web interface at bugs.java.com.

 > The following patch fixes this

Please see http://openjdk.java.net/contribute/ for how to contribute to 
OpenJDK Projects, and note in particular the requirements spelled out in 
section 0.

Of particular note for the contribution flow to the JDK 8 Updates 
Project is that changes to it will typically go through JDK 9 first.

So once your organization meets the requirements spelled out in the 
guide above, I'd suggest adjusting, testing and sending your proposed 
patch as plain text within an e-mail to the build-dev mailing list for 
JDK 9 first. Once it has been reviewed and pushed there, then you can 
follow up with a backport for the JDK 8 Updates Project. Details on the 
backport process can be found at the JDK 8 Updates page linked above.

 > As we rely heavily on being able to provide up to date, consistent,
 > secure OpenJDK builds to our customers

Unfortunately, I don't see your organization listed at 
http://www.oracle.com/technetwork/community/oca-486395.html so I'd like 
to again refer you to the guide for contributing to OpenJDK linked above.

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, Astrid Kepper, Val Maher

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