QA/Meetings/20090520

= Attendees =


 * Adam Williamson (adamw)
 * Will Woods (wwoods)
 * François Cami (fcami)
 * John Poelstra (poelcat)
 * James Laska (jlaska)
 * Jesse Keating (f13)

= Previous meeting follow-up =


 * 1) [adamw] - BugStatusWorkFlow - to file a ticket to get bodhi fixed
 * 2) * https://fedorahosted.org/bodhi/ticket/320 is the ticket, lmacken will look into this


 * 1) [adamw] - BugStatusWorkFlow - ask bugzilla guys to add a link from the bugzilla fields description page to the wiki page, for fedora
 * 2) * No updates just yet, will keep on the list for next week.


 * 1) [jlaska] - Send informal test day feedback survey to fedora-test-list and test day participants
 * 2) * drafted thanks to Chris Ward, plan to send this week


 * 1) [poelcat] - Propose updated F12 schedule with blocker bug dates
 * 2) * Checkin next week for a F12 schedule review


 * 1) [wwoods] - write a few more upgrade cases (encrypted root upgrade)
 * 2) * No updates, keep on the list for next week

= Autoqa update =


 * Project page - http://autoqa.fedorahosted.org

No updates this week. Will indicated efforts have been tied up with blocker-chasing, but this is still on the list.

= F-11-GA Preparation =


 * Blocker bugs (by component) - http://tinyurl.com/pqeq6n
 * Schedule - http://fedoraproject.org/wiki/Releases/11/Schedule
 * An additional blocker bug meeting will be hosted this Friday, May 22, 2009 ... stay tuned for announcement.

Nothing major to discuss, just reminding folks about the 1 week slip to the F-11 GA.

Adamw noted the blocker bug component report was incorrect and included F11IntelKMS as a F11Blocker bug. The report was updated.

= F-11 Common Bugs =

Bring out your bugs! Discussion around documenting known and open Fedora 11 issues in Common_F11_bugs.

Jlaska noted that the QA schedule gives more time to complete outstanding storage testing, but also provides time to document pain points for the release. The understanding is that we have the [F11 common bugs] page to fill this need but it's quite bare and in need info around some of the more popular pain points for the release, including:
 * 1) Known rough installation issues
 * 2) Outstanding X and KMS issues (intel, nouveau, radeon)
 * 3) Outstanding Alsa/pulse sound issues

Adamw noted he has experience doing similar activities and would be happy to coordinate developing the page for F11.

The Current list of bugs with  (note, this likely includes old bugs that don't apply).

Jlaska has privately been using  to tag bugs in need of documentation. Adamw indicated there needs to be a clear demarcation between release notes and common issues. Ideally there should be a separate flag for requiring a common_issue note rather than a release_note. Adamw proposed the distinction between release notes and common issues is simple: release notes is for features, common issues is for bugs.
 * release notes is for things that are different in the new release *intentionally*, we changed them because we wanted to
 * common issues is for things that are basically broken - i.e. the changed or odd behavior is not what we want

Wwoods discussed several preupgrade issues that should be fixed for the final release, and asked for the best avenue to document these issues.

Adamw pointed to the useful Fedora 10 Common bugs - http://fedoraproject.org/wiki/Bugs/F10Common. Adam offered to clean up the Fedora 11 Common bugs page and offer a "template" for use with later additions to the page. Adam also suggested keeping the Common Bugs page as a living document. The wiki should be updated as issues are fixed, with links to bodhi errata if applicable. While this may be difficult to enforce, handling the majority of Common Bugs this way should prove for a pleasant user experience.

Several in the meeting took action items to help flesh out content for the common bugs page. Plan to check in next meeting.

= Open discussion =

xorg-x11-drv-ati concerns
Fcami expressed concerns that while xorg-x11-drv-ati is good now, it's not optimal on some configurations. AMD dropped fglrx support for R400 and older, so we might see fedora does not work anymore for me threads from people who used to rely on fglrx to get their systems working (mostly the case for IGPs).

Adamw noted other distros that have already released have begun to see this.

Consensus was that nothing could be done immediately, but fcami asked if things could be made more clear for users to file bugs (i.e. dmesg with drm.debug=1 and Xorg.0.log logs). Adamw directed folks to https://fedoraproject.org/wiki/BugsAndFeatureRequests.

Fcami planned to check in with the fedora docs team to see about adding this link to the release notes for future releases.

= Upcoming QA events =


 * 2009-05-26 - BugZappers/Triage_days

= Next Meeting =


 * 2009-05-27 16:00 UTC

= Action items =

Carry over from previous week:
 * 1) [adamw] - BugStatusWorkFlow - ask bugzilla guys to add a link from the bugzilla fields description page to the wiki page, for fedora
 * 2) [jlaska] - Send informal test day feedback survey to fedora-test-list and test day participants
 * 3) [poelcat] - Check-in on F12 schedule updates
 * 4) [wwoods] - write a few more upgrade cases (encrypted root upgrade)

New items:
 * 1) [adamw] - clean up the Common_F11_bugs page to prime contributions from others
 * 2) [adamw] - ping fedora docs team for possible collaboration around common bug edits or translation
 * 3) [jlaska] - contribute installer issues to Common_F11_bugs
 * 4) [fcami+adamw] - contribute X and KMS issues to Common_F11_bugs
 * 5) [adamw] - contribute alsa/pulseaudio issues to Common_F11_bugs

= IRC Transcript =

Generated by irclog2html.py 2.7 by [mailto:marius@pov.lt Marius Gedminas] - find it at mg.pov.lt!