From Fedora Project Wiki
< Changes
No edit summary |
m (Add trackers) |
||
| (6 intermediate revisions by 2 users not shown) | |||
| Line 44: | Line 44: | ||
== Current status == | == Current status == | ||
[[Category: | [[Category:ChangeAcceptedF36]] | ||
<!-- 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 64: | Line 64: | ||
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 | ||
--> | --> | ||
* FESCo issue: | * [https://lists.fedoraproject.org/archives/list/devel@lists.fedoraproject.org/thread/MIQHSZVONUC7YXVLA6KCD4IWV7IPP3HY/ devel thread] | ||
* Tracker bug: | * FESCo issue: [https://pagure.io/fesco/issue/2707 #2707] | ||
* Release notes tracker: | * Tracker bug: [https://bugzilla.redhat.com/show_bug.cgi?id=2032951 #2032951] | ||
* Release notes tracker: [https://pagure.io/fedora-docs/release-notes/issue/780 #780] | |||
== Detailed Description == | == Detailed Description == | ||
| Line 79: | Line 80: | ||
== Scope == | == Scope == | ||
* Proposal owners: | * Proposal owners: Update all the LXQt related packages in Fedora. And fix the kickstart file if needed. | ||
<!-- What work do the feature owners 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 the feature owners 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?--> | ||
| Line 88: | 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/10405 #10405] (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 --> | ||
| Line 144: | Line 142: | ||
<!-- If you cannot complete your feature by the final development freeze, what is the backup plan? This might be as simple as "Revert the shipped configuration". Or it might not (e.g. rebuilding a number of dependent packages). If you feature is not completed in time we want to assure others that other parts of Fedora will not be in jeopardy. --> | <!-- If you cannot complete your feature by the final development freeze, what is the backup plan? This might be as simple as "Revert the shipped configuration". Or it might not (e.g. rebuilding a number of dependent packages). If you feature is not completed in time we want to assure others that other parts of Fedora will not be in jeopardy. --> | ||
* Contingency mechanism: | * Contingency mechanism: If I cannot make it happen, I'll just do not merge side-tag into f36 branch. <!-- REQUIRED FOR SYSTEM WIDE CHANGES --> | ||
<!-- When is the last time the contingency mechanism can be put in place? This will typically be the beta freeze. --> | <!-- When is the last time the contingency mechanism can be put in place? This will typically be the beta freeze. --> | ||
* Contingency deadline: Fedora 36 Beta Freeze <!-- REQUIRED FOR SYSTEM WIDE CHANGES --> | * Contingency deadline: Fedora 36 Beta Freeze <!-- REQUIRED FOR SYSTEM WIDE CHANGES --> | ||
Latest revision as of 14:37, 15 December 2021
LXQt 1.0.0
Summary
Update LXQt to 1.0.0 in Fedora.
Owner
- Name: Zamir SUN
- Email: zsun#AT#fedoraproject.org
- Release notes owner:
Current status
- Targeted release: Fedora 36
- Last updated: 2021-12-15
- devel thread
- FESCo issue: #2707
- Tracker bug: #2032951
- Release notes tracker: #780
Detailed Description
LXQt 1.0.0 released with a bunch of bugfixes and new features. 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. And fix the kickstart file if needed.
- Other developers: N/A (not a System Wide Change)
- Release engineering: #10405 (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 many 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)