QA/Meetings/20100816

= Attendees =

People present (lines said):
 * 1) jlaska (124)
 * 2) adamw (45)
 * 3) j_dulaney (34)
 * 4) maxamillion (29)
 * 5) nirik (18)
 * 6) fenris02 (16)
 * 7) kparal (14)
 * 8) fcami (7)
 * 9) ajax (7)
 * 10) zodbot (6)
 * 11) jskladan (4)
 * 12) zaniyah (4)
 * 13) jeff_hann (4)
 * 14) wwoods (3)
 * 15) jsmith (3)
 * 16) vaschenb (1)

Unable to attend:
 * 1) Liam
 * 2) Rhe
 * 3) Newgle1

= Agenda =
 * Proposed meeting agenda
 * MeetBot summary

Previous meeting follow-up

 * 1) jlaska to inquire how frequently boot.fp.org gets updated F-14 install images
 * 2) 621864 - jlaska to check-in with skvidal to see whether potential_conflict.py script updates are required for proper %ghost handling
 * 3) 622058 - jlaska to ping mgracik for guidance on pending firstboot changes

F14 Alpha test milestones

 * Owner - rhe, adamwill
 * Summary
 * F-14 Alpha RC#4 compose CD and DVD images are available for test (see https://fedorahosted.org/rel-eng/ticket/3856)
 * Alpha test results so far are positive (http://fedoraproject.org/wiki/Category:Fedora_14_Alpha_RC_Test_Results)
 * 1 blocker bug remains (see below)


 * Next steps...
 * Continue posting test results (installer or desktop)
 * Review blocker bugs
 * (MODIFIED) hang at start of X11 on fresh install from DVD -- discussion took place as to whether this issue was a blocker bug. Initial impression was that this issue is a valid alpha release blocker.  However, discussion continued after the meeting.  Stay tuned...

= Open discussion -  =

Developing action plans for Updates_Lessons

 * Owner - nirik
 * Summary
 * I setup Updates_Lessons as part of implementing the boards updates vision thing. We talked today about looking at and learning from updates issues. Would it be reasonable to file a ticket with qa track anytime there is a new update issue and then discuss it in qa how to learn from or prevent it? or would you want fesco to discuss that kind of thing.


 * Next steps...
 * nirik will raise topics in FESCO and reach out to stake-holders as needed (rel-eng, qa, devel, infrastructure etc...)
 * jlaska to fiddle with the wiki page to provide a way to clearly identify the recommendation and tracking the implementation

Nightly live composes

 * Owner - kparal
 * Summary
 * Viking-Ice raised the topic that nightly composes are probably not built from updates-testing repo
 * nirik confirmed that the nightly live images are based on dist-f14


 * Next steps...
 * No next steps required at this time

= Upcoming QA events =


 * 2010-07-29 - Test Alpha 'Test Compose'
 * 2010-07-30 - Alpha Blocker Meeting (f14alpha) #3
 * 2010-08-05 - Test Alpha Candidate
 * 2010-08-06 - Alpha Blocker Meeting (f14alpha) #4
 * 2010-08-11 - Fedora 14 Alpha Go/No-Go Meeting (17:00 EST) -- introduced 1 week schedule slip
 * 2010-08-18 - Fedora 14 Alpha Go/No-Go Meeting (17:00 EST)
 * 2010-08-24 - Alpha Public Availability

= Action items =
 * 1) adamw and jlaska to propose artwork final release criteria
 * 2) adamw to update http://fedoraproject.org/wiki/QA:Testcase_desktop_updates to better describe the test experience on live images
 * 3) jlaska to update https://fedoraproject.org/wiki/QA:Testcase_Anaconda_User_Interface_Basic_Video_Driver so that it better captures the post-install xdriver=vesa expectations
 * 4) maxamillion update rel-eng TRAC#3860 to request RC#5

= IRC Transcript =

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