From Fedora Project Wiki
(Initial commit)
 
Line 8: Line 8:


== Summary ==
== Summary ==
<!-- A sentence or two summarizing what this change is and what it will do. This information is used for the overall changeset summary page for each release. Note that motivation for the change should be in the Benefit to Fedora section below, and this part should answer the question "What?" rather than "Why?". -->
It will replace DNF, LIBDNF, and DNF-AUTOMATIC with the new Microdnf with a new Libdnf5 library. It is a consequence change after https://fedoraproject.org/wiki/Changes/MajorUpgradeOfMicrodnf.


== Owner ==
== Owner ==

Revision as of 10:22, 14 April 2022

Important.png
Comments and Explanations
The page source contains comments providing guidance to fill out each section. They are invisible when viewing this page. To read it, choose the "view source" link.
Copy the source to a new page before making changes! DO NOT EDIT THIS TEMPLATE FOR YOUR CHANGE PROPOSAL.
Idea.png
Guidance
For details on how to fill out this form, see the documentation.


Change Proposal Name Replace DNF with Microdnf

Summary

It will replace DNF, LIBDNF, and DNF-AUTOMATIC with the new Microdnf with a new Libdnf5 library. It is a consequence change after https://fedoraproject.org/wiki/Changes/MajorUpgradeOfMicrodnf.

Owner

  • Name: Your Name
  • Email: <your email address so we can contact you, invite you to meetings, etc. Please provide your Bugzilla email address if it is different from your email in FAS>


Current status

  • Targeted release: [[Releases/<number> | Fedora Linux <number> ]]
  • Last updated: 2022-04-14
  • FESCo issue: <will be assigned by the Wrangler>
  • Tracker bug: <will be assigned by the Wrangler>
  • Release notes tracker: <will be assigned by the Wrangler>

Detailed Description

Feedback

Benefit to Fedora

Scope

  • Proposal owners:
  • Other developers:
  • Policies and guidelines: N/A (not needed for this Change)
  • Trademark approval: N/A (not needed for this Change)
  • Alignment with Objectives:

Upgrade/compatibility impact

How To Test

User Experience

Dependencies

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


Documentation

N/A (not a System Wide Change)

Release Notes