Bug 2115105 - z13 as the Baseline for IBM Z Hardware
Summary: z13 as the Baseline for IBM Z Hardware
Keywords:
Status: CLOSED CURRENTRELEASE
Alias: None
Product: Fedora
Classification: Fedora
Component: Changes Tracking
Version: 38
Hardware: Unspecified
OS: Unspecified
unspecified
unspecified
Target Milestone: ---
Assignee: Dan Horák
QA Contact:
URL:
Whiteboard:
Depends On:
Blocks: F38Changes
TreeView+ depends on / blocked
 
Reported: 2022-08-03 20:41 UTC by Ben Cotton
Modified: 2023-04-18 14:06 UTC (History)
2 users (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2023-04-18 14:06:36 UTC
Type: ---
Embargoed:


Attachments (Terms of Use)

Description Ben Cotton 2022-08-03 20:41:28 UTC
This is a tracking bug for Change: z13 as the Baseline for IBM Z Hardware
For more details, see: https://fedoraproject.org/wiki/Changes/z13BaselineForIBMZ

Move the minimal architecture level for IBM Z hardware (the s390x architecture) to z13 to benefit from the new features and better performance in the newer CPU.

If you encounter a bug related to this Change, please do not comment here. Instead create a new bug and set it to block this bug.

Comment 1 Ben Cotton 2022-08-03 20:46:24 UTC
@dan since FESCo approved this as an F38 System-Wide Change, can you please add the contingency plan to the wiki page?

Comment 2 Ben Cotton 2023-02-07 14:27:33 UTC
Today we reached the Code Complete (Testable) milestone on the F38 schedule: https://fedorapeople.org/groups/schedule/f-38/f-38-key-tasks.html

At this time, all F38 Changes should be complete enough to be testable. You can indicate this by setting this tracker to the MODIFIED status. If the Change is 100% code complete, you can set the tracker to ON_QA. If you need to defer this Change to F39, please NEEDINFO me.

Changes that have not reached at least the MODIFIED status will be given to FESCo for evaluation of contingency plans.

Comment 3 Dan Horák 2023-02-07 14:33:35 UTC
All parts have been successfully implemented.


Note You need to log in before you can comment on or make changes to this bug.