2010-06-28 - Fedora QA meeting recap

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



As always, notes and IRC transcript available at
https://fedoraproject.org/wiki/QA/Meetings/20100628

= Attendees =

People present (lines said):
      * jlaska (113)
      * kparal (70)
      * adamw (64)
      * j_dulaney (38)
      * wwoods (35)
      * Oxf13 (9)
      * jskladan (7)
      * Viking-Ice (7)
      * skvidal (6)
      * zodbot (5)
      * hicham (5)
      * chenrano2002 (5)
      * ianweller (4)
      * jraber (2) 

Regrets:
      * liam
      * rhe

= Agenda =
      * Proposed meeting agenda -
        http://lists.fedoraproject.org/pipermail/test/2010-June/091736.html 
      * MeetBot summary -
        http://meetbot.fedoraproject.org/fedora-meeting/2010-06-28/fedora-qa.2010-06-28-14.59.html

== Previous meeting follow-up ==
     1. adamw to forward wwoods a good explanation of the nss-softokn
        problem scenario to ensure autoqa catches it in future
              * See
                https://fedorahosted.org/pipermail/autoqa-devel/2010-June/000703.html
     2. wwoods to evaluate nss-softokn dependency problem for proper
        'depcheck' coverage
              * wwoods will review for next week
     3. Viking-Ice will start 'how to debug systemd problems' guide and
        send to list for review
              * Inprogress, see
                https://fedoraproject.org/wiki/User:Johannbg/QA/Systemd
     4. robatino to ask infrastructure team to archive previous RCs/TCs
              * Filed, see
                http://fedorahosted.org/fedora-infrastructure/ticket/2241
              * Waiting for response, may need to raise topic on mailing
                list
     5. jlaska to review F14 test day wiki content
              * Completed, see
                https://fedoraproject.org/wiki/QA/Fedora_14_test_days
              * Draft test day ideas at
                https://fedoraproject.org/wiki/Talk:QA/Fedora_14_test_days
     6. jlaska to create a ticket about possible enhancement/new test
        case for ABI stability check
              * Available for anyone to take ownership (see
                http://fedorahosted.org/autoqa/ticket/190)
     7. jlaska to cleanup (or remove) the Critical Path
        Packages#Background section so that it provides _some_ value
              * No cleanup done yet, will complete for next meeting

== F14 QA Recommendations ==

Owner - jlaska
Summary
      * Jlaska organized [[Fedora_13_QA_Retrospective]] feedback into a
        list of [[Fedora_13_QA_Retrospective#Recommendations|QA
        recommendations for Fedora 14]].  
      * Jlaska filed tickets for improvements, see
        https://fedorahosted.org/fedora-qa/milestone/Fedora%2014

Next steps...
      * If you are looking for a way to get involved in Fedora QA ...
        grab a ticket at
        https://fedorahosted.org/fedora-qa/milestone/Fedora%2014
      * Don't see something you'd like to work on ... file a ticket at
        https://fedorahosted.org/fedora-qa/newticket
 
== Proventester Update ==

Owner - maxamillion, adamw
Summary
      * Adam Miller announced that the proventesters wiki page
        (https://fedoraproject.org/wiki/QA/JoinProvenTesters) is no
        longer a draft.  
      * There are several TRAC requests to join the ''proventesters''
        group -- http://bit.ly/c0s7kD
      * adamw and dafrito completed the proventester instructions --
        https://fedoraproject.org/wiki/Proven_tester

Next steps
      * jdulaney to propose combining wiki pages 
      * Waiting on feedback from lmacken on the status of
        https://fedorahosted.org/bodhi/ticket/424 and re-enabling
        ''proventester'' karma for critpath packages

== AutoQA ==

=== Automate Package Update Acceptance Test Plan ===

Owner - wwoods
Summary
      * The immediate goal is to automate the
        [[QA:Package_Update_Acceptance_Test_Plan]]
      * The team met and discussed task priorities and agreed to
        prioritize tasks --
        https://fedorahosted.org/pipermail/autoqa-devel/2010-June/000668.html

Next steps...
      * Limit access to test systems qa01.c.fp.org through qa06.c.fp.org
        -- https://fedorahosted.org/fedora-infrastructure/ticket/2242 
      * Create a helloworld test for use with testing hook --
        https://fedorahosted.org/fedora-infrastructure/ticket/195
      * Standardization of hook argument names will be discussed soon
      * Complete depcheck test

=== Resultdb ===

Owner - jskladan
Summary
      * https://fedorahosted.org/fedora-infrastructure/ticket/145
      * Test instance up'n'running on one of our machines
      * Rewrote initscripts & rpmlint tests (see jskladan branch in
        autoqa git) so they store the result data inside.

Next steps...
      * Finish updating other tests to store results in resultdb
      * Setup autotest-server instance to use these tests
      * Once results are posted into resultsdb ... start working on a
        front-end

=== Labels + Virt ===

Owner - kparal
Summary
      * Implement *quick* virtualization support to allow for
        destructive tests --
        https://fedorahosted.org/fedora-infrastructure/ticket/181
      * Kparal created a ''labels'' git branch to track development (see
        https://fedorahosted.org/pipermail/autoqa-devel/2010-June/000742.html)

Next steps...
      * Determine format of labels to use (see
        https://fedorahosted.org/pipermail/autoqa-devel/2010-June/000740.html)
      * Complete script to help manage virtual guests that will be used
        by the labels

= Open discussion - <Your topic here> =

== colleges to help testing ==

Owner - j_dulaney
Summary
      * Proposal: get various small technical and community colleges to
        help with testing
Next steps ...
      * dulaney will ask if the instructor's interested, and point to
        the QA/Join page for ideas -
        https://fedoraproject.org/wiki/QA/Join
      * Adamw offered QA help if there are any questions or interest

== Knowledge base ==

Owner - jkeating
Summary
      * Jkeating asked the group if a Fedora Knowledge Base would be
        useful to your efforts?
      * The team discussed the idea of a knowledge base, but there
        wasn't anything tangible to offer feedback on
Next steps ...
      * Refine the idea/proposal

= Upcoming QA events =

      * 2010-07-08 - Pre-Alpha Rawhide Acceptance Test Plan #1
      * 2010-07-15 - Pre-Alpha Rawhide Acceptance Test Plan #2
      * 2010-07-22 - Pre-Alpha Rawhide Acceptance Test Plan #3
      * 2010-07-23 - Alpha Blocker Meeting (f14alpha) #1
      * 2010-07-30 - Alpha Blocker Meeting (f14alpha) #2

= Action items =

     1. jlaska to cleanup (or remove) the Critical Path
        Packages#Background section so that it provides _some_ value
     2. j_dulaney to draft a combined proventesters / joinproventesters
        wiki page for list review
     3. wwoods to evaluate nss-softokn dependency problem for proper
        'depcheck' coverage

Attachment: signature.asc
Description: This is a digitally signed message part

-- 
test mailing list
test@xxxxxxxxxxxxxxxxxxxxxxx
To unsubscribe: 
https://admin.fedoraproject.org/mailman/listinfo/test

[Index of Archives]     [Fedora Desktop]     [Fedora SELinux]     [Photo Sharing]     [Yosemite Forum]     [KDE Users]

  Powered by Linux