From Fedora Project Wiki
(Add trackers)
 
(10 intermediate revisions by 2 users not shown)
Line 42: Line 42:
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: <will be assigned by the Wrangler>
* Tracker bug: [https://bugzilla.redhat.com/show_bug.cgi?id=1803863 #1803863]
* Release notes tracker: <will be assigned by the Wrangler>
* Release notes tracker: [https://pagure.io/fedora-docs/release-notes/issue/448 #448]


== Detailed Description ==
== Detailed Description ==
Line 60: Line 60:


== Scope ==
== Scope ==
* Proposal owners: Changes to the Wiki including testing templates and release criteria.  
* Proposal owners: Changes to the Wiki including testing templates, release criteria and deliverables.


* Other developers: N/A (not a System Wide Change)  
* Other developers: N/A (not a System Wide Change)  


* Release engineering: N/A - The AArch64 Workstation spin has been available for a number of years.
* 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) <!-- REQUIRED FOR SYSTEM WIDE CHANGES -->
* Policies and guidelines: N/A (not a System Wide Change) <!-- REQUIRED FOR SYSTEM WIDE CHANGES -->
Line 86: Line 86:


== User Experience ==
== User Experience ==
<!-- If this change proposal is noticeable by users, how will their experiences change as a result?
The same Desktop experience enjoyed on x86_64. The Armhfp Xfce Desktop spin will still be produced and tested to ensure functionality.
 
This section partially overlaps with the Benefit to Fedora section above. This section should be primarily about the User Experience, written in a way that does not assume deep technical knowledge. More detailed technical description should be left for the Benefit to Fedora section.
 
Describe what Users will see or notice, for example:
  - Packages are compressed more efficiently, making downloads and upgrades faster by 10%.
  - Kerberos tickets can be renewed automatically. Users will now have to authenticate less and become more productive. Credential management improvements mean a user can start their work day with a single sign on and not have to pause for reauthentication during their entire day.
- Libreoffice is one of the most commonly installed applications on Fedora and it is now available by default to help users "hit the ground running".
- Green has been scientifically proven to be the most relaxing color. The move to a default background color of green with green text will result in Fedora users being the most relaxed users of any operating system.
-->


== Dependencies ==
== Dependencies ==
Line 114: Line 105:


== Documentation ==
== Documentation ==
<!-- Is there upstream documentation on this change, or notes you have written yourself?  Link to that material here so other interested developers can get involved. -->
This change will require some updates to Release Criteria, release blocking deliverables lists and testing matrices.
 
<!-- REQUIRED FOR SYSTEM WIDE CHANGES -->
N/A (not a System Wide Change)


== Release Notes ==
== Release Notes ==
Line 126: Line 114:
-->
-->


[[Category:ChangePageIncomplete]]
[[Category:ChangeAcceptedF32]]
<!-- 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 15:50, 17 February 2020


ARM Release Criteria Changes

Summary

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

Owner

  • Name: Paul Whalen
  • Email: pwhalen@fedoraproject.org
  • 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.

Scope

  • 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.

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

Documentation

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

Release Notes