< Changes
mNo edit summary |
No edit summary |
||
| (8 intermediate revisions by 2 users not shown) | |||
| Line 54: | Line 54: | ||
CLOSED as NEXTRELEASE -> change is completed and verified and will be delivered in next release under development | CLOSED as NEXTRELEASE -> change is completed and verified and will be delivered in next release under development | ||
--> | --> | ||
* Tracker bug: | * Tracker bug: [https://bugzilla.redhat.com/show_bug.cgi?id=1551325 #1551325] | ||
* Release Notes tracking: [https://pagure.io/fedora-docs/release-notes/issue/124 #124] | |||
== Detailed Description == | == Detailed Description == | ||
| Line 77: | Line 78: | ||
<!-- 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?--> | ||
* Release engineering: [https://pagure.io/releng/ | * Release engineering: [https://pagure.io/releng/issue/7319 #7319] (a check of an impact with Release Engineering is needed) <!-- REQUIRED FOR SYSTEM WIDE AS WELL AS FOR SELF CONTAINED CHANGES --> | ||
<!-- Does this feature require coordination with release engineering (e.g. changes to installer image generation or update package delivery)? Is a mass rebuild required? include a link to the releng issue. | <!-- Does this feature require coordination with release engineering (e.g. changes to installer image generation or update package delivery)? Is a mass rebuild required? include a link to the releng issue. | ||
The issue is required to be filed prior to feature submission, to ensure that someone is on board to do any process development work and testing, and that all changes make it into the pipeline; a bullet point in a change is not sufficient communication --> | The issue is required to be filed prior to feature submission, to ensure that someone is on board to do any process development work and testing, and that all changes make it into the pipeline; a bullet point in a change is not sufficient communication --> | ||
| Line 150: | Line 151: | ||
--> | --> | ||
[[Category: | [[Category:ChangeAcceptedF29]] | ||
<!-- When your change proposal page is completed and ready for review and announcement --> | <!-- When your change proposal page is completed and ready for review and announcement --> | ||
<!-- remove Category:ChangePageIncomplete and change it to Category:ChangeReadyForWrangler --> | <!-- remove Category:ChangePageIncomplete and change it to Category:ChangeReadyForWrangler --> | ||
Latest revision as of 19:47, 4 March 2018
Drop Legacy GTK+ GUI in wireshark
Summary
Owner
- Name: Michal Ruprich
- Email: mruprich@redhat.com
- Release notes owner:
Current status
- Targeted release: Fedora 29
- Last updated: 2018-03-04
- Tracker bug: #1551325
- Release Notes tracking: #124
Detailed Description
Since wireshark-2.0 there are two GUIs availble for use. One is based on GTK+ and the other on Qt. The upstream focuses on the development of the Qt-based GUI and the GTK-based GUI has been marked as legacy. Since wireshark 2.4.0 the GTK-based GUI is not supported anymore and it is disabled by default. We should drop the GTK-based wireshark in Fedora 29.
Benefit to Fedora
New features and bug fixes will only be delivered for Qt-based GUI by the upstream.
Scope
- Proposal owners:
This is an isolated change. The new GUI is more or less the same as the new one. It does not affect any functionality of wireshark package. This will be a very easy change from developer point of view.
- Other developers: N/A (not a System Wide Change)
- Release engineering: #7319 (a check of an impact with Release Engineering is needed)
- List of deliverables: N/A (not a System Wide Change)
- Policies and guidelines: N/A (not a System Wide Change)
- Trademark approval: N/A (not needed for this Change)
Upgrade/compatibility impact
N/A (not a System Wide Change)
How To Test
1. simply try to install wireshark-gtk package and the operation should fail. The same should happen for wireshark-qt because wireshark-qt would become the default package and would be renamed simply as wireshark.
User Experience
N/A (not a System Wide Change)
Dependencies
This is a standalone package.
N/A (not a System Wide Change)
Contingency Plan
- Contingency mechanism: Do this change in Fedora 29, it may be done right after Fedora 28 is branched and Rawhide becomes branch for Fedora 29
- 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)