#fedora-meeting: Fedora QA Meeting
Meeting started by jlaska at 16:00:42 UTC
(full logs).
Meeting summary
- gathering critical mass (jlaska, 16:01:16)
- Previous meeting follow-up (jlaska, 16:04:28)
- https://fedoraproject.org/wiki/Common_F12_bugs#preupgrade-boot
(jlaska,
16:05:27)
- https://fedoraproject.org/wiki/How_to_use_PreUpgrade
(jlaska,
16:05:40)
- https://fedorahosted.org/fedora-qa/ticket/30
(jlaska,
16:06:48)
- Security test plan (jlaska, 16:14:08)
- http://spot.livejournal.com/312216.html
(jlaska,
16:16:40)
- part#1 of this effort should involve defining a
policy (jlaska,
16:26:25)
- the QA team can support the policy by creating
test documentation (plans/cases) and providing test results
(jlaska,
16:27:10)
- ACTION: adamw to
initiate discussion w/ -devel-list and -security-list on creating a
security policy that QA can plan around (jlaska,
16:41:54)
- Enhancing Release Criteria (jlaska, 16:43:37)
- announcement -
https://www.redhat.com/archives/fedora-test-list/2009-November/msg00926.html
(jlaska,
16:45:35)
- AutoQA Update (jlaska, 16:52:57)
- Open discussion - <your topic here> (jlaska, 17:12:06)
- Open discussion - FUDCon (jlaska, 17:13:03)
- Oxf13 proposed a FUDCon discussion on the
future of FEdora development process including NFR, AutoQA,
autosigning, milestones and jet packs (jlaska,
17:15:15)
- Open discussion - dvd img target audience (jlaska, 17:15:45)
- Open discussion (jlaska, 17:25:15)
Meeting ended at 17:26:38 UTC
(full logs).
Action items
- adamw to initiate discussion w/ -devel-list and -security-list on creating a security policy that QA can plan around
Action items, by person
- adamw
- adamw to initiate discussion w/ -devel-list and -security-list on creating a security policy that QA can plan around
People present (lines said)
- jlaska (140)
- adamw (73)
- wwoods (68)
- Oxf13 (39)
- poelcat (26)
- Viking-Ice (21)
- kparal (20)
- spot (7)
- tibbs (2)
- zodbot (2)
- jwb (2)
- buggbot (1)
- tk009 (1)
- pjones (1)
- jeff_hann (1)
Generated by MeetBot 0.1.4.