From Fedora Project Wiki
< Changes
(WIP save) |
No edit summary |
||
| Line 67: | Line 67: | ||
* Proposal owners: | * Proposal owners: | ||
<!-- 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?--> | ||
# Update existing wxPython package so that it is co-installable with wxPython 3 ([https://bugzilla.redhat.com/show_bug.cgi?id=1142515 currently in progress]) | |||
# Get wxPython 3 through the package review process, built, and ensure it can co-exist with wxPython 2.8 package | |||
* Other developers: <!-- REQUIRED FOR SYSTEM WIDE CHANGES --> | * Other developers: <!-- REQUIRED FOR SYSTEM WIDE 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?--> | <!-- 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?--> | ||
# For maintainers of packages that depend on wxPython, after wxPython 3 is packaged, verify that their packages continue to use wxPython 2.8 correctly when wxPython 3.0 is co-installed. A small change may be required to some packages to ensure they select wxPython 2.8 specifically. | |||
# Optional: switch packages to use wxPython 3.0. This can be done package-by-package as time permits. | |||
* Release engineering: N/A (not a System Wide Change) <!-- REQUIRED FOR SYSTEM WIDE CHANGES --> | * Release engineering: N/A (not a System Wide Change) <!-- REQUIRED FOR SYSTEM WIDE CHANGES --> | ||
| Line 122: | Line 122: | ||
* Contingency deadline: N/A (not a System Wide Change) <!-- REQUIRED FOR SYSTEM WIDE CHANGES --> | * Contingency deadline: N/A (not a System Wide Change) <!-- REQUIRED FOR SYSTEM WIDE CHANGES --> | ||
<!-- Does finishing this feature block the release, or can we ship with the feature in incomplete state? --> | <!-- Does finishing this feature block the release, or can we ship with the feature in incomplete state? --> | ||
* Blocks release? N/A (not a System Wide Change) | * Blocks release? N/A (not a System Wide Change) <!-- REQUIRED FOR SYSTEM WIDE CHANGES --> | ||
* Blocks product? | * Blocks product? N/A (not a System Wide Change) <!-- Applicable for Changes that blocks specific product release/Fedora.next --> | ||
== Documentation == | == Documentation == | ||
Revision as of 15:48, 30 November 2014
wxPython 3
Summary
Get wxPython 3 packaged and into Fedora.
Owner
- Name: Scott Talbert
- Email: swt@techie.net
- Release notes owner:
Current status
- Targeted release: Fedora 22
- Last updated: 2014-11-25
- Tracker bug: <will be assigned by the Wrangler>
Detailed Description
This change proposal aims to get wxPython 3.0 (Python bindings for the wxWidgets GUI library) packaged and into Fedora. Currently Fedora has wxPython 2.8 which has not been updated since 2011.
Benefit to Fedora
This change brings a more modern wxPython to Fedora, including support for GTK3 (currently wxPython 2.8 uses GTK2). Additionally, it moves Fedora to a supported version of wxPython.
Scope
- Proposal owners:
- Update existing wxPython package so that it is co-installable with wxPython 3 (currently in progress)
- Get wxPython 3 through the package review process, built, and ensure it can co-exist with wxPython 2.8 package
- Other developers:
- For maintainers of packages that depend on wxPython, after wxPython 3 is packaged, verify that their packages continue to use wxPython 2.8 correctly when wxPython 3.0 is co-installed. A small change may be required to some packages to ensure they select wxPython 2.8 specifically.
- Optional: switch packages to use wxPython 3.0. This can be done package-by-package as time permits.
- Release engineering: N/A (not a System Wide Change)
- Policies and guidelines: N/A (not a System Wide 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)
- Blocks product? N/A (not a System Wide Change)
Documentation
N/A (not a System Wide Change)