No edit summary |
No edit summary |
||
| Line 102: | Line 102: | ||
<!-- 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] <!-- REQUIRED FOR SYSTEM WIDE CHANGES --> | * Release engineering: N/A [https://pagure.io/releng/issues #Releng issue number] <!-- REQUIRED FOR SYSTEM WIDE 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 --> | ||
| Line 119: | Line 119: | ||
<!-- REQUIRED FOR SYSTEM WIDE CHANGES --> | <!-- REQUIRED FOR SYSTEM WIDE CHANGES --> | ||
The compatibility and upgrade path should remain completely smooth. | |||
| Line 137: | Line 138: | ||
<!-- REQUIRED FOR SYSTEM WIDE CHANGES --> | <!-- REQUIRED FOR SYSTEM WIDE CHANGES --> | ||
Install system JDK (java-17-openjdk) and ru your favorite application or development. No regression should be noted. | |||
== User Experience == | == User Experience == | ||
Because of in-tree libraries, minimal image or font rendering differences canbe spotted after very detailed investigations - https://fedoraproject.org/wiki/MoveFedoraJDKsToBecomePortableJDKs#Side_effects - still, no of th e https://fedoraproject.org/wiki/MoveFedoraJDKsToBecomePortableJDKs#Known_issues should be hit by this proposal. | |||
<!-- If this change proposal is noticeable by users, how will their experiences change as a result? | <!-- If this change proposal is noticeable by users, how will their experiences change as a result? | ||
| Line 153: | Line 158: | ||
== Dependencies == | == Dependencies == | ||
<!-- What other packages (RPMs) depend on this package? Are there changes outside the developers' control on which completion of this change depends? In other words, completion of another change owned by someone else and might cause you to not be able to finish on time or that you would need to coordinate? Other upstream projects like the kernel (if this is not a kernel change)? --> | <!-- What other packages (RPMs) depend on this package? Are there changes outside the developers' control on which completion of this change depends? In other words, completion of another change owned by someone else and might cause you to not be able to finish on time or that you would need to coordinate? Other upstream projects like the kernel (if this is not a kernel change)? --> | ||
No dependent packages should notice the change. | |||
<!-- REQUIRED FOR SYSTEM WIDE CHANGES --> | <!-- REQUIRED FOR SYSTEM WIDE CHANGES --> | ||
| Line 158: | Line 164: | ||
== Contingency Plan == | == Contingency Plan == | ||
<!-- If you cannot complete your feature by the final development freeze, what is the backup plan? This might be as simple as "Revert the shipped configuration". Or it might not (e.g. rebuilding a number of dependent packages). If you feature is not completed in time we want to assure others that other parts of Fedora will not be in jeopardy. --> | <!-- If you cannot complete your feature by the final development freeze, what is the backup plan? This might be as simple as "Revert the shipped configuration". Or it might not (e.g. rebuilding a number of dependent packages). If you feature is not completed in time we want to assure others that other parts of Fedora will not be in jeopardy. --> | ||
* Contingency mechanism: | * Contingency mechanism: Revert the patches and rework https://fedoraproject.org/wiki/MoveFedoraJDKsToBecomePortableJDKs | ||
<!-- When is the last time the contingency mechanism can be put in place? This will typically be the beta freeze. --> | <!-- When is the last time the contingency mechanism can be put in place? This will typically be the beta freeze. --> | ||
* Contingency deadline: | * Contingency deadline: before f37 release | ||
<!-- Does finishing this feature block the release, or can we ship with the feature in incomplete state? --> | <!-- Does finishing this feature block the release, or can we ship with the feature in incomplete state? --> | ||
* Blocks release? | * Blocks release? Unless the java-stack will become completely borked then no. | ||
== Documentation == | == Documentation == | ||
https://fedoraproject.org/wiki/MoveFedoraJDKsToBecomePortableJDKs | |||
== Release Notes == | == Release Notes == | ||
Revision as of 12:10, 4 May 2022
Build all JDKs in Fedora against in-tree libraries and with static stdc++lib
This document represents a proposed Change. As part of the Changes process, proposals are publicly announced in order to receive community feedback. This proposal will only be implemented if approved by the Fedora Engineering Steering Committee.
Summary
This is initial step to move JDKs to be more like other JDKs, to build proper transferable images, and to lower certification burden of each binary. Long storyshort, first step in: https://fedoraproject.org/wiki/MoveFedoraJDKsToBecomePortableJDKs
This first step will move, one by one, individual JDKs in F37 to be built --with-stdc++lib=static and against in-tree (bundeld) libraries: --with-zlib="bundled" --with-freetype="bundled" --with-libjpeg="bundled" --with-giflib="bundled" --withlibpng="bundled" --with-lcms="bundled" --with-harfbuzz="bundled"
We already made a heavy testing of the behavior, and user should not face negative experience. I'm not sure if this is
Owner
- Name: Jiri Vanek
- Email: jvanek@redhat.com
Current status
- System or Self contained change? By the changes done, this is Self Contianed Change. However from view of impact, and possible world notification, it is more System Wide Change.
- Targeted release: Fedora Linux 37
- Last updated: 2022-05-04
- FESCo issue: <will be assigned by the Wrangler>
- Tracker bug: <will be assigned by the Wrangler>
- Release notes tracker: <will be assigned by the Wrangler>
Detailed Description
Please see https://fedoraproject.org/wiki/MoveFedoraJDKsToBecomePortableJDKs for whole picture
Please see https://fedoraproject.org/wiki/MoveFedoraJDKsToBecomePortableJDKs#Move_JDKs_in_RPMs_to_become_portable for this particular step. I would rather keep the details in the main page then here.
Feedback
According to short investigations, there are already precedents, where certification is a reason to build once, certificate, and repack.
According to developers, the non-portbale JDK is causing upredicted behavior different from other JDK vendors
According to JDK packagers and testers, there is to much JDKs now, and the https://fedoraproject.org/wiki/MoveFedoraJDKsToBecomePortableJDKs#Move_Fedora_JDKs_to_become_single-built.2C_portable.2C_ordinary_JDKs.2C_while_keeping_comfortable.2C_usual_system_integration is the only way out
Benefit to Fedora
Please see https://fedoraproject.org/wiki/MoveFedoraJDKsToBecomePortableJDKs#Motivation for whole picture.
This particualr proposal's main benefit will be that Fedora's JDKs as packed in RPMs will again start to resemble upstream JDKs and other vendors build, and some platfrom specific issues disappear, while JDKs remain same in view of system integration and user expereince
Scope
- Proposal owners: push improved version of https://src.fedoraproject.org/rpms/java-latest-openjdk/pull-request/98#request_diff to all JDKs - one by one from latest, over 17 to 11 and 8. Once settled down in F37 the backport to F36 is expected.
- Other developers: really, nothing. If there will be unexpected impact to other developers, the https://fedoraproject.org/wiki/MoveFedoraJDKsToBecomePortableJDKs may need rework
- Release engineering: N/A #Releng issue number
- Policies and guidelines: N/A (not needed for this Change)
- Trademark approval: N/A (not needed for this Change)
- Alignment with Objectives:
Upgrade/compatibility impact
The compatibility and upgrade path should remain completely smooth.
How To Test
Install system JDK (java-17-openjdk) and ru your favorite application or development. No regression should be noted.
User Experience
Because of in-tree libraries, minimal image or font rendering differences canbe spotted after very detailed investigations - https://fedoraproject.org/wiki/MoveFedoraJDKsToBecomePortableJDKs#Side_effects - still, no of th e https://fedoraproject.org/wiki/MoveFedoraJDKsToBecomePortableJDKs#Known_issues should be hit by this proposal.
Dependencies
No dependent packages should notice the change.
Contingency Plan
- Contingency mechanism: Revert the patches and rework https://fedoraproject.org/wiki/MoveFedoraJDKsToBecomePortableJDKs
- Contingency deadline: before f37 release
- Blocks release? Unless the java-stack will become completely borked then no.
Documentation
https://fedoraproject.org/wiki/MoveFedoraJDKsToBecomePortableJDKs