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 is...")
 
(Add trackers)
 
(6 intermediate revisions by 2 users not shown)
Line 44: Line 44:
  
 
== Current status ==
 
== Current status ==
 +
[[Category:ChangeAcceptedF33]]
 
* Targeted release: [[Releases/33 | Fedora 33 ]]  
 
* Targeted release: [[Releases/33 | Fedora 33 ]]  
 
* 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}}  
Line 54: Line 55:
 
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: <!--[https://bugzilla.redhat.com/show_bug.cgi?id=# #?]-->
+
* FESCo issue: [https://pagure.io/fesco/issue/2414 #2414]
* Release notes tracker: <!--[https://pagure.io/fedora-docs/release-notes/issue/? #?]-->
+
* Tracker bug: [https://bugzilla.redhat.com/show_bug.cgi?id=1852027 #1852027]
 +
* Release notes tracker: [https://pagure.io/fedora-docs/release-notes/issue/517 #517]
  
 
== Detailed Description ==
 
== Detailed Description ==
Line 80: Line 82:
 
<!-- 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/8076 #8076] (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/9530 #9530] (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 131: Line 133:
 
== Dependencies ==
 
== Dependencies ==
  
The package libqtxdg will be updated. Only Deepin related packages depends on this. In theory the Deepin change owner will need to be reminded. In reality I am also the DeepinDE change owner, so there aren't any risk for this aspect.
+
The package libqtxdg is updated. Only Deepin related packages depends on this. I am also part of the DeepinDE SIG and I've reminded our packagers. So no risk here now.
  
 
== Contingency Plan ==
 
== Contingency Plan ==
Line 138: Line 140:
 
* Contingency mechanism: Not announcing the update.  <!-- REQUIRED FOR SYSTEM WIDE CHANGES -->
 
* Contingency mechanism: Not announcing the update.  <!-- 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 30 Beta Freeze  <!-- REQUIRED FOR SYSTEM WIDE CHANGES -->
+
* Contingency deadline: Fedora 33 Beta Freeze  <!-- REQUIRED FOR SYSTEM WIDE CHANGES -->
 
<!-- Does finishing this feature block the release, or can we ship with the feature in incomplete state? -->
 
<!-- Does finishing this feature block the release, or can we ship with the feature in incomplete state? -->
 
* Blocks release? N/A (not a System Wide Change) <!-- REQUIRED FOR SYSTEM WIDE CHANGES -->
 
* Blocks release? N/A (not a System Wide Change) <!-- REQUIRED FOR SYSTEM WIDE CHANGES -->
Line 156: Line 158:
 
-->
 
-->
  
[[Category:ChangeReadyForWrangler]]
+
 
 
<!-- 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:38, 29 June 2020


LXQt 0.15.0

Summary

Update LXQt to 0.15.0 or later in Fedora.

Owner

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

Current status

Detailed Description

LXQt 0.15.0 just released with a bunch of bugfixes and enhancements. It's always good to keep Fedora users running on most recent software.

Detailed LXQt release note is available https://lxqt.github.io/release/2020/04/24/lxqt-0-15-0/ here].

Benefit to Fedora

This change brings bug fixes and enhancements to LXQt in Fedora.

Scope

  • Proposal owners:

1. Update all the LXQt related packages in Fedora.

2. Make lxqt-l10n noarch

3. Fix comps and/or kickstart if needed.

  • Other developers: N/A (not a System Wide Change)
  • Release engineering: #9530 (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 spin, netinstall or DVD. Or upgrade from older release. Then users should be able to test by doing any daily work.

User Experience

Users shouldn't feel any difference rather than bug fixes and new features.

Dependencies

The package libqtxdg is updated. Only Deepin related packages depends on this. I am also part of the DeepinDE SIG and I've reminded our packagers. So no risk here now.

Contingency Plan

  • Contingency mechanism: Not announcing the update.
  • Contingency deadline: Fedora 33 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