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 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...") |
(→Scope) |
||
| Line 86: | Line 86: | ||
<!-- 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/ | * Release engineering: [https://pagure.io/releng/issue/10870 10870 (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 --> | ||
Revision as of 06:35, 2 July 2022
LXQt 1.1.0
Summary
Update LXQt to 1.1.0 in Fedora.
Owner
- Name: Zamir SUN
- Email: zsun#AT#fedoraproject.org
- Release notes owner:
Current status
- Targeted release: Fedora 37
- Last updated: 2022-07-02
- devel thread
- FESCo issue: #???
- Tracker bug:
- Release notes tracker:
Detailed Description
LXQt 1.1.0 released with a bunch of bugfixes and new features including but not limited to Qt6 integration, appearance changes etc. It's always good to keep Fedora users running on most recent software.
Detailed LXQt release note is available here.
Benefit to Fedora
This change brings bug fixes and enhancements to LXQt in Fedora.
Scope
- Proposal owners: Update all the LXQt related packages in Fedora.
- Other developers: N/A (not a System Wide Change)
- Release engineering: [https://pagure.io/releng/issue/10870 10870 (a check of an impact with Release Engineering is needed)
- List of deliverables: N/A (not a System Wide Change)
- 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 spin, netinstall or DVD. Or upgrade from older release. Then users should be able to test by doing any daily work.
User Experience
There will be a better user experience and some new features to explore.
Dependencies
This update is pretty self contained.
Contingency Plan
- Contingency mechanism: If I cannot make it happen, I'll just do not merge side-tag into f36 branch.
- Contingency deadline: Fedora 36 Beta Freeze
- Blocks release? N/A (not a System Wide Change)
- Blocks product? N/A
Documentation
N/A (not a System Wide Change)