Search results

# jlaska (65) ; Owner : [[User:jlaska|jlaska]]

# jlaska (67) ! style="background-color: #407a40" | jlaska

# adamw and jlaska to propose artwork final release criteria # jlaska to publish F-14-Alpha QA retrospective page

* jlaska (99) # maxamillion will work on second draft of provenpackagers proposal

# jlaska (97) ; Owner : [[User:jlaska|jlaska]]

* jlaska * jds2001 to draft message to fedora-devel-announce about upcoming rawhide rebase

* jlaska (91) * jlaska + fenris02 to review whether F-13-Beta is an option for boot.fedoraproject.

[[User:jlaska]] hs a conflict at our regular meeting time today (16:00 UTC). If * [adamw] - propose draft wording of minimal requirements for the release_notes team to digest

* jlaska (123) ...t_Day:2010-03-30_SSSDByDefault|SSSD by default Test Day]] -- [[User:jlaska|jlaska]]

* jlaska (116) ...eck-in with desktop team for guidance on s-c-* -- thank you j_dulaney!!! (jlaska, 15:04:33)

# jlaska (110) # jlaska will ask Hurry whether adding some amount of installer validation or instal

* [[User:Jlaska|jlaska]] - Having [[QA/SOP_Test_Day_management]] was invaluable and resulted in a * [[User:jlaska|jlaska]] - Care and feeding of the Test Day live image creation wiki ([[QA/Test_Da

* jlaska (98) # adamw noted that the [[Privilege_escalation_policy]] is no longer a draft and has been reviewed by FESCO

...lable<ref>http://fedoraproject.org/wiki/QA/Meetings/20100118</ref>. [[User:Jlaska|James Laska]] noted that [[User:maxamillion|Adam Miller]] was not present t ...ocumenting installation testing as a QA group activity. They had created a draft page<ref>http://fedoraproject.org/wiki/QA/Installation_Test</ref>, and plan

# jlaska (103) # jlaska to check-in with lmacken on the status of https://fedorahosted.org/bodhi/ti

* jlaska (141) * jlaska to reach out to beland for guidance/ideas on how to document the process (o

* jlaska (155) # jlaska will discuss CommonBugs entry for {{bz|552423}} with halfline

# jlaska (92) * jlaska to follow-up w/ maxamillion after meeting

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

# jlaska (106) # adamw and jlaska to propose artwork final release criteria

* jlaska (174) ...'' - 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/gi

...a wiki page created to track validation of the RCs for preview, I'll have jlaska or wwoods cook one of those up for us | style="color: #8c4a4a" | f13: #843 (Draft Fedora 11 Schedule) - Fedora Release Engineering - Trac - https://fedorahos

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

* jlaska (165) * At tflink's suggestion, jlaska migrated our remaining production F13 test clients to F14

...lable<ref>http://fedoraproject.org/wiki/QA/Meetings/20090701</ref>. [[User:Jlaska|James Laska]] reported that he had not yet been able to update the QA Goals ...ked in a ticket<ref>https://fedorahosted.org/autoqa/ticket/9</ref>. [[User:Jlaska|James Laska]] and [[User:jkeating|Jesse Keating]] are working on this toget

# jlaska (63) ; Owner - [[User:jlaska]]

* jlaska (184) # maxamillion to draft up some proposed policy docs for qa FAS group membership

* jlaska (100) # jlaska request zodbot tracking for updated F-13 QA RSS feeds (blocker bugs, common

* [[User:jlaska|jlaska]] (113) # jlaska to review F14 test day wiki content

* jlaska (154) # jlaska to post recommendations on F-12 QA retrospective

# [[User:Jlaska|jlaska]] - ''Pre-release acceptance'' - the Rawhide Acceptance milestones continue # [[User:Jlaska|jlaska]] - ''Alpha TC1'' - Missed the Alpha-TC1 milestone by 1 week, little to no

# jlaska (154) : jlaska will ping lmacken after meeting

* jlaska (133) # jlaska to cleanup (or remove) the Critical Path Packages#Background section so tha

* jlaska (114) * jlaska + adamw - clear out [https://bugzilla.redhat.com/buglist.cgi?cmdtype=runnam

# jlaska (152) ; Owner : [[User:jlaska|jlaska]]

# [[User:Jlaska|jlaska]] - ''Mailing list'' - Seeing an increased level of mailing list traffic di # [[User:Jlaska|jlaska]] - ''Beta'' - Because of the FESCO approval for the late arriving NM-0.9 c

* jlaska ! style="background-color: #42427e" | jlaska

* jlaska (97) Jlaska asked the team to think about a method for dividing up remaining '''22''' c

* jlaska (46) * [[User:jlaska]]

* jlaska (98) # adamw and jlaska to propose artwork final release criteria

* jlaska (115) * jlaska to send request for retrospective feedback to fedora-test-list@

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

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

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

* jlaska (163) # jlaska to add bugzilla shared query links to Common_Bugs wiki page

* James Laska (jlaska) # [jlaska+adamw] mediawiki semantic update (packaging and hosting)

...ing for FUDCon Pune, India and FAmSCo updates. In Quality Assurance news, draft standard operating procedures for QA meetings, validation testing updates a suggest a draft change. The procedure for this is documented here<ref>https://fedoraproject

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

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

...said he was planning to work in all the received feedback, send a revised draft of the page to the mailing list for comment, and do the final touches in a [[User:Jlaska|James Laska]] gave an update on the Fedora 12 QA retrospective. He thanked

...kground: #407a40"> f13</th><td class="text" style="color: #407a40">what of jlaska's stuff are we going to use for alpha?</td><td class="time">13:31</td></tr> ..."background: #854685"> wwoods</th><td class="text" style="color: #854685">(draft)</td><td class="time">13:32</td></tr>

|align="left" | 9:30am ||align="center" | Proposal - Draft proposal on Wiki to shop around to larger audiences * [[User:jlaska|James Laska]]

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

* '''jlaska''' - drop loop back install source cases * '''jlaska''' - drop ia64 and s390x

...nd something missing, incorrect, or in need of revision, you can suggest a draft change. The procedure for this is documented here:<ref>http://fedoraproject [[User:Jlaska|James Laska]] announced<ref>http://lists.fedoraproject.org/pipermail/devel-

* jlaska ! style="background-color: #8c4a4a" | jlaska

* jlaska (174) * James Laska (jlaska)

* jlaska (140) * jlaska will propose Common_F12_Bugs after meeting for bug#530541

==== New Fedora Project Contributor Agreement Draft ==== ...ibutor License Agreement. He asked project members to give feedback on the draft.

...would be helpful in at least some cases, and Ankur said he would work on a draft of such a page<ref>http://lists.fedoraproject.org/pipermail/test/2010-July/ [[User:Jlaska|James Laska]] reported<ref>http://lists.fedoraproject.org/pipermail/test/20

...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

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

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

...eting<ref>http://fedoraproject.org/wiki/QA/Meetings/20100315</ref>, [[User:Jlaska|James Laska]] noted that release engineering should be working on the first ...defined. [[User:maxamillion|Adam Miller]] had already provided an initial draft policy<ref>http://lists.fedoraproject.org/pipermail/test/2010-March/088980.

...lable<ref>http://fedoraproject.org/wiki/QA/Meetings/20100208</ref>. [[User:Jlaska|James Laska]] and [[User:Kevin|Kevin Fenzi]] arranged to update the list of [[User:Jlaska|James Laska]] reported that [[User:Wwoods|Will Woods]] and [[User:Kparal|Ka

...king people to help with the process of writing Debugging pages<ref>http://jlaska.livejournal.com/5693.html</ref>. [[User:Adamwill|Adam Williamson]] mentione [[User:Jlaska|James Laska]] had created a meeting time matrix<ref>http://fedoraproject.or

* poelcat to draft EOL Fedora 8 ticket for Red Hat Engineering Operations | style="color: #42427e" | ping tk009 jds2001 jlaska John5342 quantumburnz all bug Triagers

[[User:Jlaska|James Laska]] noted that there were several reports indicating the new hard ...</ref>, but there has been no progress in the code since next week. [[User:Jlaska|James Laska]] suggested setting a goal of finishing the previously agreed-u

...s<ref>http://fedorahosted.org/fedora-qa/ticket/173#comment:7</ref>. [[User:Jlaska|James Laska]] followed up with some questions and comments<ref>http://fedor === Draft btrfs test case ===

...08-30<ref>http://fedoraproject.org/wiki/QA/Meetings/20100830</ref>, [[User:Jlaska|James Laska]] asked what to do about an email from a proven tester asking t === Fedora 14 Release Notes Draft Available ===

...autoqa is now run automatically when a new Rawhide tree is created. [[User:Jlaska|James Laska]] mentioned that autoqa results are currently being sent to a m [[User:Jlaska|James Laska]] said he had checked in with [[User:Wtogami| Warren Togami]] a

[[User:Jlaska|James Laska]] reported that he was still not yet ready to send out a Test D ...RC2_Install_Test_Results</ref> between release candidate revisions. [[User:Jlaska|James Laska]] committed to work out his best solution and send it to the ma

...lable<ref>http://fedoraproject.org/wiki/QA/Meetings/20100104</ref>. [[User:Jlaska|James Laska]] reported that had finished his list of recommendations based [[User:Jlaska|James Laska]] reported that he, [[User:Adamwill|Adam Williamson]], [[User:L

suggest a draft change. The procedure for this is documented here: ...5. The event went successfully and exposed some bugs in the system. [[User:Jlaska|James Laska]] provided a wrap-up of the event<ref>http://lists.fedoraprojec

# Draft announcement emails # jlaska will propose an updated [[Releases/Rawhide]] page

suggest a draft change. The procedure for this is documented here: ...5. The event went successfully and exposed some bugs in the system. [[User:Jlaska|James Laska]] provided a wrap-up of the event<ref>http://lists.fedoraprojec

...f>http://www.happyassassin.net/extras/fedora-qa-20090318.log</ref>. [[User:Jlaska|James Laska]] reported good progress in his work on the Semantic test resul ...ave been made in FAS, and this was agreed. Christopher said he will send a draft of the new 'How to Triage' page to the mailing list for discussion in the c

[[User:Jlaska|James Laska]] called out<ref>http://jlaska.livejournal.com/5693.html</ref> for anyone interested in joining the Fedora ...lable<ref>http://fedoraproject.org/wiki/QA/Meetings/20090715</ref>. [[User:Jlaska|James Laska]] reported that he had filed tickets to track the creation of t

[[User:Jlaska|James Laska]] noted that the first Alpha release candidate was now availabl ...mportant. [[User:maxamillion|Adam Miller]] volunteered to write an initial draft of a policy / procedure on group membership.

[[User:Jlaska|James Laska]] reported that he had not yet been able to talk to [[User:Liam ...d built the new version of autotest for the AutoQA project to test. [[User:Jlaska|James Laska]] and [[User:Wwoods|Will Woods]] were in progress on testing it

...er activities, Fedora 13 Alpha and Beta updates, and details on a proposed draft of a package update policy. Translation reports details on last week's Tra No QA group weekly meeting was held on 2010-03-08 as [[User:Jlaska|James Laska]] was unavailable and there were no pressing items needing disc

...ramsey Prepared the community for 2nd July Bi-weekly meeting on 2nd July, draft agenda was proposed and published. [[User:Jlaska|James Laska]] proposed several changes to the release criteria<ref>http://l

[[User:Adamwill|Adam Williamson]] summarized upcoming events, and [[User:Jlaska|James Laska]] pointed out the relevant calendar page<ref>http://poelstra.fe [[User:Jlaska|James Laska]] started a discussion regarding plans for the then-upcoming An

...f>http://www.happyassassin.net/extras/fedora-qa-20090506.log</ref>. [[User:Jlaska|James Laska]] reported solid progress in transferring future tasks for the [[User:Jlaska|James Laska]] reported that he had not had time to work with David Zeuthen

...when adding one..." [[User:Jlaska|James Laska]] also suggested<ref>http://jlaska.livejournal.com/5561.html</ref> that there are still some high priority def ...et sent out a Test Day feedback survey to previous participants, but had a draft ready and would continue to work on it.

...[[User:bskeggs|Ben Skeggs]], and [[User:Adamwill|Adam Williamson]], [[User:Jlaska|James Laska]] and [[User:Wwoods|Will Woods]] were present for the QA team. [[User:Jlaska|James Laska]] reported that packaging work on the Semantic extension for Me

...mundsson]] suggested an email to the fedora-test-list mailing list. [[User:Jlaska|James Laska]] wanted to get in touch with the maintainers who had been invo The group then discussed the Fedora 11 release situation. [[User:Jlaska|James Laska]] explained that [[User:jkeating|Jesse Keating]] had already le

...p://lists.fedoraproject.org/pipermail/test/2010-June/091746.html</ref> his draft<ref>http://fedoraproject.org/wiki/User:Jdulaney/Proven_Tester</ref>. [[User ...pers/BugStatusWorkFlow#VERIFIED</ref> regarding the VERIFIED state. [[User:Jlaska|James Laska]] reviewed and approved his changes, which were also discussed

...cussion during the meeting. After the meeting arxs volunteered to create a draft of a revised components list based on information from [[Critical_Path_Pack * Action Item - arxs will create a draft of a revised components list and update on progress next week.

...010-08-27/f-14-beta-blocker-review.2010-08-27-16.00.html</ref>, and [[User:Jlaska|James Laska]] posted a recap<ref>http://lists.fedoraproject.org/pipermail/t ...:Writing_autoqa_tests</ref>. Josef, [[User:Kparal|Kamil Paral]] and [[User:Jlaska|James Laska]] continued to revise and refine the page over the next few day

...candidate build failed to install correctly to an Intel X25-M SSD. [[User:Jlaska|James Laska]] suggested<ref>http://lists.fedoraproject.org/pipermail/test/2 ...sts.fedoraproject.org/pipermail/test/2010-March/089764.html</ref> a second draft of the proventesters SOP proposal, and [[User:Adamwill|Adam Williamson]] po

...if there were no major objections. Adam Miller subsequently sent the final draft to the list<ref>http://lists.fedoraproject.org/pipermail/test/2010-April/09 ...g/pipermail/test/2010-April/090287.html</ref> on the plan, to which [[User:Jlaska|James Laska]]<ref>http://lists.fedoraproject.org/pipermail/test/2010-April/

...bracing discussion on how to send an apparently empty line to IRC, [[User:Jlaska|James Laska]] reported little progress in his work on making the Semantic t .../wiki/User:Tk009/bugzappers</ref> and [[User:Beland|Christopher Beland's]] draft<ref>http://fedoraproject.org/wiki/User:Beland/BugZappers</ref>, with refere

* jlaska (2) suggest a draft change. The procedure for this is documented here:

[[User:Jlaska|James Laska]] put into production<ref>http://lists.fedoraproject.org/piperm .../pipermail/test/2011-July/101180.html</ref>, and requested feedback on the draft.

suggest a draft change. The procedure for this is documented here: ...ists.fedoraproject.org/pipermail/test/2011-March/097863.html</ref>. [[User:Jlaska|James Laska]] recommended caution to avoid tying the criterion too closely

...nd something missing, incorrect, or in need of revision, you can suggest a draft change. The procedure for this is documented here [[User:Jlaska|James Laska]] requested testing of an installer image which included update

...ation<ref>http://cgit.freedesktop.org/packagekit/plain/docs/app-install-v1.draft</ref> that is distribution-agnostic and should allow relevant metadata (inc [[User:Jlaska|James Laska]] reported on the progress of the project to make the Semantic

...lists.fedoraproject.org/pipermail/test/2010-July/092266.html</ref> a rough draft<ref>http://fedoraproject.org/wiki/User:Ankursinha/Reporting_Bugs</ref>. Jon [[User:Jlaska|James Laska]] reported<ref>http://lists.fedoraproject.org/pipermail/test/20

...ated to critical path functionality. Following useful feedback from [[User:Jlaska|James Laska]]<ref>http://lists.fedoraproject.org/pipermail/test/2010-Decemb

...t and Makefile.in files."[[ TillMaas|TillMaas]] added[19] a link to a wiki draft on the subject and suggested that "[...] one should run autoreconf locally The IRC logs[1] from the meeting on 10/24/2008 were posted by [[:User:Jlaska|James Laska]]. The team has outlined their test plans[2], and discussed wh

...doraproject.org/pipermail/ambassadors/2011-February/017081.html </ref> the draft Agenda <ref> https://fedoraproject.org/wiki/Meeting:APAC_Ambassadors_2011-0 ...he way the event had turned out. [[User:Adamwill|Adam Williamson]], [[User:Jlaska|James Laska]] and [[User:Johannbg|Jóhann Guðmundsson]] joined in with sug