2013-10-14 - Fedora QA Meeting - recap

[Adam Williamson]

As always, minutes and IRC transcript available on the wiki at
https://fedoraproject.org/wiki/QA/Meetings/20131014

Next meeting is scheduled for 2013-10-21 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/20131021 . Thanks!

TOPIC: Previous meeting follow-up
=======================================================================
	* "adamw to co-ordinate with anaconda team to get a new anaconda
	  build done and roll TC2" - this was done, TC2 went ahead and
	  by meeting time we were on TC3/TC4
	* "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" - tflink wrote up his
	  proposal[1] and submitted it to FESCo; viking-ice floated his
	  on anaconda-devel-list but had little response from
	  developers. tflink's proposal was viewed favourably by FESCo
	  and it appears[2] there will be at least some extension of the
	  F21 schedule in response to it and other considerations: F21
	  release no earlier than August 2014 

TOPIC: Fedora 20 Beta status
=======================================================================
	* TC2 was built and quite comprehensively tested, gave us a
	  good overview of current status 
	* TC3 was built but the DVD compose failed as the attempt to
	  remove gimp-help subpackages to save space[3] caused compose
	  problems.[4] TC4 was immediately built with the gimp-help
	  subpackage removal reverted to ensure a successful compose,
	  so TC4's DVD image is over-size, but it is otherwise fully
	  testable, and TC3 is a dead letter 
	* TC4 should work on the Beaglebone Black and ought to be
	  tested on it 
	* We agreed that in principle we would support a freeze
	  exception proposal for GNOME 3.10.1 to land just after Beta
	  freeze

TOPIC: Test Day result tracking
=======================================================================
	* jskladan wrote a webapp for tracking Test Day results[5],
	  documented here[6]
	* We agreed that the Test Day SOP[7] should be updated to
	  recommend use of the webapp for tracking Test Day results
	  (only), with the results to be copied into the Test Day wiki
	  page soon after the event ends (so as not to rely on the app
	  as a long term data store) 

TOPIC: Open floor
=======================================================================
N/A

Action items
=======================================================================
	* roshi will update the Test Day SOP as agreed (encourage use
	  of webapp for tracking test day results) 

1. https://fedoraproject.org/wiki/User:Tflink/f21_delay_taskbot_development_proposal
2. http://meetbot.fedoraproject.org/fedora-meeting/2013-10-09/fesco.2013-10-09-18.01.log.html
3. https://bugzilla.redhat.com/show_bug.cgi?id=1000891#c12
4. https://bugzilla.redhat.com/show_bug.cgi?id=1000891#c20
5. http://testdays.qa.fedoraproject.org/testdays
6. https://fedoraproject.org/wiki/User:Jskladan/Sandbox:TestdayApp
7. https://fedoraproject.org/wiki/QA/SOP_Test_Day_management
-- 
Adam Williamson
Fedora QA Community Monkey
IRC: adamw | Twitter: AdamW_Fedora | XMPP: adamw AT happyassassin DOT net
http://www.happyassassin.net