From Fedora Project Wiki

< QA‎ | Meetings

m (Add wiki link)
m (Add meetbot links)
Line 10: Line 10:
= Agenda =
= Agenda =
* [http://lists.fedoraproject.org/pipermail/test/2010-February/088655.html Proposed meeting agenda]
* [http://lists.fedoraproject.org/pipermail/test/2010-February/088655.html Proposed meeting agenda]
* [FIXME meetbot summary]
* [http://meetbot.fedoraproject.org/fedora-meeting/2010-02-22/fedora-qa.2010-02-22-16.00.html meetbot summary]


== Previous meeting follow-up ==
== Previous meeting follow-up ==

Revision as of 17:10, 22 February 2010

Attendees

People present (lines said)

Regrets:

Agenda

Previous meeting follow-up

  1. No follow-up items

Fedora 13 Alpha test status

Alpha Test Compose verification has completed. From the wiki pages, there were 26 bugs filed.

Alpha RC#1 is available for testing. Instructions for downloading and providing feedback available at:

Current RC#1 bugs listed as blocking the Fedora_13_Alpha_Release_Criteria ...

  • RHBZ #566948 NEW - Input devices don't work
  • RHBZ #566979 NEW - Failed dependencies and login problem; basic video driver installation, F13 Alpha RC1.
  • RHBZ #566991 NEW - Incorrect repourl during install
  • RHBZ #566995 NEW - /etc/selinux/targeted/contexts/files/file_contexts: Multiple different specifications for /var/lib/cobbler/webui_sessions(/.*)? (system_u:object_r:httpd_cobbler_content_rw_t:s0 and system_u:object_r:public_content_rw_t:s0).
  • RHBZ #566460 ASSIGNED - kernel 2.6.33 strips coredump when using pipe in core_pattern

Open discussion - <Your topic here>

development/13 bug procedures

Are there documentation updates needed for filing and closing development/13 bugs?

Defining the QA team

A topic we may want to visit in the future ... define what it means to be on the QA team, and how to gain membership.

Upcoming QA events

Action items

  • No action items

IRC transcript