From Fedora Project Wiki
(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 isolated/leaf package without the impact on other packages/rest of the distribution * limited scope changes without the impact on other packages/rest of the distribution * coordinated effort within SIG with limited impact outside SIG functional area, accepted by the SIG System Wide Changes are: * cha...")
 
(Deferred by owner)
 
(5 intermediate revisions by 2 users not shown)
Line 1: Line 1:
<!-- 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 isolated/leaf package without the impact on other packages/rest of the distribution
* limited scope changes without the impact on other packages/rest of the distribution
* coordinated effort within SIG with limited impact outside SIG functional area, accepted by the SIG
System Wide Changes are:
* changes that does not fit Self Contained Changes category touching
* changes that require coordination within the distribution (for example mass rebuilds, release engineering or other teams effort etc.)
* changing system defaults
For Self Contained Changes, sections marked as "REQUIRED FOR SYSTEM WIDE CHANGES" are OPTIONAL but FESCo/Wrangler can request more details (especially in case the change proposal category is
improper or updated to System Wide category). For System Wide Changes all fields on this form are required for FESCo acceptance (when applies). 
We request that you maintain the same order of sections so that all of the change proposal pages are uniform.
-->
<!-- The actual name of your proposed change page should look something like: Changes/Your_Change_Proposal_Name.  This keeps all change proposals in the same namespace -->
<!-- The actual name of your proposed change page should look something like: Changes/Your_Change_Proposal_Name.  This keeps all change proposals in the same namespace -->
= LXQt image for aarch64 =
= LXQt image for aarch64 =


Line 34: Line 12:
* Name: [[User:Zsun|Zamir SUN]]
* Name: [[User:Zsun|Zamir SUN]]
* Email: zsun#AT#fedoraproject.org <!--- bugzilla account : sztsian # gmail.com -->
* Email: zsun#AT#fedoraproject.org <!--- bugzilla account : sztsian # gmail.com -->
* Release notes owner: <!--- To be assigned by docs team [[User:FASAccountName| Release notes owner name]] <email address> -->
<!--- UNCOMMENT only for Changes with assigned Shepherd (by FESCo)
<!--- UNCOMMENT only for Changes with assigned Shepherd (by FESCo)
* FESCo shepherd: [[User:FASAccountName| Shehperd name]] <email address>
* FESCo shepherd: [[User:FASAccountName| Shehperd name]] <email address>
Line 44: Line 21:


== Current status ==
== Current status ==
[[Category:ChangeReadyForWrangler]]
[[Category:ChangeAcceptedF39]]
<!-- 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 -->
Line 54: Line 31:
<!-- [[Category:SystemWideChange]] -->
<!-- [[Category:SystemWideChange]] -->


* Targeted release: [[Releases/38 | Fedora 38 ]]  
* Targeted release: [[Releases/39 | Fedora 39 ]]  
* Last updated: <!-- this is an automatic macro — you don't need to change this line -->  {{REVISIONYEAR}}-{{REVISIONMONTH}}-{{REVISIONDAY2}}  
* Last updated: <!-- this is an automatic macro — you don't need to change this line -->  {{REVISIONYEAR}}-{{REVISIONMONTH}}-{{REVISIONDAY2}}  
<!-- After the change proposal is accepted by FESCo, tracking bug is created in Bugzilla and linked to this page  
<!-- After the change proposal is accepted by FESCo, tracking bug is created in Bugzilla and linked to this page  
Line 64: Line 41:
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
-->
-->
* devel thread
* [https://lists.fedoraproject.org/archives/list/devel@lists.fedoraproject.org/thread/STU74CAXBTHZPTD3VD5IVFHAQDEWYRQW/ devel thread]
* FESCo issue:  
* FESCo issue: [https://pagure.io/fesco/issue/2884 #2884]
* Tracker bug:  
* Tracker bug: [https://bugzilla.redhat.com/show_bug.cgi?id=2139111 #2139111]
* Release notes tracker:
* Release notes tracker: [https://pagure.io/fedora-docs/release-notes/issue/895 #895]


== Detailed Description ==
== Detailed Description ==
Line 84: Line 61:
<!-- 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/issue/??? TO-Be-filed] (a check of an impact with Release Engineering is needed) <!-- REQUIRED FOR SYSTEM WIDE AS WELL AS FOR SELF CONTAINED CHANGES -->
* Release engineering: [https://pagure.io/releng/issue/11086 11086] (a check of an impact with Release Engineering is needed) <!-- REQUIRED FOR SYSTEM WIDE AS WELL AS FOR SELF CONTAINED 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 -->

Latest revision as of 15:35, 10 April 2023

LXQt image for aarch64

Summary

Generate LXQt image (both iso and disk image) for aarch64 architecture.

Owner

  • Name: Zamir SUN
  • Email: zsun#AT#fedoraproject.org

Current status

Detailed Description

LXQt has moved out of 0.x version and is now 1.1.0, so I consider it to be a pretty stable desktop environment. Recently, 64bit ARM architecture is becoming more and more popular in laptops and workstations. By generating a LXQt image for aarch64 will offer aarch64 another easier option to evaluate and use Fedora.

Benefit to Fedora

Offers users of 64bit ARM architecture another desktop option that works out-of-the-box.

Scope

  • Proposal owners: Nothing. The LXQt packages are already in the distribution. And the kickstart for generating LXQt image on x86_64 can be directly used.
  • Other developers: N/A (not a System Wide Change)
  • Release engineering: 11086 (a check of an impact with Release Engineering is needed)
  • 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

Install using the ISO or the disk image on aarch64 system. The system should work as it should be by manually installing on top of any existing aarch64 system.


User Experience

Users of aarch64 systems should be able to directly install from LXQt ISO or disk image if they want to use LXQt.

Dependencies

We need to ask release engineering team to generate the image.

Contingency Plan

  • Contingency mechanism: Just do not ship the newly generated image.
  • Contingency deadline: Fedora 38 Beta Freeze
  • Blocks release? N/A (not a System Wide Change)
  • Blocks product? N/A

Documentation

N/A (not a System Wide Change)

Release Notes

Retrieved from "https://fedoraproject.org/w/index.php?title=Changes/LXQt_image_for_aarch64&oldid=673519"