Search results

...lable<ref>http://fedoraproject.org/wiki/QA/Meetings/20100201</ref>. [[User:Jlaska|James Laska]] reported that [[User:Beland|Christopher Beland]] had added li ...e project would become important to several groups, if implemented. [[User:Jlaska|James Laska]] suggested a micro-FAD<ref>http://fedoraproject.org/wiki/FAD</

* James Laska (jlaska) * James Laska (jlaska)

.... [[User:Adamwill|Adam Williamson]] reported that he had added a suggested draft for the previously agreed change to the minimum hardware requirements to an [[User:Jlaska|James Laska]] reported on the Fedora 11 retrospective meeting which had tak

...land/Bugzilla_Legend - Adamw will edit and refine this UN-OFFICIAL WORKING DRAFT based on current information. Follow up on next weeks agenda. ...p://fedoraproject.org/wiki/User:Beland/Bugzilla_Legend&gt; - revising the draft list of priority / severity criteria.

...Fedora_16_Alpha_PowerPC_Release_Criteria|James Laskas PPC Release Criteria draft]]

* James Laska (jlaska) # [jlaska] - Send informal test day feedback survey to fedora-test-list and test day

...lable<ref>http://fedoraproject.org/wiki/QA/Meetings/20090624</ref>. [[User:Jlaska|James Laska]] reported that he had not yet been able to update the QA Goals [[User:Jlaska|James Laska]] reviewed the new schedule for Fedora 12 QA events which has b

* James Laska - jlaska (169) * James Laska (jlaska)

* James Laska (jlaska) * James Laska (jlaska)

...l/test/2010-June/091559.html</ref> with a much-improved revision of Adam's draft<ref>https://fedoraproject.org/wiki/User:Dafrito/Draft_proventesters_instruc [[User:Jlaska|James Laska]] announced<ref>http://lists.fedoraproject.org/pipermail/test/2

...Fedora_16_Alpha_PowerPC_Release_Criteria|James Laskas PPC Release Criteria draft]]

* James Laska (jlaska) * James Laska (jlaska)

...lable<ref>http://fedoraproject.org/wiki/QA/Meetings/20090824</ref>. [[User:Jlaska|James Laska]] led a post-Alpha release recap (on the assumption the Fedora ...ggested posting announcements to fedora-devel-announce instead, but [[User:Jlaska|James Laska]] said he had been asked to stop posting Test Day announcements

| style="color: #407a40" | [jlaska] - Announce event to fedora-{devel,test}-list@redhat.com | style="color: #407a40" | [jlaska] - Reach out to Red Hat and Fedora i18n teams

suggest a draft change. The procedure for this is documented here<ref>https://fedoraproject ...://lists.fedoraproject.org/pipermail/test/2011-July/101439.html</ref>. The draft matrix was reviewed at the weekly meeting of 2011-07-25<ref>http://fedorapr

[[User:Jlaska|James Laska]] said he had spoken to [[MatthiasClasen|Matthias Clasen]] abou ...was now thinking about how to improve rpmguard's reporting method. [[User:Jlaska|James Laska]] provided an update on the status of packaging the AutoQA comp

...lable<ref>http://fedoraproject.org/wiki/QA/Meetings/20090817</ref>. [[User:Jlaska|James Laska]] reported that a first release candidate for the Fedora 12 Alp ...omatically, with no manual intervention needed. He was planning to write a draft of a 'How to write a test' document. He had also made a blog post<ref>http:

...edoraproject.org/pipermail/test/2010-July/091984.html</ref> an alternative draft<ref>http://fedoraproject.org/wiki/User:Adamwill/Draft_proventesters</ref> w [[User:MCloaked|Mike Cloaked]] generally liked Aaron's draft<ref>http://lists.fedoraproject.org/pipermail/test/2010-July/091938.html</re

* [jlaska] - announce live image create wiki update to fedora-test-list * [jlaska] - schedule autoqa discussion w/ wwoods and jkeating - is there any work we

This is a first draft that keep all tests of original template to ease comparison of this specifi | {{result|fail|jlaska|XYZ|ZXY}}