From Fedora Project Wiki
(Summary) |
|||
| (One intermediate revision by the same user not shown) | |||
| Line 5: | Line 5: | ||
== Participants == | == Participants == | ||
* [[KevinKofler]] | |||
* [[LukasTinkl]] | * [[LukasTinkl]] | ||
* [[RexDieter]] | * [[RexDieter]] | ||
| Line 46: | Line 46: | ||
'''rename knetworkmanager-* plugins to kde-plasma-networkmanagement-*''' | '''rename knetworkmanager-* plugins to kde-plasma-networkmanagement-*''' | ||
* we do not have knetworkmanager but plugins are still named with knetworkmanager- prefix | |||
* ''AGREED'': rdieter to rename s/knetworkmanager/kde-plasma-networkmanagement/ where needed | * ''AGREED'': rdieter to rename s/knetworkmanager/kde-plasma-networkmanagement/ where needed | ||
== Comments == | == Comments == | ||
Latest revision as of 15:41, 9 November 2010
Meeting Time
- 2010-11-09 14:00 UTC
- #fedora-meeting on freenode
Participants
Agenda
- topics to discuss:
- 4.5.3 status
- f13/qt 4.7.1
- standalone QtWebKit
- rename knetworkmanager-* plugins to kde-plasma-networkmanagement-*
- recent bugs:
- (none)
Transcript
Summary
KDE 4.5.3 update status
- ltinkl thomasj and than_ reports it's ok to pushed to updates-testing
- Kevin_Kofler to prepare updates
Fedora 13 and Qt 4.7.1
- Qt 4.7.1 released today
- do we have any strong technical case to push it to stable (as an argument for FESCo)?
- features - Qt Quick, new Qt Creator, Qt Mobility, KDE 4.6
- depends on decision on QtWebKit
- it can be more disruptive than Qt update itself
standalone QtWebKit
- rdieter to submit qtwebkit for pkg review
- than to look on assistant de
- a few issues has to be checked before we can decide both qtwebkit build and qt 4.7 update -> move discussion to ML
rename knetworkmanager-* plugins to kde-plasma-networkmanagement-*
- we do not have knetworkmanager but plugins are still named with knetworkmanager- prefix
- AGREED: rdieter to rename s/knetworkmanager/kde-plasma-networkmanagement/ where needed