From Fedora Project Wiki
< Changes
No edit summary |
|||
| (8 intermediate revisions by 2 users not shown) | |||
| Line 57: | Line 57: | ||
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=1308538 1308538] | ||
The complete implementation of this feature is available in gnome-software 3.19.90 in rawhide. | |||
== Detailed Description == | == Detailed Description == | ||
We'll implement a graphical user interface for system upgrades. The implementation will use PackageKit and the libhif stack | We'll implement a graphical user interface for system upgrades. The implementation will be similar to what the dnf system-upgrade plugin does: Download the content first, and then use systemd's offline update infrastructure for the actual installation. The main difference is that we use PackageKit and the libhif stack for the download and GNOME Software as a frontend. | ||
To determine if a new release is available, we query the https://admin.fedoraproject.org/pkgdb/api/collections/ API. | |||
Descriptions and headlines for representing the new release to the user will be taken from appstream data if available, falling back to pre-generated text if nothing is available. | |||
The feature is going to be implemented in gnome-software 3.20, but we are planning to backport this version to Fedora 23, to make this feature work for 23->24 upgrades as well. | |||
== Benefit to Fedora == | == Benefit to Fedora == | ||
| Line 69: | Line 77: | ||
== Scope == | == Scope == | ||
* Proposal owners: | * Proposal owners: | ||
** Implement this :) | ** Implement this :). | ||
<!-- 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 75: | Line 83: | ||
<!-- 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: | * Release engineering: Keep the collections API working | ||
<!-- Does this feature require coordination with release engineering (e.g. changes to installer image generation or update package delivery)? Is a mass rebuid required? If a rel-eng ticket exists, add a link here. | <!-- Does this feature require coordination with release engineering (e.g. changes to installer image generation or update package delivery)? Is a mass rebuid required? If a rel-eng ticket exists, add a link here. | ||
Please work with releng prior to feature submission, and ensure that someone is on board to do any process development work and testing; don't just assume that a bullet point in a change puts someone else on the hook.--> | Please work with releng prior to feature submission, and ensure that someone is on board to do any process development work and testing; don't just assume that a bullet point in a change puts someone else on the hook.--> | ||
** [[Fedora_Program_Management/ReleaseBlocking/Fedora{{FedoraVersionNumber|next}}|List of deliverables]]: N/A (not a System Wide Change) <!-- REQUIRED FOR SYSTEM WIDE CHANGES --> | ** [[Fedora_Program_Management/ReleaseBlocking/Fedora{{FedoraVersionNumber|next}}|List of deliverables]]: N/A (not a System Wide Change) <!-- REQUIRED FOR SYSTEM WIDE CHANGES --> | ||
<!-- Please check the list of Fedora release deliverables and list all the differences the feature brings --> | <!-- Please check the list of Fedora release deliverables and list all the differences the feature brings --> | ||
* Marketing: Provide material to represent the new release to the user | |||
* Policies and guidelines: N/A (not a System Wide Change) <!-- REQUIRED FOR SYSTEM WIDE CHANGES --> | * Policies and guidelines: N/A (not a System Wide Change) <!-- REQUIRED FOR SYSTEM WIDE CHANGES --> | ||
| Line 146: | Line 156: | ||
Fedora 24 supports graphical system upgrades. | Fedora 24 supports graphical system upgrades. | ||
[[Category: | [[Category:ChangeAcceptedF24]] | ||
<!-- 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 13:46, 16 February 2016
Graphical System Upgrades
Summary
Add support for performing system upgrades to a newer Fedora release through GNOME Software.
Owner
- Name: Kalev Lember
- Email: klember@redhat.com
- Release notes owner:
Current status
The complete implementation of this feature is available in gnome-software 3.19.90 in rawhide.
Detailed Description
We'll implement a graphical user interface for system upgrades. The implementation will be similar to what the dnf system-upgrade plugin does: Download the content first, and then use systemd's offline update infrastructure for the actual installation. The main difference is that we use PackageKit and the libhif stack for the download and GNOME Software as a frontend.
To determine if a new release is available, we query the https://admin.fedoraproject.org/pkgdb/api/collections/ API.
Descriptions and headlines for representing the new release to the user will be taken from appstream data if available, falling back to pre-generated text if nothing is available.
The feature is going to be implemented in gnome-software 3.20, but we are planning to backport this version to Fedora 23, to make this feature work for 23->24 upgrades as well.
Benefit to Fedora
This makes it easier for users to keep up to date with Fedora's rapid 6 month schedule, making sure users have an easy way to upgrade to latest Fedora.
Scope
- Proposal owners:
- Implement this :).
- Other developers: N/A (not a System Wide Change)
- Release engineering: Keep the collections API working
- List of deliverables: N/A (not a System Wide Change)
- Marketing: Provide material to represent the new release to the user
- 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
N/A (not a System Wide Change)
User Experience
N/A (not a System Wide Change)
Dependencies
N/A (not a System Wide Change)
Contingency Plan
- Contingency mechanism: (What to do? Who will do it?) N/A (not a System Wide Change)
- Contingency deadline: N/A (not a System Wide Change)
- Blocks release? N/A (not a System Wide Change), Yes/No
- Blocks product? product
Documentation
N/A (not a System Wide Change)
Release Notes
Fedora 24 supports graphical system upgrades.