From Fedora Project Wiki

< Changes

Revision as of 15:50, 17 February 2020 by Bcotton (talk | contribs) (Add trackers)
(diff) ← Older revision | Latest revision (diff) | Newer revision → (diff)

ARM Release Criteria Changes


Proposed changes to the Desktop release criteria for ARM and AArch64 in Fedora 32:

  • drop Xfce on 32-bit ARM from release blocking desktops
  • add Workstation on AArch64 to release blocking desktops


  • Name: Paul Whalen
  • Email:
  • Responsible WG: ARM SIG

Current status

Detailed Description

In Fedora 32 we will have a couple new additions to release blocking deliverables including IoT and CoreOS. In order to reduce the overall test coverage and release blocking desktops we propose no longer blocking on the 32-Bit ARM Xfce Desktop spin, and adding Workstation on AArch64 as a release blocking desktop. The AArch64 Workstation image has been available for a number of Fedora releases and contains the same package set as x86_64 where it is heavily tested.

Release blocking image changes:

  • Drop: Spins/armhfp/images/Fedora-Xfce-armhfp-_RELEASE_MILESTONE_-sda.raw.xz
  • Add: Workstation/aarch64/images/Fedora-Workstation-aarch64-_RELEASE_MILESTONE_-sda.raw.xz

Benefit to Fedora

This change will reduce the release blocking desktops and potential for blocker bugs.


  • Proposal owners: Changes to the Wiki including testing templates, release criteria and deliverables.
  • Other developers: N/A (not a System Wide Change)
  • Release engineering: Small tweaks to the pungi config to make the compose fail on AArch64 Workstation and not fail on armhfp Xfce. The AArch64 Workstation spin has been available for a number of years.
  • Policies and guidelines: N/A (not a System Wide Change)
  • Trademark approval: N/A (not needed for this Change)

Upgrade/compatibility impact

N/A (not a System Wide Change)

How To Test

N/A (not a System Wide Change)

User Experience

The same Desktop experience enjoyed on x86_64. The Armhfp Xfce Desktop spin will still be produced and tested to ensure functionality.


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? product


This change will require some updates to Release Criteria, release blocking deliverables lists and testing matrices.

Release Notes