From Fedora Project Wiki
< Changes
mNo edit summary |
(→Owner) |
||
| Line 36: | Line 36: | ||
* Name: [[User:ignatenkobrain|Igor Gnatenko]] | * Name: [[User:ignatenkobrain|Igor Gnatenko]] | ||
<!-- Include you email address that you can be reached should people want to contact you about helping with your change, status is requested, or technical issues need to be resolved. If the change proposal is owned by a SIG, please also add a primary contact person. --> | <!-- Include you email address that you can be reached should people want to contact you about helping with your change, status is requested, or technical issues need to be resolved. If the change proposal is owned by a SIG, please also add a primary contact person. --> | ||
* Email: | * Email: jsilhan@redhat.com, mluscon@redhat.com, ignatenko@redhat.com | ||
* Release notes owner: <!--- To be assigned by docs team [[User:FASAccountName| Release notes owner name]] <email address> --> | * Release notes owner: <!--- To be assigned by docs team [[User:FASAccountName| Release notes owner name]] <email address> --> | ||
<!--- UNCOMMENT only for Changes with assigned Shepherd (by FESCo) | <!--- UNCOMMENT only for Changes with assigned Shepherd (by FESCo) | ||
Revision as of 15:51, 8 September 2016
Change Proposal Name
Summary
Rebase DNF to 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.
Benefit to Fedora
DNF-2.0 brings many new features and bug fixes. [Release Notes]
Scope
- Proposal owners:
- Other developers: Owners of 3rd party DNF plugins or components depending on DNF should adjust their packages otherwise they may not work with DNF-2.
- Release engineering: All release enginerring tools that depends on DNF should be tested against DNF-2.0.
- List of deliverables: N/A (not a System Wide Change)
- Policies and guidelines: N/A (not a System Wide Change)
Upgrade/compatibility impact
Enduser compatibility should be preserved as much as possible. Only minor
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)