From Fedora Project Wiki
m (Add trackers)
 
(7 intermediate revisions by 2 users not shown)
Line 1: Line 1:
!THIS IS A DRAFT!
 
 
<!-- Self Contained or System Wide Change Proposal?
 
<!-- Self Contained or System Wide Change Proposal?
 
Use this guide to determine to which category your proposed change belongs to.
 
Use this guide to determine to which category your proposed change belongs to.
Line 54: Line 53:
 
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:  
+
* Tracker bug: [https://bugzilla.redhat.com/show_bug.cgi?id=1739974 #1739974]
* Release notes tracker
+
* Release notes tracker: [https://pagure.io/fedora-docs/release-notes/issue/372 #372]
  
 
== Detailed Description ==
 
== Detailed Description ==
Line 76: Line 75:
 
<!-- 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/# #?] (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/8551 #8551] (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 113: Line 112:
 
== Contingency Plan ==
 
== Contingency Plan ==
  
* Contingency mechanism: Not announce the availability of Deepin Desktop in Fedora.
+
* Contingency mechanism: Not announce the availability of Deepin Desktop 15.11 in Fedora.
 
* Contingency deadline: Beta Freeze
 
* Contingency deadline: Beta Freeze
 
* Blocks release? No.
 
* Blocks release? No.
Line 134: Line 133:
 
Release Notes are not required for initial draft of the Change Proposal but has to be completed by the Change Freeze.  
 
Release Notes are not required for initial draft of the Change Proposal but has to be completed by the Change Freeze.  
 
-->
 
-->
 
+
[[Category:ChangeAcceptedF31]]
 
<!-- 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 02:56, 12 August 2019


DeepinDE 15.11

Summary

Update the Deepin Desktop Environment to 15.11 in Fedora.

Owner

  • Name: Zamir SUN - main coordinator, packager
  • Email: zsun#AT#fedoraproject.org
  • Robin 'cheese' Lee - main packager
  • Email: cheeselee#AT#fedoraproject.org
  • Release notes owner:

Current status

Detailed Description

Update Deepin Desktop in Fedora to the newest upstream, which is 15.11.

Deepin Desktop in Fedora 30 is based on 15.9 and the changelog for 15.10 and 15.11 are

Benefit to Fedora

Fedora stays in sync with upstream and gets the latest features and bug fixes.

Scope

  • Proposal owners: Deepin Desktop 15.11 packages packaged and built in Fedora 31.
  • Other developers: N/A (not a System Wide Change)
  • Release engineering: #8551 (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

No impact should happen to current users except the bugfixes.

How To Test

Install or update your Deepin Desktop on Fedora, make sure that the desktop and all apps are usable.

User Experience

There are some improvements.

  • The default window manager will be changed to deepin-kwin (known as dde-kwin in Deepin), which consumes less memory and has better performance
  • The deepin-file-manager will support burn ISO to disks.
  • The dock - will show the capacity and the remaining time of battery.

Dependencies

N/A (not a System Wide Change)

Contingency Plan

  • Contingency mechanism: Not announce the availability of Deepin Desktop 15.11 in Fedora.
  • Contingency deadline: Beta Freeze
  • Blocks release? No.
  • Blocks product? None.

Documentation

DeepinDE-1.png

Release Notes