From Fedora Project Wiki

< QA‎ | Meetings

(Initial draft)
 
m (Small change)
Line 36: Line 36:
== Bodhi QA workflow status check-in ==
== Bodhi QA workflow status check-in ==


* [[User:adamwill|adamw]] asked lmacken and mathieu for a heads up as to when the improved feedback system will be available.  Adamw noted that mathieu is working on it in the 'tg2 branch' (turbogears 2).  Jlaska asked if there were requirements for bodhi-2 posted, adamw indicated that [http://lists.fedoraproject.org/pipermail/devel/2010-March/134087.html his earlier email], and dledford's, were being used as the initial requirements.
https://fedorahosted.org/bodhi/milestone/2.0


== Proventesters check-in ==
== Proventesters check-in ==

Revision as of 13:34, 26 April 2010

Attendees

People present (lines said):

Regrets:

Agenda

  • [FIXME Proposed meeting agenda]
  • [FIXME MeetBot summary]

Previous meeting follow-up

  • jlaska + fenris02 to review whether F-13-Beta is an option for boot.fedoraproject.org
    • Already completed by the infrastructure team, yay infrastructure!

See agenda below for additional follow-up items included in specific topics

Fedora 13 RC test status

Upcoming test milestones:

  • 2010-04-16 - Pre-RC Branched Acceptance Test Plan -- DELAYED, now INPROGRESS
  • 2010-04-23 - Final Blocker Meeting (f13blocker) #2 (recap)
  • 2010-04-29 - Test 'Final' Test Compose
  • 2010-04-30 - Final Blocker Meeting (f13blocker) #3
  • 2010-05-05 - Final Blocker Meeting (f13blocker) #4
  • 2010-05-06 - Test 'Final' RC

Upcoming test days:

Important.png
Fedora 13 QA Retrospective
Ideas have already been coming in since F-13-Alpha. It's not too early to note QA issues you felt where handled well, or could have been improved. Your ideas will be used during F-14 QA goal planning. Voice your comments at Fedora_13_QA_Retrospective.

Bodhi QA workflow status check-in

https://fedorahosted.org/bodhi/milestone/2.0

Proventesters check-in

Package Acceptance Test Plan check-in

AutoQA check-in

There has been a lot of AutoQA activities in recent weeks, Jlaska asked the group to walk through some highlights.

Josef Skladanka updated the group on several AutoQA activities:

  1. Getting URLs of test results from AutoQA testruns is nearly finished. Patches out for review on autoqa-devel@lists.fedorahosted.org
  2. The beakerlib-based initscript test is now in production (see sample results)
  3. Making progress on the resultsDB - We have finished the db schema (see AutoQA_resultsdb_schema) and accepted a input API (see AutoQA_resultsdb_API)
  4. Next steps ...
    • Prototyping the resultsdb and using an XMLRPC based API to populate with results (jlaska, 16:06:12)
    • Creating a front-end which will be used for review/publish the data

Kamil Páral updated the group on his AutoQA focus areas:

  1. In addition to the notes above from Josef, working with Petr Splichal to automate the QA:Package_Sanity_Test_Plan (track plans using the autoqa PST milestone).
  2. Package Sanity ensures clean install, removal, upgrade, etc of the packages (see sample test output). There is already a 'pst' script in the repository which you can try to perform sanity tests on a downloaded package or package in a repo.
  3. Next steps ...
    • detect that new updates are pushed to bodhi
    • download the package and all relevant packages

Will Woods provide some updates on his AutoQA focus areas:

  1. We have enough info about current bodhi to write a bodhi update watcher, but it may have some shortcomings and will soon be obsoleted
  2. We have a proposed storage encoding for putting test plan metadata in the wiki (see QA:Test_Plan_Metadata_Test_Page), this will be used by the resultsdb

Open discussion - <Your topic here>

Upcoming QA events

Action items

IRC Transcript

Retrieved from "https://fedoraproject.org/w/index.php?title=QA/Meetings/20100426&oldid=169044"