From Fedora Project Wiki
< Changes
| Line 78: | Line 78: | ||
== Upgrade/compatibility impact == | == Upgrade/compatibility impact == | ||
Enduser compatibility should be preserved as much as possible. We do not expect any manual user intervention. | Enduser compatibility should be preserved as much as possible. We do not expect any required manual user intervention. | ||
<!-- What happens to systems that have had a previous versions of Fedora installed and are updated to the version containing this change? Will anything require manual configuration or data migration? Will any existing functionality be no longer supported? --> | <!-- What happens to systems that have had a previous versions of Fedora installed and are updated to the version containing this change? Will anything require manual configuration or data migration? Will any existing functionality be no longer supported? --> | ||
Revision as of 17:05, 8 September 2016
Change Proposal Name
Summary
DNF rebase to version 2.0.
Owner
- Name: Jan Silhan
- Name: Michal Luscon
- Name: Igor Gnatenko
- Email: jsilhan@redhat.com, mluscon@redhat.com, ignatenko@redhat.com
- Release notes owner:
Current status
- Targeted release: Fedora 26
- Last updated: 2016-09-08
- Tracker bug: <will be assigned by the Wrangler>
Detailed Description
DNF-2.0 is the next upcoming major version of DNF package manager. Unfortunately, it brings some incompatibilities with previous version of DNF (DNF-1) which were either needed to preserve compatibility with YUM CLI or where bigger redesigns were needed. A list of identified incompatible changes can be found here[1].
Benefit to Fedora
New major version of DNF brings many new features and bug fixes. Moreover, the support period of older versions is reaching its end.
Scope
- Proposal owners:
- complete release notes
- deliver DNF-2.0 stack to Rawhide
- Other developers:
- Owners of 3rd party DNF plugins or components depending on DNF should check and adjust their packages otherwise they may not work with DNF-2.0.
- Release engineering:
- All release engineering tools that depends on DNF should be tested against DNF-2.0.
Upgrade/compatibility impact
Enduser compatibility should be preserved as much as possible. We do not expect any required manual user intervention.
How To Test
- early adopters are welcomed to use this COPR repo for testing
- testing scenarios:
- anaconda installation
- upgrade from previous Fedora version
- core functionality: install, upgrade, remove, repoquery
- dnf-plugins: copr, system-upgrade, download
- third party software: mock, yumex
User Experience
N/A (unaffected)
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
documented differences between 1.x and 2.0