From Fedora Project Wiki
(→Agenda) |
|||
Line 18: | Line 18: | ||
* Topics to discuss: | * Topics to discuss: | ||
** should we stop shipping the broken phonon-backend-gstreamer? | ** should we stop shipping the broken phonon-backend-gstreamer? | ||
** KDE 4.2.4 updates | ** KDE 4.2.4 updates | ||
** Qt 4.5.1 updates | ** Qt 4.5.1 updates | ||
** amarok-2.1 status | ** amarok-2.1 status | ||
** patch numbering and metadata | ** patch numbering and metadata | ||
* Recent bugs: | * Recent bugs: | ||
** https://bugzilla.redhat.com/show_bug.cgi?id=502953 | ** https://bugzilla.redhat.com/show_bug.cgi?id=502953 |
Latest revision as of 18:16, 2 June 2009
Meeting Time
- 2009-06-02 16:00 UTC
- #fedora-meeting on freenode
Participants
Agenda
- Topics to discuss:
- should we stop shipping the broken phonon-backend-gstreamer?
- KDE 4.2.4 updates
- Qt 4.5.1 updates
- amarok-2.1 status
- patch numbering and metadata
- Recent bugs:
Transcript
Summary
should we stop shipping the broken phonon-backend-gstreamer?
- the consensus is to keep shipping it, it's not the default anyway (kkofler)
- ship it, there is nothing broken with it, ltinkl has been using it for some months already without any major problems
- https://bugzilla.redhat.com/show_bug.cgi?id=503260 (we've got 2 issues at least to sort out: 1. how to build support phonon (qt or standalone), 2. depending on 1, how best to build/ship phonon backends) (rdieter)
KDE 4.2.4 updates
- KDE 4.2.4 CVS done for F10/F11, builds underway (ltinkl)
- Kevin is backporting to F9 (kkofler)
- extragear and kde-l10n still TODO (ltinkl)
Qt 4.5.1 updates
- rssnow has a temporary hack, amarok-2.1 helps, and the yum issue is worked-around via a well-placed Obsoletes (rdieter)
- qt-4.5.1 is ready for stable updates (rdieter)
amarok-2.1 status
- amarok-2.1 landing... , for F-10 at least, means blocking on libgpod-0.7.0 batch update too
patch numbering and metadata
- we should unify the way we number patches and document them
- ltinkl to prepare a draft guideline on wiki
recent bugs
Bug 502953 - kdm switches manually selected session after entering userid
- we will drop the offending patch as a temporary solution (than)