From Fedora Project Wiki
< Changes
(Created page with "<!-- Self Contained or System Wide Change Proposal? Use this guide to determine to which category your proposed change belongs to. Self Contained Changes are: * changes to is...") |
mNo edit summary |
||
| (8 intermediate revisions by 4 users not shown) | |||
| Line 26: | Line 26: | ||
<!-- A sentence or two summarizing what this change is and what it will do. This information is used for the overall changeset summary page for each release. | <!-- A sentence or two summarizing what this change is and what it will do. This information is used for the overall changeset summary page for each release. | ||
Note that motivation for the change should be in the Motivation section below, and this part should answer the question "What?" rather than "Why?". --> | Note that motivation for the change should be in the Motivation section below, and this part should answer the question "What?" rather than "Why?". --> | ||
After a number of projects dropped support for the big endian ppc64 architecture and our move of ppc64 to "maintenance-only" mode few releases back, now a vital dependency, the Eclipse project, stops supporting ppc64. As a consequence we need to discontinue producing any ppc64 content. This is a long time anticipated step as the upstream focus on the little endian variant (ppc64le) on Linux is well known. | After a number of projects dropped support for the big endian ppc64 architecture and our move of ppc64 to "maintenance-only" mode few releases back, now a vital dependency, the Eclipse project, stops supporting ppc64. As a consequence we need to discontinue producing any ppc64 content. This is a long time anticipated step as the upstream focus on the little endian variant (ppc64le) on Linux is well known. My [https://lists.fedoraproject.org/archives/list/ppc@lists.fedoraproject.org/message/D6G5RQUTRYGZ5Y4XIPMADMUSH2PTZDO4/ email] sent to the Fedora PPC mailing list has few more details. | ||
== Owner == | == Owner == | ||
| Line 56: | Line 56: | ||
CLOSED as NEXTRELEASE -> change is completed and verified and will be delivered in next release under development | CLOSED as NEXTRELEASE -> change is completed and verified and will be delivered in next release under development | ||
--> | --> | ||
* Tracker bug: | * Tracker bug: [https://bugzilla.redhat.com/show_bug.cgi?id=1601599 #1601599] | ||
== Detailed Description == | == Detailed Description == | ||
| Line 101: | Line 101: | ||
<!-- 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: [https://pagure.io/releng/ | * Release engineering: [https://pagure.io/releng/issue/7602 #7602] (a check of an impact with Release Engineering is needed) <!-- REQUIRED FOR SYSTEM WIDE AS WELL AS FOR SELF CONTAINED CHANGES --> changes in koji, bodhi and pungi configurations are expected | ||
<!-- 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 --> | ||
** [[Fedora_Program_Management/ReleaseBlocking/Fedora{{FedoraVersionNumber|next}}|List of deliverables]]: N/A | ** [[Fedora_Program_Management/ReleaseBlocking/Fedora{{FedoraVersionNumber|next}}|List of deliverables]]: N/A | ||
<!-- Please check the list of Fedora release deliverables and list all the differences the feature brings --> | <!-- Please check the list of Fedora release deliverables and list all the differences the feature brings --> | ||
| Line 151: | Line 151: | ||
<!-- REQUIRED FOR SYSTEM WIDE CHANGES --> | <!-- REQUIRED FOR SYSTEM WIDE CHANGES --> | ||
none | |||
== Contingency Plan == | == Contingency Plan == | ||
| Line 167: | Line 167: | ||
<!-- REQUIRED FOR SYSTEM WIDE CHANGES --> | <!-- REQUIRED FOR SYSTEM WIDE CHANGES --> | ||
Fedora 28 was the last that was released with ppc64 content. | |||
== Release Notes == | == Release Notes == | ||
| Line 175: | Line 175: | ||
Release Notes are not required for initial draft of the Change Proposal but has to be completed by the Change Freeze. | Release Notes are not required for initial draft of the Change Proposal but has to be completed by the Change Freeze. | ||
--> | --> | ||
Fedora 28 was the last that was released with ppc64 content. | |||
[[Category: | [[Category:ChangeAcceptedF29]] | ||
<!-- When your change proposal page is completed and ready for review and announcement --> | <!-- When your change proposal page is completed and ready for review and announcement --> | ||
<!-- remove Category:ChangePageIncomplete and change it to Category:ChangeReadyForWrangler --> | <!-- remove Category:ChangePageIncomplete and change it to Category:ChangeReadyForWrangler --> | ||
Latest revision as of 19:53, 16 July 2018
Discontinue PPC64 as Alternative Architecture
Summary
After a number of projects dropped support for the big endian ppc64 architecture and our move of ppc64 to "maintenance-only" mode few releases back, now a vital dependency, the Eclipse project, stops supporting ppc64. As a consequence we need to discontinue producing any ppc64 content. This is a long time anticipated step as the upstream focus on the little endian variant (ppc64le) on Linux is well known. My email sent to the Fedora PPC mailing list has few more details.
Owner
- Name: Dan Horák
- Email: <sharkcz at fedoraproject dot org>
- Release notes owner:
Current status
Detailed Description
Fedora will stop producing ppc64 content - binary rpms or composes.
Benefit to Fedora
Without this step Fedora build system would be blocked at some point as some build dependencies couldn't be resolved.
Scope
- Proposal owners: synchronize with rel-engs
- Other developers: none
- Release engineering: #7602 (a check of an impact with Release Engineering is needed) changes in koji, bodhi and pungi configurations are expected
- List of deliverables: N/A
- Policies and guidelines: none
- Trademark approval: N/A (not needed for this Change)
Upgrade/compatibility impact
There won't be composes or updates available for Fedora 29, users are advised to move to the little endian ppc64le variant.
How To Test
- check if no ppc64 rpms or composes are produced
User Experience
Dependencies
none
Contingency Plan
- Contingency mechanism: (What to do? Who will do it?) hire Eclipse developer and convince upstream now, repeat for other projects later
- Contingency deadline: N/A
- Blocks release? Yes
- Blocks product? all, because the build system will stop
Documentation
Fedora 28 was the last that was released with ppc64 content.
Release Notes
Fedora 28 was the last that was released with ppc64 content.