2010-04-19 - Fedora QA meeting recap

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

 



Greetings folks!  

See below for minutes from today's QA meeting.  As always, details are
available on the wiki at
https://fedoraproject.org/wiki/QA/Meetings/20100419

= Attendees =

People present (lines said):

      * jlaska (174)
      * kparal (39)
      * maxamillion (28)
      * adamw (23)
      * jskladan (19)
      * wwoods (16)
      * fenris02 (8)
      * zodbot (4)
      * Oxf13 (3)
      * _lmr_ (2)

Regrets:
      * [[User:liam]]
      * [[User:rhe]]

= Agenda =
      * Proposed meeting agenda -
        http://lists.fedoraproject.org/pipermail/test/2010-April/090226.html 
      * MeetBot summary -
        http://meetbot.fedoraproject.org/fedora-meeting/2010-04-19/fedora-qa.2010-04-19-15.00.html

== Fedora 13 RC test status ==

Upcoming test milestones:
      * 2010-04-16 - Final Blocker Meeting (f13blocker) #1
        ([http://meetbot.fedoraproject.org/fedora-bugzappers/2010-04-16/f-13-blocker-bug-review.2010-04-16-15.12.html recap])
      * 2010-04-16 - Pre-RC Branched Acceptance Test Plan
      * 2010-04-23 - Final Blocker Meeting (f13blocker) #2
      * 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:
      * 2010-04-22 - [[Test_Day:2010-04-22_StorageFiltering]]
      * 2010-04-29 - [[Test_Day:2010-04-29_Preupgrade]]

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
        https://fedoraproject.org/wiki/Fedora_13_QA_Retrospective

Questions:
      * ''fenris02'' - asked how to update boot.fedoraproject.org
        configs to use F-13-Beta.  Jlaska noted that the configs
        appeared updated in
        ([http://git.fedorahosted.org/git/?p=fedora-infrastructure.git;a=blob;f=bfo/pxelinux.cfg/fedora_install.conf;h=26acb46afa285f999356c912305395294240b0dd;hb=HEAD infrastructure.git]), but promised to follow-up with ''fenris02' after the meeting

== Bodhi QA workflow status check-in ==

      * Adam Williamson 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.

== Proventesters check-in ==

      * Adam Miller asked whether a vote was needed to move things
        forward.  Adam Williamson offered sending a final draft mail to
        the list, noting the policy would go into effect if no serious
        objections surface.
      * After the final draft, jlaska asked what steps should follow.
        The group came up with:
              * Submit a ticket to create ''proventester'' FAS group
              * Email test@xxxxxxxx to invite people to apply to
                ''proventester'' group
              * Flesh out some test guidance for members of the
                ''proventester'' group (links to
                [[User:Kparal/Proposal:Package_update_acceptance_test_plan|QA:Package_update_acceptance_test_plan]] or [[:Category:Test_Cases]]).

== Package Acceptance Test Plan check-in ==

      * Kamil Paral discussed the current state of the
        [[https://fedoraproject.org/wiki/User:Kparal/Proposal:Package_update_acceptance_test_plan|QA:Package_update_acceptance_test_plan]].  Kamil noted that we can have the test plan completed before F-13 is released, but work to automate the test plan won't be completed and will be tracked separately as a combination of AutoQA milestones ([https://fedorahosted.org/autoqa/milestone/Package%20Sanity%20Tests Package Sanity Test], [https://fedorahosted.org/autoqa/milestone/Resultdb Resultsdb], [https://fedorahosted.org/autoqa/milestone/autoqa%20depcheck depcheck]).  
      * Kamil plans to send a final draft to the test@xxxxxxxx list for
        review.  AdamW pointed out he was pretty please with the state
        of the test plan.

== AutoQA check-in ==

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
        [https://fedorahosted.org/mailman/listinfo/autoqa-devel
        autoqa-devel@xxxxxxxxxxxxxxxxxxxxxx]
     2. The beakerlib-based initscript test is now in production (see
        [https://fedorahosted.org/pipermail/autoqa-results/2010-April/016011.html 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
        [https://fedorahosted.org/autoqa/milestone/Package%20Sanity%
        20Tests autoqa PST milestone]).
     2. Package Sanity ensures clean install, removal, upgrade, etc of
        the packages (see
        [http://git.fedorahosted.org/git/?p=autoqa.git;a=blob;f=tests/package_sanity/examples/cheese-rpm-summary.txt;h=830a0a9311eb4e8442fd3858c0ad67ce694ad6c9;hb=refs/heads/pst 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
        http://fedoraproject.org/wiki/QA:Test_Plan_Metadata_Test_Page),
        this will be used by the resultsdb 

== Open discussion - <Your topic here> ==

      * No topics discussion

= Action items =

     1. jlaska + fenris02 to review whether F-13-Beta is an option for
        boot.fedoraproject.org
     2. kparal will bother other QA members if they have some comments
        to the test plan :)
     3. maxamillion - send Proventester draft to test@xxxxxxxx for final
        review
     4. maxamillion - Request new proventester FAS group

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