From Fedora Project Wiki
(Initial load of self contained change java-openjdk 10)
 
(added RE ticket)
Line 76: Line 76:
 
<!-- What work do other developers have to accomplish to complete the feature in time for release?  Is it a large change affecting many parts of the distribution or is it a very isolated change? What are those changes?-->
 
<!-- What work do other developers have to accomplish to complete the feature in time for release?  Is it a large change affecting many parts of the distribution or is it a very isolated change? What are those changes?-->
  
* Release engineering: N/A <!--[https://pagure.io/releng/issues #Releng issue number] (a check of an impact with Release Engineering is needed) <REQUIRED FOR SYSTEM WIDE AS WELL AS FOR SELF CONTAINED CHANGES -->
+
* Release engineering: [https://pagure.io/releng/issue/7433 #7433] <!-- (a check of an impact with Release Engineering is needed) <REQUIRED FOR SYSTEM WIDE AS WELL AS FOR SELF CONTAINED CHANGES -->
 
<!-- Does this feature require coordination with release engineering (e.g. changes to installer image generation or update package delivery)?  Is a mass rebuild required?  include a link to the releng issue.  
 
<!-- Does this feature require coordination with release engineering (e.g. changes to installer image generation or update package delivery)?  Is a mass rebuild required?  include a link to the releng issue.  
 
The issue is required to be filed prior to feature submission, to ensure that someone is on board to do any process development work and testing, and that all changes make it into the pipeline; a bullet point in a change is not sufficient communication -->
 
The issue is required to be filed prior to feature submission, to ensure that someone is on board to do any process development work and testing, and that all changes make it into the pipeline; a bullet point in a change is not sufficient communication -->

Revision as of 12:42, 10 April 2018


java-openjdk 10 - rolling release for Short Term Support releases of OpenJDK

Summary

OpenJDK have release cadence of 6 months. but 3/4 of them are Short Term Supported for 6 months only. This package is designed to harbore them. Currently it is build on openJDK 10. LTSs (next is 11) will go as separate packages.

See announcement: http://mail.openjdk.java.net/pipermail/discuss/2017-September/004281.html
See java SIG plans: https://jvanek.fedorapeople.org/devconf/2018/changesInjavaReleaseProcess.pdf

Owner

  • Name: Jiri Vanek
  • Email: jvanek@redhat.com
  • Release notes owner:

Current status

  • Targeted release: Fedora 28
  • Last updated: 2018-04-10
  • Tracker bug: 1557371

Detailed Description

JDK10 is next major release of Java platform. It is bringing many cool improvements - http://openjdk.java.net/projects/jdk/10/ and is landing to your Fedora. Where it will be maintained for f27 and newer. Unluckily, it is STS (short term support) version. Between individual LTS will be always several STS. Again, please See announcement: http://mail.openjdk.java.net/pipermail/discuss/2017-September/004281.html and See java SIG plans: https://jvanek.fedorapeople.org/devconf/2018/changesInjavaReleaseProcess.pdf . So this is rolling release of all STSs to come. Its fate during the release of fresh LTS is yet to be decided. You will always be allowed to install Used LTS in fedora build root, alongside with latest STS via alternatives.

Benefit to Fedora

Fedora will keep on top of java technology, All developers and interested parties will have latest OpenJDK available (currently 10). As another benefit of this approach, build stack will not be affected, and will continue to be build by most stable LTS (currently 8, in year or so replaced by JDK 11).

Scope

  • Proposal owners:

This is isolated change. The maintainers of OpenJDK in Fedora must build the binaries, and keep them working. Still, to keep this rolling release will be soem packaging challenge. Lets see this when JDK12 (or maybe already 11) come out.

  • Other developers: Should slowly start to check theirs packages against JDK10
  • Policies and guidelines: N/A (not a System Wide Change)
  • Trademark approval: N/A (not needed for this Change)

Upgrade/compatibility impact

java-openjdk can coexists with java-1.8.0-openjdk (and possibly also with eoled java-9-openjdk). It should coexist with java-11-openjdk in future too. The update of java-openjdk v10 to v11 or v12 should be smooth and transparent.
Please note, that since java-9-openjdk config files of JDK are in /etc/java. Still, you can have several JDKs installed in parallel.

How To Test

dnf install java-openjdk
alternatives --config java
[select JDK10]
java -version
[should be 10]
alternatives --config javac
[select JDK10]
javac -version
[should be 10]

And happy hacking!


User Experience

Users will be able to write programs for JDK10 and to enjoy runtime for JDK10 specific applications

Dependencies

N/A (not a System Wide Change)

Contingency Plan

  • Contingency mechanism: (What to do? Who will do it?) N/A (not a System Wide Change)
  • Contingency deadline: N/A (not a System Wide Change)
  • Blocks release? N/A (not a System Wide Change), Yes/No
  • Blocks product? N/A

Documentation

N/A (not a System Wide Change)

Release Notes