(fwn 209 beat) |
(fwn 210 beat) |
||
| Line 16: | Line 16: | ||
=== Weekly meetings === | === Weekly meetings === | ||
The QA group weekly meeting<ref>http://fedoraproject.org/wiki/QA/Meetings</ref> was held on 2010-01- | The QA group weekly meeting<ref>http://fedoraproject.org/wiki/QA/Meetings</ref> was held on 2010-01-18. The full logs are available<ref>http://fedoraproject.org/wiki/QA/Meetings/20100118</ref>. [[User:Jlaska|James Laska]] noted that [[User:maxamillion|Adam Miller]] was not present to update on the Xfce test day planning. [[User:Johannbg|Jóhann Guðmundsson]] reported that he had created a ticket for the LXDE test day<ref>http://fedorahosted.org/fedora-qa/ticket/46</ref>. | ||
[[User: | [[User:Adamwill|Adam Williamson]] reported on his and [[User:Rhe|Rui He's]] progres with documenting installation testing as a QA group activity. They had created a draft page<ref>http://fedoraproject.org/wiki/QA/Installation_Test</ref>, and planned to have a short paragraph in the QA Joining page<ref>http://fedoraproject.org/wiki/QA/Join</ref> which would refer to it. | ||
[[User: | [[User:Cwickert|Christoph Wickert]] reported that an LXDE mailing list had been created by the infrastructure team<ref>http://admin.fedoraproject.org/mailman/listinfo/lxde</ref>. | ||
[[User:Adamwill|Adam Williamson]] reported on the privilege escalation policy topic. He and [[User:Wwoods|Will Woods]] had discussed the topic at the most recent FESco meeting<ref>http://meetbot.fedoraproject.org/fedora-meeting/2010-01-15/fesco.2010-01-15-17.00.log.html</ref>, which had resulted in FESco asking for the QA group to provide a draft policy for discussion at a future FESco meeting. Adam said that he planned to write an initial draft policy and submit it to the QA group for discussion, then take a refined draft to a future FESco meeting. | |||
[[User:Wwoods|Will Woods]] | [[User:Wwoods|Will Woods]] observed that the change to making Rawhide repository definitions part of a package which is not installed by default may have an impact on QA's Rawhide testing procedures, and Wiki documentation. [[User:Kevin|Kevin Fenzi]] said he was already planning to update the Rawhide wiki page<ref>http://fedoraproject.org/wiki/Releases/Rawhide</ref> to reflect the change. | ||
[[User:Kparal|Kamil Paral]] announced that he had started sending reports from automated rpmguard<ref>http://fedorahosted.org/autoqa/wiki/rpmguard</ref> tests to the autoqa-results list<ref>http://fedorahosted.org/mailman/listinfo/autoqa-results</ref>. Reports from rpmlint were also enabled, primarily for comparison. He had also started a discussion within the AutoQA project on the possibility of creating a server which would collate AutoQA test results and provide an API for accessing them. | |||
[[User:Wwoods|Will Woods]] reported that he had continued working with [[User:Lmacken|Luke Macken]] on the implementation of a post-bodhi-update trigger for AutoQA, and Luke would be adding the necessary API calls to the next Bodhi update. Will had been working on the logic of a dependency checking test, and was close to a solution. His current code is available in git<ref>http://git.fedorahosted.org/git/?p=autoqa.git;a=blob;f=tests/depcheck/depcheck</ref>. The test is designed to be run with a repository and set of new packages specified; it generates the set of changed dependencies in the new packages and then checks them for sanity and consistency. [[User:Jlaska|James Laska]] passed on the information that [[User:Liam|Liam Li]] had been working on a python script to automate a virtual installation from a DVD image, as a precursor to a full automated installation test. Kamil and Will suggested it could be committed into AutoQA git as a branch while Liam works on it. | |||
< | [[User:Jlaska|James Laska]] reported that he was working on revising the autotest-client package based on feedback in the review ticket<ref>http://bugzilla.redhat.com/bugzilla/show_bug.cgi?id=548522</ref>. He had also created a Wiki page<ref>https://fedoraproject.org/wiki/User:Jlaska/gwt</ref> to chart out the requirements for packaging Google web toolkit (gwt), a requirement for packaging autotest. | ||
[[User:Wwoods|Will Woods]] asked when the first drop of Fedora 13 install images was scheduled. [[User:Jlaska|James Laska]] replied that this was planned for Thursday 2010-01-21, and the Rawhide acceptance test plan was scheduled to be run. | |||
There was no BugZappers meeting during the week due to the absence of several members. | |||
<references/> | <references/> | ||
=== | === Improved freeze policy documentation === | ||
[[User: | [[User:poelstra|John Poelstra]] announced<ref>http://lists.fedoraproject.org/pipermail/test/2010-January/088027.html</ref> improved documentation of the Fedora freeze policy on the Wiki<ref>http://fedoraproject.org/wiki/Important_Release_Milestones</ref>, and requested feedback. None was forthcoming, clearly indicating that the pages admit of no possible improvement. | ||
[[User:Adamwill|Adam Williamson]] asked the group<ref>http://lists.fedoraproject.org/pipermail/test/2010-January/087886.html</ref> to make a special effort to test several new X.org and graphics-related candidate updates, due to the significant impact they could have if approved as stable updates. Many group members responded with valuable feedback, which helped the X developers promote the updates to stable status with confidence. | |||
<references/> | <references/> | ||
=== | === Localization testing update === | ||
[[User:Igor|Igor Pires Soares]] noted that [[User:Noriko|Noriko Mizumoto]] was away on vacation, and so provided an update on the localization testing project. He had updated the wiki page<ref>http://fedoraproject.org/wiki/QA:Fedora_13_l10n_Results_Template</ref> to include a list of instructions for testing various packages. | |||
<references/> | <references/> | ||
=== | === Privilege escalation policy === | ||
[[User: | [[User:Adamwill|Adam Williamson]] posted an initial draft<ref>http://lists.fedoraproject.org/pipermail/test/2010-January/088063.html</ref> for a proposed privilege escalation policy, as the group had been discussing for a while. The draft was based on [[TomCallaway|Tom 'spot' Callaway]]'s blog post on the topic<ref>http://spot.livejournal.com/312216.html</ref>. The draft provoked a lively discussion with criticisms and suggestions from many group members. Adam later provided a second draft<ref>http://lists.fedoraproject.org/pipermail/test/2010-January/088094.html</ref> which attempted to address some of the issues raised, and the revision process continued. | ||
<references/> | <references/> | ||
Revision as of 06:46, 25 January 2010
QualityAssurance
In this section, we cover the activities of the QA team[1], as the QA group and the Fedora project in general awaken from its holiday slumber!
Contributing Writer: Adam Williamson
Test Days
There was no Test Day last week, and no Test Day is currently planned for this week. If you would like to propose a main track Test Day for the Fedora 13 cycle, please contact the QA team via email or IRC, or file a ticket in QA Trac[1].
Weekly meetings
The QA group weekly meeting[1] was held on 2010-01-18. The full logs are available[2]. James Laska noted that Adam Miller was not present to update on the Xfce test day planning. Jóhann Guðmundsson reported that he had created a ticket for the LXDE test day[3].
Adam Williamson reported on his and Rui He's progres with documenting installation testing as a QA group activity. They had created a draft page[4], and planned to have a short paragraph in the QA Joining page[5] which would refer to it.
Christoph Wickert reported that an LXDE mailing list had been created by the infrastructure team[6].
Adam Williamson reported on the privilege escalation policy topic. He and Will Woods had discussed the topic at the most recent FESco meeting[7], which had resulted in FESco asking for the QA group to provide a draft policy for discussion at a future FESco meeting. Adam said that he planned to write an initial draft policy and submit it to the QA group for discussion, then take a refined draft to a future FESco meeting.
Will Woods observed that the change to making Rawhide repository definitions part of a package which is not installed by default may have an impact on QA's Rawhide testing procedures, and Wiki documentation. Kevin Fenzi said he was already planning to update the Rawhide wiki page[8] to reflect the change.
Kamil Paral announced that he had started sending reports from automated rpmguard[9] tests to the autoqa-results list[10]. Reports from rpmlint were also enabled, primarily for comparison. He had also started a discussion within the AutoQA project on the possibility of creating a server which would collate AutoQA test results and provide an API for accessing them.
Will Woods reported that he had continued working with Luke Macken on the implementation of a post-bodhi-update trigger for AutoQA, and Luke would be adding the necessary API calls to the next Bodhi update. Will had been working on the logic of a dependency checking test, and was close to a solution. His current code is available in git[11]. The test is designed to be run with a repository and set of new packages specified; it generates the set of changed dependencies in the new packages and then checks them for sanity and consistency. James Laska passed on the information that Liam Li had been working on a python script to automate a virtual installation from a DVD image, as a precursor to a full automated installation test. Kamil and Will suggested it could be committed into AutoQA git as a branch while Liam works on it.
James Laska reported that he was working on revising the autotest-client package based on feedback in the review ticket[12]. He had also created a Wiki page[13] to chart out the requirements for packaging Google web toolkit (gwt), a requirement for packaging autotest.
Will Woods asked when the first drop of Fedora 13 install images was scheduled. James Laska replied that this was planned for Thursday 2010-01-21, and the Rawhide acceptance test plan was scheduled to be run.
There was no BugZappers meeting during the week due to the absence of several members.
- ↑ http://fedoraproject.org/wiki/QA/Meetings
- ↑ http://fedoraproject.org/wiki/QA/Meetings/20100118
- ↑ http://fedorahosted.org/fedora-qa/ticket/46
- ↑ http://fedoraproject.org/wiki/QA/Installation_Test
- ↑ http://fedoraproject.org/wiki/QA/Join
- ↑ http://admin.fedoraproject.org/mailman/listinfo/lxde
- ↑ http://meetbot.fedoraproject.org/fedora-meeting/2010-01-15/fesco.2010-01-15-17.00.log.html
- ↑ http://fedoraproject.org/wiki/Releases/Rawhide
- ↑ http://fedorahosted.org/autoqa/wiki/rpmguard
- ↑ http://fedorahosted.org/mailman/listinfo/autoqa-results
- ↑ http://git.fedorahosted.org/git/?p=autoqa.git;a=blob;f=tests/depcheck/depcheck
- ↑ http://bugzilla.redhat.com/bugzilla/show_bug.cgi?id=548522
- ↑ https://fedoraproject.org/wiki/User:Jlaska/gwt
Improved freeze policy documentation
John Poelstra announced[1] improved documentation of the Fedora freeze policy on the Wiki[2], and requested feedback. None was forthcoming, clearly indicating that the pages admit of no possible improvement.
Adam Williamson asked the group[3] to make a special effort to test several new X.org and graphics-related candidate updates, due to the significant impact they could have if approved as stable updates. Many group members responded with valuable feedback, which helped the X developers promote the updates to stable status with confidence.
Localization testing update
Igor Pires Soares noted that Noriko Mizumoto was away on vacation, and so provided an update on the localization testing project. He had updated the wiki page[1] to include a list of instructions for testing various packages.
Privilege escalation policy
Adam Williamson posted an initial draft[1] for a proposed privilege escalation policy, as the group had been discussing for a while. The draft was based on Tom 'spot' Callaway's blog post on the topic[2]. The draft provoked a lively discussion with criticisms and suggestions from many group members. Adam later provided a second draft[3] which attempted to address some of the issues raised, and the revision process continued.