From Fedora Project Wiki

< QA‎ | Meetings

(Stub notes)
 
(Update agenda)
Line 1: Line 1:
== Proposed topics ==
= Attendees =
* Do changes to rawhide impact how to close bugs during the pending release (e.g. used to use CLOSED RAWHIDE)?
 
* Define what it means to be on the QA team, and how to gain membership
People present (lines said)
 
Regrets:
 
* [[User:liam]]
* [[User:rhe]]
 
= Agenda =
* [http://lists.fedoraproject.org/pipermail/test/2010-February/088655.html Proposed meeting agenda]
* [FIXME meetbot summary]
 
== Previous meeting follow-up ==
 
# 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:
* [[Test_Results:Fedora_13_Alpha_RC1_Install]]
* [[Test_Results:Fedora_13_Alpha_RC1_Desktop]]
 
Current RC#1 known bugs ...
* {{bz|566948}} NEW  - Input devices don't work
* {{bz|566979}} NEW  - Failed dependencies and login problem; basic video driver installation, F13 Alpha RC1.
* {{bz|566991}} NEW  - Incorrect repourl during install
* {{bz|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).
 
== 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 =
 
* 2010-01-21 - [[Test_Results:Fedora_13_Rawhide_Acceptance_Test_1|Pre-Alpha Rawhide Acceptance Test Plan #1]]
* 2010-01-28 - [[Test_Results:Fedora_13_Rawhide_Acceptance_Test_2|Pre-Alpha Rawhide Acceptance Test Plan #2]]
* 2010-02-04 - [[Test_Results:Fedora_13_Rawhide_Acceptance_Test_3|Pre-Alpha Rawhide Acceptance Test Plan #3]]
* 2010-02-04 - [[Test_Day:2010-02-04_NFS|NFSv4 Test Day]]
* 2010-02-05 - Alpha Blocker Meeting (F13Alpha) #1 ([http://lists.fedoraproject.org/pipermail/test/2010-February/088334.html recap])
* 2010-02-11 - [[QA:Fedora_13_Alpha_TC_Install_Test_Results|Test Alpha 'Test Compose' (boot media testing)]]
* 2010-02-12 - Alpha Blocker Meeting (F13Alpha) #2 ([http://meetbot.fedoraproject.org/fedora-bugzappers/2010-02-12/fedora-bugzappers.2010-02-12-16.00.html recap])
* 2010-02-12 - Alpha Test Candidate verification ([http://lists.fedoraproject.org/pipermail/test/2010-February/088377.html announcement])
* 2010-02-18 - Alpha Release Candidate verification
* 2010-02-18 - [[Test_Day:2010-02-18_Color_management|Color Management test day]]
* 2010-02-19 - Alpha Blocker Meeting (F13Alpha) #3
* '' '''WE ARE HERE''' ''
* 2010-02-24 - Alpha Go/No-Go Meeting (20:00 EST)
* 2010-02-25 - [[Test_Day:2010-02-25_YumLangpackPlugin|Yum Langpack plugin test day]]
 
= Action items =
 
* No action items
 
= IRC transcript =

Revision as of 15:52, 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 known bugs ...

  • 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).

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