From Fedora Project Wiki
< Changes
No edit summary |
mNo edit summary |
||
| Line 25: | Line 25: | ||
== Summary == | == Summary == | ||
DNF | Rebase DNF to 2.0. | ||
== Owner == | == Owner == | ||
| Line 34: | Line 34: | ||
* Name: [[User:jsilhan| Jan Silhan]] | * Name: [[User:jsilhan| Jan Silhan]] | ||
* Name: [[User:mluscon| Michal Luscon]] | * Name: [[User:mluscon| Michal Luscon]] | ||
* Name: [[User: | * 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: <your email address so we can contact you, invite you to meetings, etc.> | * Email: <your email address so we can contact you, invite you to meetings, etc.> | ||
| Line 71: | Line 71: | ||
<!-- 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?--> | ||
* Other developers: | * 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. | ||
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: | * Release engineering: All release enginerring tools that depends on DNF should be tested against DNF-2.0. | ||
All release enginerring tools that depends on DNF should be tested against DNF-2.0. | |||
<!-- 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. | ||
| Line 152: | Line 150: | ||
<!-- Select proper category, default is Self Contained Change --> | <!-- Select proper category, default is Self Contained Change --> | ||
[[Category:SelfContainedChange]] | <!-- [[Category:SelfContainedChange]] --> | ||
[[Category:SystemWideChange]] | |||
Revision as of 11:56, 8 September 2016
Change Proposal Name
Summary
Rebase DNF to 2.0.
Owner
- Name: Jan Silhan
- Name: Michal Luscon
- Name: Igor Gnatenko
- Email: <your email address so we can contact you, invite you to meetings, etc.>
- 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)