From Fedora Project Wiki
(Initial agenda) |
(Initial draft) |
||
| Line 1: | Line 1: | ||
= Attendees = | |||
People present (lines said) | |||
Unable to attend: | |||
# [[User:Rhe|Rhe]] (hopefully sleeping) | |||
= Agenda = | = Agenda = | ||
* [FIXME Proposed meeting agenda] | |||
* [FIXME MeetBot summary] | |||
== Previous meeting follow-up == | |||
== Call for Test Days == | |||
; Owner : [[User:jlaska|jlaska]] | |||
; Summary | |||
: Call for ideas/owners for Fedora 15 [[QA/Test_Days]] | |||
: Monitor [[Releases/15/FeatureList|list of approved features]] for ideas | |||
: [[User:Adamwill|AdamW]] initiated GNOME3 discussion on [http://lists.fedoraproject.org/pipermail/desktop/2010-November/006702.html desktop@ list] | |||
; Next steps ... | |||
: Contribute ideas to [[Talk:QA/Fedora_15_test_days]] | |||
: Identify owners to organize and host test days | |||
GNOME 3 (pre-Alpha) | |||
Xfce 4.8 | |||
X Test Week | |||
== Bodhi patch == | |||
; Owner : [[User:fcami|fcami]] | |||
; Summary | |||
: Posted a [http://lists.fedoraproject.org/pipermail/test/2010-December/095866.html bodhi patch] to improve the bugzilla comment bodhi posts when an update is available | |||
: See also {{ticket|fedora-infrastructure|701}} | |||
; Next steps ... | |||
: Is there another bodhi-1.x build planned? | |||
== Python script communicating with bugzilla == | |||
; Owner : [[User:Bruno|Bruno]] | |||
: Tune existing python scripts to detect UNTESTED blocker bugs | |||
: Bruno drafted a set of sample queries, see [[User:Bruno#Mockup_for_QA_-_Tracking_bug_queries]] | |||
; Next steps ... | |||
: See {{ticket|fedora-qa|89}} | |||
== Requirements review for Fedora test case management == | |||
; Owner : [[User:rhe|rhe]] | |||
: See {{ticket|fedora-qa|152}} | |||
: Requirements review for Fedora test case management | |||
: Drafted [[Rhe/tcms_requirements_proposal]] | |||
; Next steps ... | |||
: Gather feedback on requirements proposal | |||
: Continue refining requirements | |||
== Critical Path test case development == | |||
; Owner : [[User:adamwill|adamwill]] | |||
: Critical Path test case development | |||
; Next steps ... | |||
: See {{ticket|fedora-qa|154}} | |||
== AutoQA Update == | |||
; Owner : [[User:kparal|kparal]] | |||
; Summary | |||
# Wwoods posting blog article explaining the need for {{Ticket|autoqa|248}} | |||
# Jskladan rewriting bodhi watcher to work with depcheck (encountering depcheck issues) | |||
; Next steps ... | |||
= Open discussion - <Your topic here> = | |||
= Action items = | |||
= IRC Transcript = | |||
Revision as of 14:40, 13 December 2010
Attendees
People present (lines said)
Unable to attend:
- Rhe (hopefully sleeping)
Agenda
- [FIXME Proposed meeting agenda]
- [FIXME MeetBot summary]
Previous meeting follow-up
Call for Test Days
- Owner
- jlaska
- Summary
- Call for ideas/owners for Fedora 15 QA/Test_Days
- Monitor list of approved features for ideas
- AdamW initiated GNOME3 discussion on desktop@ list
- Next steps ...
- Contribute ideas to Talk:QA/Fedora_15_test_days
- Identify owners to organize and host test days
GNOME 3 (pre-Alpha) Xfce 4.8 X Test Week
Bodhi patch
- Owner
- fcami
- Summary
- Posted a bodhi patch to improve the bugzilla comment bodhi posts when an update is available
- See also
fedora-infrastructure ticket#701 - Next steps ...
- Is there another bodhi-1.x build planned?
Python script communicating with bugzilla
- Owner
- Bruno
- Tune existing python scripts to detect UNTESTED blocker bugs
- Bruno drafted a set of sample queries, see User:Bruno#Mockup_for_QA_-_Tracking_bug_queries
- Next steps ...
- See
fedora-qa ticket#89
Requirements review for Fedora test case management
- Owner
- rhe
- See
fedora-qa ticket#152 - Requirements review for Fedora test case management
- Drafted Rhe/tcms_requirements_proposal
- Next steps ...
- Gather feedback on requirements proposal
- Continue refining requirements
Critical Path test case development
AutoQA Update
- Owner
- kparal
- Summary
- Wwoods posting blog article explaining the need for
autoqa ticket#248 - Jskladan rewriting bodhi watcher to work with depcheck (encountering depcheck issues)
- Next steps ...