As always, minutes and IRC transcript available on the wiki at https://fedoraproject.org/wiki/QA/Meetings/20131007
Next meeting is scheduled for 2013-10-14 at 1500 UTC in #fedora-meeting. If you have topics you think we should bring up at the meeting, please add them to the Wiki page at https://fedoraproject.org/wiki/QA/Meetings/20131014 . Thanks! TOPIC: Previous meeting follow-up ======================================================================= * "tflink or someone competent to talk to releng about where to file bugs in the cloud .ks and whether it needs to be packaged in the distro" - dgilmore will be making sure cloud kickstarts get added to spin-kickstarts package, cloud kickstart bugs should be reported against spin-kickstarts package going forward * "adamw to talk to anaconda devs and get a build done for beta tc1 with live keyboard bug fixed" - there was already a build ready that went into TC1. anaconda team was happy with that build for TC1 * "spstarr to work on iSCSI install testing" - spstarr not present at the meeting, did not look like testing had been done for TC1 * "adamw to look into nightly fail" - was already resolved soon after the meeting TOPIC: Fedora 20 Beta status ======================================================================= * Quite a few required tests had not yet been run for TC1, we needed to get to those for TC1/TC2 * TC1 ARM images were DOA, dgilmore and pwhalen were dealing with it * We decided it would be a good idea to build TC2 soon TOPIC: Test Day status and help wanted ======================================================================= * 2013-10-08 would be virtualization test day[1], and Thursday 2013-10-10 would be GNOME test day[2] * adamw and handsome-pirate volunteered to help out with graphics test week * Volunteers were still welcome to help run future Test Days TOPIC: Possible elongated schedule for Fedora 21 ======================================================================= * Per ticket #1178[3], FESCo wanted solid justifications for possibly providing extra development time for F21 * viking-ice suggested pushing to have anaconda development cycle adjusted to stabilize earlier in the cycle (would probably need a longer cycle to achieve) * tflink wanted to work on test automation and blocker bug app * handsome-pirate wanted to work on validation test result tracker app * adamw suggested that all those with solid ideas draw up a detailed and realistic proposal for getting somewhere concrete within an elongated release cycle and add them to the FESCo ticket, perhaps after list discussion TOPIC: Open floor ======================================================================= * viking-ice suggested a plan to assign 'QA team' members to specific packages or package groups for testing and triage tasks; further discussion needed Action items ======================================================================= * adamw to co-ordinate with anaconda team to get a new anaconda build done and roll TC2 * tflink and handsome_pirate to write up detailed proposals for projects to be worked on in a possible longer f21 schedule and post / link to them in the trac ticket 1. https://fedoraproject.org/wiki/Test_Day:2013-10-08_Virtualization 2. https://fedoraproject.org/wiki/Test_Day:2013-10-10_Gnome_3.10 3. https://fedorahosted.org/fesco/ticket/1178 -- Adam Williamson Fedora QA Community Monkey IRC: adamw | Twitter: AdamW_Fedora | XMPP: adamw AT happyassassin DOT net http://www.happyassassin.net -- test mailing list test@lists.fedoraproject.org To unsubscribe: https://admin.fedoraproject.org/mailman/listinfo/test
