From Fedora Project Wiki

< QA‎ | Meetings

m (Small change)
m (internal link cleaning)
 
(8 intermediate revisions by one other user not shown)
Line 2: Line 2:


People present (lines said):
People present (lines said):
* jlaska (91)
* kparal (37)
* jeff_hann (9)
* damNageHack (8)
* zodbot (4)
* jskladan (3)
* lmacken (3)
* Viking-Ice (1)


Regrets:
Regrets:
* [[User:liam]]
* [[User:wwoods|wwoods]]
* [[User:rhe]]
* [[User:adamwill|adamwill]]
* [[User:liam|liam]]
* [[User:rhe|rhe]]


= Agenda =
= Agenda =
* [FIXME Proposed meeting agenda]
* [http://lists.fedoraproject.org/pipermail/test/2010-April/090413.html Proposed meeting agenda]
* [FIXME MeetBot summary]
* [http://meetbot.fedoraproject.org/fedora-meeting/2010-04-26/fedora-qa.2010-04-26-15.00.html MeetBot summary]


== Previous meeting follow-up ==
== Previous meeting follow-up ==
Line 15: Line 26:
* jlaska + fenris02 to review whether F-13-Beta is an option for boot.fedoraproject.org
* jlaska + fenris02 to review whether F-13-Beta is an option for boot.fedoraproject.org
** Already completed by the infrastructure team, yay infrastructure!
** Already completed by the infrastructure team, yay infrastructure!
* adamw + jlaska - Bodhi QA workflow status check-in
** lmacken organizing existing tickets into Bodhi-2.0 TRAC roadmap (see https://fedorahosted.org/bodhi/milestone/2.0).  Expects to complete in next few weeks.


See agenda below for additional follow-up items included in specific topics
See agenda below for additional follow-up items included in specific topics
Line 31: Line 45:
Upcoming test days:
Upcoming test days:
* 2010-04-29 - [[Test_Day:2010-04-29_Preupgrade]]
* 2010-04-29 - [[Test_Day:2010-04-29_Preupgrade]]
Recent test changes:
* Adding i18n support to installation test plan (see details [https://fedorahosted.org/fedora-qa/ticket/63 ticket#63])


{{admon/important|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 [[Fedora_13_QA_Retrospective]].}}
{{admon/important|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 [[Fedora_13_QA_Retrospective]].}}
== Bodhi QA workflow status check-in ==
https://fedorahosted.org/bodhi/milestone/2.0


== Proventesters check-in ==
== Proventesters check-in ==


* maxamillion - send Proventester draft to test@l.fp.org for final review
* maxamillion - send Proventester draft to test@l.fp.org for final review (see http://lists.fedoraproject.org/pipermail/test/2010-April/090252.html)
** Sent for final review at http://lists.fedoraproject.org/pipermail/test/2010-April/090252.html
* maxamillion - Request new proventester FAS group (see https://fedorahosted.org/fedora-infrastructure/ticket/2114)
 
* The team discussed possible next steps, including ...
* maxamillion - Request new proventester FAS group
** Recommending that current members of the 'qa' group ... apply to 'proventesters'
** Requested and created (thanks lmacken) -- https://fedorahosted.org/fedora-infrastructure/ticket/2114
** Document exact criteria needed for proventesters
** https://admin.fedoraproject.org/accounts/group/view/proventesters
** Provide a TRAC ticket template for mentor requests (for sample, see similar https://fedorahosted.org/fedora-infrastructure/newtplticket)


== Package Acceptance Test Plan check-in ==
== Package Acceptance Test Plan check-in ==


* kparal will bother other QA members if they have some comments to the test plan :)
* Kparal sent request for final review at http://lists.fedoraproject.org/pipermail/test/2010-April/090287.html
** Sent for final review at http://lists.fedoraproject.org/pipermail/test/2010-April/090287.html
* If no additional feedback, test plan will be finalized this week
* Next steps ...
** Remove ''draft'' status
** Document each test case (see [https://fedorahosted.org/fedora-qa/ticket/62 ticket#62])


== AutoQA check-in ==
== AutoQA check-in ==


There has been a lot of AutoQA activities in recent weeks, Jlaska asked the group to walk through some highlights.
There has been a lot of AutoQA activities in recent weeks, jlaska asked the group to walk through some highlights.


Josef Skladanka updated the group on several AutoQA activities:
* Kparal provided some updates from jskladan on the results database efforts..
# 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@lists.fedorahosted.org]
** First draft of implementing the resultsdb API
# The beakerlib-based initscript test is now in production (see [https://fedorahosted.org/pipermail/autoqa-results/2010-April/016011.html sample results])
** Test suite for resultsdb API created
# Making progress on the resultsDB - We have finished the db schema (see [[AutoQA_resultsdb_schema]]) and accepted a input API (see [[AutoQA_resultsdb_API]])
# 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:
# 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]).
# 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.
# 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:
# We have enough info about current bodhi to write a bodhi update watcher, but it may have some shortcomings and will soon be obsoleted
# We have a proposed storage encoding for putting test plan metadata in the wiki (see [[QA:Test_Plan_Metadata_Test_Page]]), this will be used by the resultsdb  


== Open discussion - <Your topic here> ==
== Open discussion - <Your topic here> ==
Line 119: Line 120:


= Action items =
= Action items =
# current members of the 'qa' group ... apply to 'proventesters'
# jlaska to follow-up w/ maxamillion after meeting


= IRC Transcript =
= IRC Transcript =
{|
|- id="t15:00:08"
! style="background-color: #407a40" | jlaska
| style="color: #407a40" | #startmeeting Fedora QA Meeting
|| [[#t15:00:08|15:00]]
|- id="t15:00:09"
! style="background-color: #42427e" | zodbot
| style="color: #42427e" | Meeting started Mon Apr 26 15:00:08 2010 UTC.  The chair is jlaska. Information about MeetBot at http://wiki.debian.org/MeetBot.
|| [[#t15:00:09|15:00]]
|- id="t15:00:10"
! style="background-color: #42427e" | zodbot
| style="color: #42427e" | Useful Commands: #action #agreed #halp #info #idea #link #topic.
|| [[#t15:00:10|15:00]]
|- id="t15:00:12"
! style="background-color: #407a40" | jlaska
| style="color: #407a40" | #meetingname fedora-qa
|| [[#t15:00:12|15:00]]
|- id="t15:00:13"
! style="background-color: #42427e" | zodbot
| style="color: #42427e" | The meeting name has been set to 'fedora-qa'
|| [[#t15:00:13|15:00]]
|- id="t15:00:22"
! style="background-color: #407a40" | jlaska
| style="color: #407a40" | #topic Gathering critical mass ...
|| [[#t15:00:22|15:00]]
|- id="t15:00:31"
| colspan="2" | * jeff_hann is here
|| [[#t15:00:31|15:00]]
|- id="t15:00:35"
| colspan="2" | * kparal jumps straight into meeting
|| [[#t15:00:35|15:00]]
|- id="t15:00:44"
! style="background-color: #407a40" | jlaska
| style="color: #407a40" | jeff_hann: kparal: howdy
|| [[#t15:00:44|15:00]]
|- id="t15:00:57"
! style="background-color: #818144" | jeff_hann
| style="color: #818144" | howdee
|| [[#t15:00:57|15:00]]
|- id="t15:00:59"
| colspan="2" | * jskladan watching from the shadows
|| [[#t15:00:59|15:00]]
|- id="t15:01:38"
| colspan="2" | * jlaska tips hat towards jskladan
|| [[#t15:01:38|15:01]]
|- id="t15:02:23"
! style="background-color: #854685" | damNageHack
| style="color: #854685" | hi
|| [[#t15:02:23|15:02]]
|- id="t15:02:27"
! style="background-color: #407a40" | jlaska
| style="color: #407a40" | damNageHack: hello :)
|| [[#t15:02:27|15:02]]
|- id="t15:02:34"
! style="background-color: #407a40" | jlaska
| style="color: #407a40" | wwoods: adamw: you guys around?
|| [[#t15:02:34|15:02]]
|- id="t15:03:22"
! style="background-color: #407a40" | jlaska
| style="color: #407a40" | I don't think this time slot works great for maxamillion, but lemme check ...
|| [[#t15:03:22|15:03]]
|- id="t15:04:29"
! style="background-color: #407a40" | jlaska
| style="color: #407a40" | I've got a conflict @ the half hour increment ... so let's get started
|| [[#t15:04:29|15:04]]
|- id="t15:04:59"
! style="background-color: #407a40" | jlaska
| style="color: #407a40" | if we run over, I may need help closing out the proposed agenda items
|| [[#t15:04:59|15:04]]
|- id="t15:05:08"
! style="background-color: #407a40" | jlaska
| style="color: #407a40" | Proposed agenda - http://lists.fedoraproject.org/pipermail/test/2010-April/090413.html
|| [[#t15:05:08|15:05]]
|- id="t15:05:13"
! style="background-color: #407a40" | jlaska
| style="color: #407a40" | #topic Previous meeting follow-up
|| [[#t15:05:13|15:05]]
|- id="t15:05:39"
! style="background-color: #407a40" | jlaska
| style="color: #407a40" | #info jlaska + fenris02 to review whether F-13-Beta is an option for boot.fedoraproject.org
|| [[#t15:05:39|15:05]]
|- id="t15:05:56"
! style="background-color: #407a40" | jlaska
| style="color: #407a40" | This was easy, thanks to the infrastructure team ... boot.fp.org should already have links to Fedora 13 beta
|| [[#t15:05:56|15:05]]
|- id="t15:06:07"
! style="background-color: #407a40" | jlaska
| style="color: #407a40" | #info Completed by the infrastructure team, yay infrastructure!
|| [[#t15:06:07|15:06]]
|- id="t15:06:16"
! style="background-color: #407a40" | jlaska
| style="color: #407a40" | #info adamw + jlaska - Bodhi QA workflow status check-in
|| [[#t15:06:16|15:06]]
|- id="t15:06:18"
! style="background-color: #488888" | kparal
| style="color: #488888" | jlaska: is it necessary to re-download the images?
|| [[#t15:06:18|15:06]]
|- id="t15:07:02"
! style="background-color: #407a40" | jlaska
| style="color: #407a40" | kparal: good question ... I tested by downloading the images
|| [[#t15:07:02|15:07]]
|- id="t15:07:20"
! style="background-color: #407a40" | jlaska
| style="color: #407a40" | so I don't know if the configs are pulled from the server, or are on the media
|| [[#t15:07:20|15:07]]
|- id="t15:08:14"
! style="background-color: #488888" | kparal
| style="color: #488888" | ok
|| [[#t15:08:14|15:08]]
|- id="t15:08:21"
| colspan="2" | * kparal will test some day
|| [[#t15:08:21|15:08]]
|- id="t15:08:31"
! style="background-color: #407a40" | jlaska
| style="color: #407a40" | kparal: that'll likely need a follow-up to #fedora-admin for guidance, I'm not sure
|| [[#t15:08:31|15:08]]
|- id="t15:09:05"
! style="background-color: #407a40" | jlaska
| style="color: #407a40" | adamw and I spoke w/ lmacken last week, he is working to organize a lot of TRAC tickets into a bodhi-2.0 milestone
|| [[#t15:09:05|15:09]]
|- id="t15:09:20"
! style="background-color: #407a40" | jlaska
| style="color: #407a40" | and expected to have that finished out in the next few weeks
|| [[#t15:09:20|15:09]]
|- id="t15:09:24"
! style="background-color: #407a40" | jlaska
| style="color: #407a40" | bodhi-2.0 milestone - https://fedorahosted.org/bodhi/milestone/2.0
|| [[#t15:09:24|15:09]]
|- id="t15:09:51"
! style="background-color: #407a40" | jlaska
| style="color: #407a40" | Some initial requirements gathering will also take place in the coming weeks
|| [[#t15:09:51|15:09]]
|- id="t15:10:33"
! style="background-color: #407a40" | jlaska
| style="color: #407a40" | my understanding is this will be helpful for us so we can coordinate AutoQA dependencies and document/educate 'proventesters' on the QA workflow through bodhi
|| [[#t15:10:33|15:10]]
|- id="t15:10:52"
! style="background-color: #407a40" | jlaska
| style="color: #407a40" | we had several other follow-up items, but I've moved those into specific topics below ...
|| [[#t15:10:52|15:10]]
|- id="t15:11:00"
! style="background-color: #407a40" | jlaska
| style="color: #407a40" | so I'll dive in, unless anyone has other thoughts
|| [[#t15:11:00|15:11]]
|- id="t15:11:50"
| colspan="2" | * Viking-Ice sneaks in a bit late..
|| [[#t15:11:50|15:11]]
|- id="t15:11:55"
! style="background-color: #407a40" | jlaska
| style="color: #407a40" | Viking-Ice: welcome!
|| [[#t15:11:55|15:11]]
|- id="t15:11:57"
! style="background-color: #407a40" | jlaska
| style="color: #407a40" | #topic Fedora 13 RC test status
|| [[#t15:11:57|15:11]]
|- id="t15:12:20"
! style="background-color: #407a40" | jlaska
| style="color: #407a40" | #info the current deliverable I'm working on is the Pre-RC Branched Acceptance Test Run
|| [[#t15:12:20|15:12]]
|- id="t15:12:41"
! style="background-color: #407a40" | jlaska
| style="color: #407a40" | a new anaconda was built, and given proper karma in bodhi to be available for Branched testing
|| [[#t15:12:41|15:12]]
|- id="t15:13:02"
! style="background-color: #407a40" | jlaska
| style="color: #407a40" | it's an unusual worflow to run through an acceptanc test, but that's hopefully something we can work out post F-13
|| [[#t15:13:02|15:13]]
|- id="t15:13:14"
! style="background-color: #407a40" | jlaska
| style="color: #407a40" | the Friday Branched compose failed to build due to deps, but it looks like things are okay today
|| [[#t15:13:14|15:13]]
|- id="t15:13:20"
! style="background-color: #407a40" | jlaska
| style="color: #407a40" | I'll be posting a test summary to the list later this afternoon
|| [[#t15:13:20|15:13]]
|- id="t15:14:00"
! style="background-color: #407a40" | jlaska
| style="color: #407a40" | #info there was a F13Blocker review last week - see http://meetbot.fedoraproject.org/fedora-bugzappers/2010-04-23/fedora-bugzappers.2010-04-23-16.06.html
|| [[#t15:14:00|15:14]]
|- id="t15:14:24"
! style="background-color: #407a40" | jlaska
| style="color: #407a40" | We can expect the following milestones this week ...
|| [[#t15:14:24|15:14]]
|- id="t15:14:33"
! style="background-color: #407a40" | jlaska
| style="color: #407a40" | #info 2010-04-29 - Test 'Final' Test Compose
|| [[#t15:14:33|15:14]]
|- id="t15:14:50"
! style="background-color: #407a40" | jlaska
| style="color: #407a40" | #info 2010-04-29 - PreUpgrade test day - [[Test_Day:2010-04-29_Preupgrade]]
|| [[#t15:14:50|15:14]]
|- id="t15:15:00"
! style="background-color: #407a40" | jlaska
| style="color: #407a40" | #info 2010-04-30 - Final Blocker Meeting (f13blocker) #3
|| [[#t15:15:00|15:15]]
|- id="t15:15:32"
! style="background-color: #407a40" | jlaska
| style="color: #407a40" | In other F-13 testing news, there have been some i18n test considerations under discussion
|| [[#t15:15:32|15:15]]
|- id="t15:15:49"
! style="background-color: #407a40" | jlaska
| style="color: #407a40" | you may have see this already from a ticket mail to test@
|| [[#t15:15:49|15:15]]
|- id="t15:16:02"
! style="background-color: #854685" | damNageHack
| style="color: #854685" | how is a release critical bug marked in bugzilla?
|| [[#t15:16:02|15:16]]
|- id="t15:16:23"
! style="background-color: #407a40" | jlaska
| style="color: #407a40" | damNageHack: to mark a bug as a release blocker, you add the blocks: F13Blocker
|| [[#t15:16:23|15:16]]
|- id="t15:16:38"
! style="background-color: #407a40" | jlaska
| style="color: #407a40" | damNageHack: and add a quick statement indicating what release criteria are impacted by the bug
|| [[#t15:16:38|15:16]]
|- id="t15:16:57"
! style="background-color: #854685" | damNageHack
| style="color: #854685" | k thx. i will not do such a thing. only for my information :)
|| [[#t15:16:57|15:16]]
|- id="t15:17:19"
! style="background-color: #407a40" | jlaska
| style="color: #407a40" | damNageHack: no worries, folks are encouraged to escalate issues of concern
|| [[#t15:17:19|15:17]]
|- id="t15:17:39"
! style="background-color: #407a40" | jlaska
| style="color: #407a40" | we've documented what are considered the most common release criteria at [[Fedora_13_Final_Release_Criteria]]
|| [[#t15:17:39|15:17]]
|- id="t15:17:43"
! style="background-color: #854685" | damNageHack
| style="color: #854685" | i am thinking of the bug with gtk2 v2.19/2.20 + thunar/pcmanfm
|| [[#t15:17:43|15:17]]
|- id="t15:17:51"
! style="background-color: #488888" | kparal
| style="color: #488888" | damNageHack: current blocker list is here: https://bugzilla.redhat.com/showdependencytree.cgi?id=507681&amp;hide_resolved=1
|| [[#t15:17:51|15:17]]
|- id="t15:18:03"
! style="background-color: #407a40" | jlaska
| style="color: #407a40" | however, there are always cases where bugs don't fit a criteria ... feel free to raise those issues on the mailing list, or #fedora-qa
|| [[#t15:18:03|15:18]]
|- id="t15:18:23"
! style="background-color: #854685" | damNageHack
| style="color: #854685" | k tx
|| [[#t15:18:23|15:18]]
|- id="t15:18:56"
! style="background-color: #407a40" | jlaska
| style="color: #407a40" | So lastly, if anyone wants to contribute to additional i18n tests  ... feel free to add your thoughts to https://fedorahosted.org/fedora-qa/ticket/63
|| [[#t15:18:56|15:18]]
|- id="t15:18:58"
! style="background-color: #854685" | damNageHack
| style="color: #854685" | i can see a lot of still open bugs :)
|| [[#t15:18:58|15:18]]
|- id="t15:19:11"
! style="background-color: #407a40" | jlaska
| style="color: #407a40" | damNageHack: 18 non-MODIFIED bugs ... we have a lot of testing MODIFIED and ON_QA bugs to do
|| [[#t15:19:11|15:19]]
|- id="t15:19:23"
! style="background-color: #407a40" | jlaska
| style="color: #407a40" | okay ... next agenda item ...
|| [[#t15:19:23|15:19]]
|- id="t15:19:40"
! style="background-color: #854685" | damNageHack
| style="color: #854685" | i am sure, it can be done
|| [[#t15:19:40|15:19]]
|- id="t15:20:02"
! style="background-color: #854685" | damNageHack
| style="color: #854685" | fedora has a high quality, i like that :)
|| [[#t15:20:02|15:20]]
|- id="t15:20:28"
! style="background-color: #407a40" | jlaska
| style="color: #407a40" | damNageHack: glad to hear, we only get that because people contribute time to make it better ... so thank you! :)
|| [[#t15:20:28|15:20]]
|- id="t15:20:33"
! style="background-color: #407a40" | jlaska
| style="color: #407a40" | #topic Proventesters check-in
|| [[#t15:20:33|15:20]]
|- id="t15:20:47"
! style="background-color: #407a40" | jlaska
| style="color: #407a40" | We had 2 action items to follow-up on from last week
|| [[#t15:20:47|15:20]]
|- id="t15:20:54"
! style="background-color: #407a40" | jlaska
| style="color: #407a40" | looks like maxamillion completed both of them
|| [[#t15:20:54|15:20]]
|- id="t15:21:22"
! style="background-color: #407a40" | jlaska
| style="color: #407a40" | #info maxamillion - sent Proventester draft to test@l.fp.org for final review (see http://lists.fedoraproject.org/pipermail/test/2010-April/090252.html)
|| [[#t15:21:22|15:21]]
|- id="t15:21:42"
! style="background-color: #407a40" | jlaska
| style="color: #407a40" | #info maxamillion requested creation of proventester FAS group (see https://fedorahosted.org/fedora-infrastructure/ticket/2114)
|| [[#t15:21:42|15:21]]
|- id="t15:21:48"
! style="background-color: #407a40" | jlaska
| style="color: #407a40" | thanks maxamillion! :)
|| [[#t15:21:48|15:21]]
|- id="t15:22:00"
! style="background-color: #407a40" | jlaska
| style="color: #407a40" | he's not around right now, but I was going to ask the obvious ...
|| [[#t15:22:00|15:22]]
|- id="t15:22:07"
! style="background-color: #407a40" | jlaska
| style="color: #407a40" | what's next?
|| [[#t15:22:07|15:22]]
|- id="t15:22:27"
! style="background-color: #488888" | kparal
| style="color: #488888" | now to populate the group
|| [[#t15:22:27|15:22]]
|- id="t15:22:40"
! style="background-color: #407a40" | jlaska
| style="color: #407a40" | yeah, is it time to request applications to the group?
|| [[#t15:22:40|15:22]]
|- id="t15:22:50"
! style="background-color: #407a40" | jlaska
| style="color: #407a40" | do we know how to evaluate and mentor applicants?
|| [[#t15:22:50|15:22]]
|- id="t15:23:25"
! style="background-color: #407a40" | jlaska
| style="color: #407a40" | Has bodhi been changed to use 'proventester' FAS group, instead of 'qa' for critpath updates?
|| [[#t15:23:25|15:23]]
|- id="t15:23:47"
! style="background-color: #488888" | kparal
| style="color: #488888" | the mentoring process could be described, yes
|| [[#t15:23:47|15:23]]
|- id="t15:23:57"
! style="background-color: #8c4a4a" | lmacken
| style="color: #8c4a4a" | jlaska: I have myself CC'd to the proventesters infrastructure ticket, but it's still not completed, from what I can tell
|| [[#t15:23:57|15:23]]
|- id="t15:24:09"
! style="background-color: #8c4a4a" | lmacken
| style="color: #8c4a4a" | once it's done, changing it in bodhi will be trivial
|| [[#t15:24:09|15:24]]
|- id="t15:24:12"
! style="background-color: #818144" | jeff_hann
| style="color: #818144" | jlaska: what are the qualities required for someone to become a proventester?
|| [[#t15:24:12|15:24]]
|- id="t15:24:24"
! style="background-color: #407a40" | jlaska
| style="color: #407a40" | lmacken: is this the ticket to create the group, or to change bodhi to use proventester group?
|| [[#t15:24:24|15:24]]
|- id="t15:24:37"
! style="background-color: #8c4a4a" | lmacken
| style="color: #8c4a4a" | jlaska: to create the group... once it's created, I'll change it in bodhi
|| [[#t15:24:37|15:24]]
|- id="t15:25:05"
! style="background-color: #407a40" | jlaska
| style="color: #407a40" | lmacken: eggsellent, thank you!
|| [[#t15:25:05|15:25]]
|- id="t15:25:26"
! style="background-color: #407a40" | jlaska
| style="color: #407a40" | #action current members of the 'qa' group ... apply to 'proventesters'
|| [[#t15:25:26|15:25]]
|- id="t15:25:41"
| colspan="2" | * jskladan needs to leave now. see you around, gang!
|| [[#t15:25:41|15:25]]
|- id="t15:25:41"
! style="background-color: #407a40" | jlaska
| style="color: #407a40" | jeff_hann: kparal yeah good suggestions
|| [[#t15:25:41|15:25]]
|- id="t15:25:45"
! style="background-color: #407a40" | jlaska
| style="color: #407a40" | jskladan: take care!
|| [[#t15:25:45|15:25]]
|- id="t15:26:10"
! style="background-color: #4b904b" | jskladan
| style="color: #4b904b" | jlaska: thanks, will do my best
|| [[#t15:26:10|15:26]]
|- id="t15:26:10"
! style="background-color: #407a40" | jlaska
| style="color: #407a40" | kparal: jeff_hann: I can take an action to follow-up w/ maxamillion after the meeting
|| [[#t15:26:10|15:26]]
|- id="t15:26:32"
| colspan="2" | * kparal brb in 2min
|| [[#t15:26:32|15:26]]
|- id="t15:26:46"
! style="background-color: #818144" | jeff_hann
| style="color: #818144" | jlaska: a page where the exact criteria needed would be useful
|| [[#t15:26:46|15:26]]
|- id="t15:26:57"
! style="background-color: #407a40" | jlaska
| style="color: #407a40" | jeff_hann: yeah I agree
|| [[#t15:26:57|15:26]]
|- id="t15:27:13"
! style="background-color: #407a40" | jlaska
| style="color: #407a40" | I believe we started that page a few weeks back, but that might just need to be refreshed
|| [[#t15:27:13|15:27]]
|- id="t15:27:19"
! style="background-color: #818144" | jeff_hann
| style="color: #818144" | jlaska: and instructions as how/what to fill in TRAC
|| [[#t15:27:19|15:27]]
|- id="t15:27:25"
! style="background-color: #407a40" | jlaska
| style="color: #407a40" | #info a page where exact criteria needed for proventesters would be useful
|| [[#t15:27:25|15:27]]
|- id="t15:27:34"
! style="background-color: #407a40" | jlaska
| style="color: #407a40" | jeff_hann: in TRAC?
|| [[#t15:27:34|15:27]]
|- id="t15:27:40"
! style="background-color: #407a40" | jlaska
| style="color: #407a40" | jeff_hann: oh for applying to the group?
|| [[#t15:27:40|15:27]]
|- id="t15:27:49"
! style="background-color: #818144" | jeff_hann
| style="color: #818144" | jeff_hann: yeah
|| [[#t15:27:49|15:27]]
|- id="t15:27:58"
! style="background-color: #407a40" | jlaska
| style="color: #407a40" | #info provide a TRAC ticket template for mentor requests
|| [[#t15:27:58|15:27]]
|- id="t15:28:22"
! style="background-color: #407a40" | jlaska
| style="color: #407a40" | #action jlaska to follow-up w/ maxamillion after meeting
|| [[#t15:28:22|15:28]]
|- id="t15:28:54"
! style="background-color: #407a40" | jlaska
| style="color: #407a40" | for any other ideas that come to folks, please feel free to reply to the meeting minutes I send out
|| [[#t15:28:54|15:28]]
|- id="t15:28:58"
! style="background-color: #407a40" | jlaska
| style="color: #407a40" | next topic ...
|| [[#t15:28:58|15:28]]
|- id="t15:29:00"
! style="background-color: #407a40" | jlaska
| style="color: #407a40" | #topic Package Acceptance Test Plan check-in
|| [[#t15:29:00|15:29]]
|- id="t15:29:01"
! style="background-color: #818144" | jeff_hann
| style="color: #818144" | jlaska: of course, I would like to join the proventesters group; been slackin' recently.
|| [[#t15:29:01|15:29]]
|- id="t15:29:09"
| colspan="2" | * kparal back
|| [[#t15:29:09|15:29]]
|- id="t15:29:21"
! style="background-color: #407a40" | jlaska
| style="color: #407a40" | kparal: hey, do you want to give an update on this topic?
|| [[#t15:29:21|15:29]]
|- id="t15:29:25"
! style="background-color: #488888" | kparal
| style="color: #488888" | sure
|| [[#t15:29:25|15:29]]
|- id="t15:29:33"
! style="background-color: #407a40" | jlaska
| style="color: #407a40" | #chair kparal
|| [[#t15:29:33|15:29]]
|- id="t15:29:33"
! style="background-color: #42427e" | zodbot
| style="color: #42427e" | Current chairs: jlaska kparal
|| [[#t15:29:33|15:29]]
|- id="t15:29:41"
! style="background-color: #488888" | kparal
| style="color: #488888" | #link [[User:Kparal/Proposal:Package_update_acceptance_test_plan]]
|| [[#t15:29:41|15:29]]
|- id="t15:30:03"
! style="background-color: #488888" | kparal
| style="color: #488888" | so, I posted a few last questions about the test plan and a call for comments
|| [[#t15:30:03|15:30]]
|- id="t15:30:25"
! style="background-color: #488888" | kparal
| style="color: #488888" | #link http://lists.fedoraproject.org/pipermail/test/2010-April/090287.html
|| [[#t15:30:25|15:30]]
|- id="t15:30:48"
! style="background-color: #407a40" | jlaska
| style="color: #407a40" | kparal: thanks for picking that back up ... I think I've got a few UNREAD's to read still on that thread
|| [[#t15:30:48|15:30]]
|- id="t15:30:57"
! style="background-color: #488888" | kparal
| style="color: #488888" | from discussion with jlaska and jkeating I changed a few definitions
|| [[#t15:30:57|15:30]]
|- id="t15:31:03"
! style="background-color: #488888" | kparal
| style="color: #488888" | so thanks for all comments
|| [[#t15:31:03|15:31]]
|- id="t15:31:21"
! style="background-color: #488888" | kparal
| style="color: #488888" | I believe the test plan should be final now
|| [[#t15:31:21|15:31]]
|- id="t15:31:22"
| colspan="2" | * jlaska loves your test categories
|| [[#t15:31:22|15:31]]
|- id="t15:31:27"
! style="background-color: #488888" | kparal
| style="color: #488888" | if no more comments come
|| [[#t15:31:27|15:31]]
|- id="t15:31:32"
! style="background-color: #407a40" | jlaska
| style="color: #407a40" | mandatory, introspection, advisory :)
|| [[#t15:31:32|15:31]]
|- id="t15:31:51"
! style="background-color: #488888" | kparal
| style="color: #488888" | one remaining item is to create separate wiki page for each test case
|| [[#t15:31:51|15:31]]
|- id="t15:32:10"
! style="background-color: #488888" | kparal
| style="color: #488888" | #link https://fedorahosted.org/fedora-qa/ticket/62
|| [[#t15:32:10|15:32]]
|- id="t15:32:25"
! style="background-color: #488888" | kparal
| style="color: #488888" | and we can start to just implement it :)
|| [[#t15:32:25|15:32]]
|- id="t15:32:47"
! style="background-color: #488888" | kparal
| style="color: #488888" | alright, that would be it, I believe
|| [[#t15:32:47|15:32]]
|- id="t15:32:47"
! style="background-color: #407a40" | jlaska
| style="color: #407a40" | yay!
|| [[#t15:32:47|15:32]]
|- id="t15:33:01"
! style="background-color: #407a40" | jlaska
| style="color: #407a40" | kparal: thanks for the updates ... anything you'd like to track here for next week?
|| [[#t15:33:01|15:33]]
|- id="t15:33:33"
! style="background-color: #488888" | kparal
| style="color: #488888" | nope, I would say it's complete (nearly) :)
|| [[#t15:33:33|15:33]]
|- id="t15:33:41"
! style="background-color: #407a40" | jlaska
| style="color: #407a40" | awesome, nice work
|| [[#t15:33:41|15:33]]
|- id="t15:33:54"
! style="background-color: #407a40" | jlaska
| style="color: #407a40" | okay, the next planned topic I had was for AutoQA
|| [[#t15:33:54|15:33]]
|- id="t15:34:03"
! style="background-color: #407a40" | jlaska
| style="color: #407a40" | but we're low on AutoQA folks today
|| [[#t15:34:03|15:34]]
|- id="t15:34:09"
! style="background-color: #407a40" | jlaska
| style="color: #407a40" | #topic AutoQA update
|| [[#t15:34:09|15:34]]
|- id="t15:34:16"
! style="background-color: #407a40" | jlaska
| style="color: #407a40" | kparal: anything you'd like to note for this week?
|| [[#t15:34:16|15:34]]
|- id="t15:34:19"
! style="background-color: #488888" | kparal
| style="color: #488888" | I can say a few words for jskladan
|| [[#t15:34:19|15:34]]
|- id="t15:34:26"
! style="background-color: #407a40" | jlaska
| style="color: #407a40" | kparal: great, please go for it!
|| [[#t15:34:26|15:34]]
|- id="t15:34:32"
! style="background-color: #488888" | kparal
| style="color: #488888" | he created a test suite for resultdb API
|| [[#t15:34:32|15:34]]
|- id="t15:34:45"
! style="background-color: #488888" | kparal
| style="color: #488888" | and made some first draft of implementing the API
|| [[#t15:34:45|15:34]]
|- id="t15:35:04"
! style="background-color: #488888" | kparal
| style="color: #488888" | and of course the test suite failed, so he's now deep in solving the issues :)
|| [[#t15:35:04|15:35]]
|- id="t15:35:37"
! style="background-color: #488888" | kparal
| style="color: #488888" | but we could have some first attempts for API implementation soon
|| [[#t15:35:37|15:35]]
|- id="t15:35:53"
! style="background-color: #488888" | kparal
| style="color: #488888" | at least from what I caught
|| [[#t15:35:53|15:35]]
|- id="t15:36:34"
! style="background-color: #488888" | kparal
| style="color: #488888" | ok, as for other topics, no big development that I know of
|| [[#t15:36:34|15:36]]
|- id="t15:36:58"
! style="background-color: #488888" | kparal
| style="color: #488888" | so, let's move it to open discussion
|| [[#t15:36:58|15:36]]
|- id="t15:37:09"
! style="background-color: #488888" | kparal
| style="color: #488888" | #topic Open Floor
|| [[#t15:37:09|15:37]]
|- id="t15:37:21"
! style="background-color: #488888" | kparal
| style="color: #488888" | do you have anything you want to discuss today?
|| [[#t15:37:21|15:37]]
|- id="t15:39:05"
! style="background-color: #488888" | kparal
| style="color: #488888" | how it happens that when I'm the chairman the meeting is always so fast? :)
|| [[#t15:39:05|15:39]]
|- id="t15:40:03"
! style="background-color: #488888" | kparal
| style="color: #488888" | ok, last minute and then I'll end the meeting
|| [[#t15:40:03|15:40]]
|- id="t15:40:09"
! style="background-color: #818144" | jeff_hann
| style="color: #818144" | kparal: today there only few attendees
|| [[#t15:40:09|15:40]]
|- id="t15:40:16"
! style="background-color: #818144" | jeff_hann
| style="color: #818144" | *there are
|| [[#t15:40:16|15:40]]
|- id="t15:40:31"
! style="background-color: #488888" | kparal
| style="color: #488888" | jeff_hann: I see. everyone on holiday or something :)
|| [[#t15:40:31|15:40]]
|- id="t15:40:39"
! style="background-color: #407a40" | jlaska
| style="color: #407a40" | kparal: you're much better at moving the meeting along than I am! :D
|| [[#t15:40:39|15:40]]
|- id="t15:41:21"
| colspan="2" | * jlaska has mollases fingers
|| [[#t15:41:21|15:41]]
|- id="t15:41:43"
! style="background-color: #488888" | kparal
| style="color: #488888" | ok, so thanks everyone for comming in, have a nice day!
|| [[#t15:41:43|15:41]]
|- id="t15:41:51"
! style="background-color: #488888" | kparal
| style="color: #488888" | #endmeeting
|| [[#t15:41:51|15:41]]
|}
Generated by irclog2html.py 2.7 by [mailto:marius@pov.lt Marius Gedminas] - find it at [http://mg.pov.lt/irclog2html mg.pov.lt]!

Latest revision as of 09:01, 18 September 2016

Attendees

People present (lines said):

  • jlaska (91)
  • kparal (37)
  • jeff_hann (9)
  • damNageHack (8)
  • zodbot (4)
  • jskladan (3)
  • lmacken (3)
  • Viking-Ice (1)

Regrets:

Agenda

Previous meeting follow-up

  • jlaska + fenris02 to review whether F-13-Beta is an option for boot.fedoraproject.org
    • Already completed by the infrastructure team, yay infrastructure!

See agenda below for additional follow-up items included in specific topics

Fedora 13 RC test status

Upcoming test milestones:

  • 2010-04-16 - Pre-RC Branched Acceptance Test Plan -- DELAYED, now INPROGRESS
  • 2010-04-23 - Final Blocker Meeting (f13blocker) #2 (recap)
  • 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:

Recent test changes:

  • Adding i18n support to installation test plan (see details ticket#63)
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 Fedora_13_QA_Retrospective.

Proventesters check-in

Package Acceptance Test Plan check-in

AutoQA check-in

There has been a lot of AutoQA activities in recent weeks, jlaska asked the group to walk through some highlights.

  • Kparal provided some updates from jskladan on the results database efforts..
    • First draft of implementing the resultsdb API
    • Test suite for resultsdb API created

Open discussion - <Your topic here>

Upcoming QA events

Action items

  1. current members of the 'qa' group ... apply to 'proventesters'
  2. jlaska to follow-up w/ maxamillion after meeting

IRC Transcript

jlaska #startmeeting Fedora QA Meeting 15:00
zodbot Meeting started Mon Apr 26 15:00:08 2010 UTC. The chair is jlaska. Information about MeetBot at http://wiki.debian.org/MeetBot. 15:00
zodbot Useful Commands: #action #agreed #halp #info #idea #link #topic. 15:00
jlaska #meetingname fedora-qa 15:00
zodbot The meeting name has been set to 'fedora-qa' 15:00
jlaska #topic Gathering critical mass ... 15:00
* jeff_hann is here 15:00
* kparal jumps straight into meeting 15:00
jlaska jeff_hann: kparal: howdy 15:00
jeff_hann howdee 15:00
* jskladan watching from the shadows 15:00
* jlaska tips hat towards jskladan 15:01
damNageHack hi 15:02
jlaska damNageHack: hello :) 15:02
jlaska wwoods: adamw: you guys around? 15:02
jlaska I don't think this time slot works great for maxamillion, but lemme check ... 15:03
jlaska I've got a conflict @ the half hour increment ... so let's get started 15:04
jlaska if we run over, I may need help closing out the proposed agenda items 15:04
jlaska Proposed agenda - http://lists.fedoraproject.org/pipermail/test/2010-April/090413.html 15:05
jlaska #topic Previous meeting follow-up 15:05
jlaska #info jlaska + fenris02 to review whether F-13-Beta is an option for boot.fedoraproject.org 15:05
jlaska This was easy, thanks to the infrastructure team ... boot.fp.org should already have links to Fedora 13 beta 15:05
jlaska #info Completed by the infrastructure team, yay infrastructure! 15:06
jlaska #info adamw + jlaska - Bodhi QA workflow status check-in 15:06
kparal jlaska: is it necessary to re-download the images? 15:06
jlaska kparal: good question ... I tested by downloading the images 15:07
jlaska so I don't know if the configs are pulled from the server, or are on the media 15:07
kparal ok 15:08
* kparal will test some day 15:08
jlaska kparal: that'll likely need a follow-up to #fedora-admin for guidance, I'm not sure 15:08
jlaska adamw and I spoke w/ lmacken last week, he is working to organize a lot of TRAC tickets into a bodhi-2.0 milestone 15:09
jlaska and expected to have that finished out in the next few weeks 15:09
jlaska bodhi-2.0 milestone - https://fedorahosted.org/bodhi/milestone/2.0 15:09
jlaska Some initial requirements gathering will also take place in the coming weeks 15:09
jlaska my understanding is this will be helpful for us so we can coordinate AutoQA dependencies and document/educate 'proventesters' on the QA workflow through bodhi 15:10
jlaska we had several other follow-up items, but I've moved those into specific topics below ... 15:10
jlaska so I'll dive in, unless anyone has other thoughts 15:11
* Viking-Ice sneaks in a bit late.. 15:11
jlaska Viking-Ice: welcome! 15:11
jlaska #topic Fedora 13 RC test status 15:11
jlaska #info the current deliverable I'm working on is the Pre-RC Branched Acceptance Test Run 15:12
jlaska a new anaconda was built, and given proper karma in bodhi to be available for Branched testing 15:12
jlaska it's an unusual worflow to run through an acceptanc test, but that's hopefully something we can work out post F-13 15:13
jlaska the Friday Branched compose failed to build due to deps, but it looks like things are okay today 15:13
jlaska I'll be posting a test summary to the list later this afternoon 15:13
jlaska #info there was a F13Blocker review last week - see http://meetbot.fedoraproject.org/fedora-bugzappers/2010-04-23/fedora-bugzappers.2010-04-23-16.06.html 15:14
jlaska We can expect the following milestones this week ... 15:14
jlaska #info 2010-04-29 - Test 'Final' Test Compose 15:14
jlaska #info 2010-04-29 - PreUpgrade test day - Test_Day:2010-04-29_Preupgrade 15:14
jlaska #info 2010-04-30 - Final Blocker Meeting (f13blocker) #3 15:15
jlaska In other F-13 testing news, there have been some i18n test considerations under discussion 15:15
jlaska you may have see this already from a ticket mail to test@ 15:15
damNageHack how is a release critical bug marked in bugzilla? 15:16
jlaska damNageHack: to mark a bug as a release blocker, you add the blocks: F13Blocker 15:16
jlaska damNageHack: and add a quick statement indicating what release criteria are impacted by the bug 15:16
damNageHack k thx. i will not do such a thing. only for my information :) 15:16
jlaska damNageHack: no worries, folks are encouraged to escalate issues of concern 15:17
jlaska we've documented what are considered the most common release criteria at Fedora_13_Final_Release_Criteria 15:17
damNageHack i am thinking of the bug with gtk2 v2.19/2.20 + thunar/pcmanfm 15:17
kparal damNageHack: current blocker list is here: https://bugzilla.redhat.com/showdependencytree.cgi?id=507681&hide_resolved=1 15:17
jlaska however, there are always cases where bugs don't fit a criteria ... feel free to raise those issues on the mailing list, or #fedora-qa 15:18
damNageHack k tx 15:18
jlaska So lastly, if anyone wants to contribute to additional i18n tests ... feel free to add your thoughts to https://fedorahosted.org/fedora-qa/ticket/63 15:18
damNageHack i can see a lot of still open bugs :) 15:18
jlaska damNageHack: 18 non-MODIFIED bugs ... we have a lot of testing MODIFIED and ON_QA bugs to do 15:19
jlaska okay ... next agenda item ... 15:19
damNageHack i am sure, it can be done 15:19
damNageHack fedora has a high quality, i like that :) 15:20
jlaska damNageHack: glad to hear, we only get that because people contribute time to make it better ... so thank you! :) 15:20
jlaska #topic Proventesters check-in 15:20
jlaska We had 2 action items to follow-up on from last week 15:20
jlaska looks like maxamillion completed both of them 15:20
jlaska #info maxamillion - sent Proventester draft to test@l.fp.org for final review (see http://lists.fedoraproject.org/pipermail/test/2010-April/090252.html) 15:21
jlaska #info maxamillion requested creation of proventester FAS group (see https://fedorahosted.org/fedora-infrastructure/ticket/2114) 15:21
jlaska thanks maxamillion! :) 15:21
jlaska he's not around right now, but I was going to ask the obvious ... 15:22
jlaska what's next? 15:22
kparal now to populate the group 15:22
jlaska yeah, is it time to request applications to the group? 15:22
jlaska do we know how to evaluate and mentor applicants? 15:22
jlaska Has bodhi been changed to use 'proventester' FAS group, instead of 'qa' for critpath updates? 15:23
kparal the mentoring process could be described, yes 15:23
lmacken jlaska: I have myself CC'd to the proventesters infrastructure ticket, but it's still not completed, from what I can tell 15:23
lmacken once it's done, changing it in bodhi will be trivial 15:24
jeff_hann jlaska: what are the qualities required for someone to become a proventester? 15:24
jlaska lmacken: is this the ticket to create the group, or to change bodhi to use proventester group? 15:24
lmacken jlaska: to create the group... once it's created, I'll change it in bodhi 15:24
jlaska lmacken: eggsellent, thank you! 15:25
jlaska #action current members of the 'qa' group ... apply to 'proventesters' 15:25
* jskladan needs to leave now. see you around, gang! 15:25
jlaska jeff_hann: kparal yeah good suggestions 15:25
jlaska jskladan: take care! 15:25
jskladan jlaska: thanks, will do my best 15:26
jlaska kparal: jeff_hann: I can take an action to follow-up w/ maxamillion after the meeting 15:26
* kparal brb in 2min 15:26
jeff_hann jlaska: a page where the exact criteria needed would be useful 15:26
jlaska jeff_hann: yeah I agree 15:26
jlaska I believe we started that page a few weeks back, but that might just need to be refreshed 15:27
jeff_hann jlaska: and instructions as how/what to fill in TRAC 15:27
jlaska #info a page where exact criteria needed for proventesters would be useful 15:27
jlaska jeff_hann: in TRAC? 15:27
jlaska jeff_hann: oh for applying to the group? 15:27
jeff_hann jeff_hann: yeah 15:27
jlaska #info provide a TRAC ticket template for mentor requests 15:27
jlaska #action jlaska to follow-up w/ maxamillion after meeting 15:28
jlaska for any other ideas that come to folks, please feel free to reply to the meeting minutes I send out 15:28
jlaska next topic ... 15:28
jlaska #topic Package Acceptance Test Plan check-in 15:29
jeff_hann jlaska: of course, I would like to join the proventesters group; been slackin' recently. 15:29
* kparal back 15:29
jlaska kparal: hey, do you want to give an update on this topic? 15:29
kparal sure 15:29
jlaska #chair kparal 15:29
zodbot Current chairs: jlaska kparal 15:29
kparal #link User:Kparal/Proposal:Package_update_acceptance_test_plan 15:29
kparal so, I posted a few last questions about the test plan and a call for comments 15:30
kparal #link http://lists.fedoraproject.org/pipermail/test/2010-April/090287.html 15:30
jlaska kparal: thanks for picking that back up ... I think I've got a few UNREAD's to read still on that thread 15:30
kparal from discussion with jlaska and jkeating I changed a few definitions 15:30
kparal so thanks for all comments 15:31
kparal I believe the test plan should be final now 15:31
* jlaska loves your test categories 15:31
kparal if no more comments come 15:31
jlaska mandatory, introspection, advisory :) 15:31
kparal one remaining item is to create separate wiki page for each test case 15:31
kparal #link https://fedorahosted.org/fedora-qa/ticket/62 15:32
kparal and we can start to just implement it :) 15:32
kparal alright, that would be it, I believe 15:32
jlaska yay! 15:32
jlaska kparal: thanks for the updates ... anything you'd like to track here for next week? 15:33
kparal nope, I would say it's complete (nearly) :) 15:33
jlaska awesome, nice work 15:33
jlaska okay, the next planned topic I had was for AutoQA 15:33
jlaska but we're low on AutoQA folks today 15:34
jlaska #topic AutoQA update 15:34
jlaska kparal: anything you'd like to note for this week? 15:34
kparal I can say a few words for jskladan 15:34
jlaska kparal: great, please go for it! 15:34
kparal he created a test suite for resultdb API 15:34
kparal and made some first draft of implementing the API 15:34
kparal and of course the test suite failed, so he's now deep in solving the issues :) 15:35
kparal but we could have some first attempts for API implementation soon 15:35
kparal at least from what I caught 15:35
kparal ok, as for other topics, no big development that I know of 15:36
kparal so, let's move it to open discussion 15:36
kparal #topic Open Floor 15:37
kparal do you have anything you want to discuss today? 15:37
kparal how it happens that when I'm the chairman the meeting is always so fast? :) 15:39
kparal ok, last minute and then I'll end the meeting 15:40
jeff_hann kparal: today there only few attendees 15:40
jeff_hann *there are 15:40
kparal jeff_hann: I see. everyone on holiday or something :) 15:40
jlaska kparal: you're much better at moving the meeting along than I am! :D 15:40
* jlaska has mollases fingers 15:41
kparal ok, so thanks everyone for comming in, have a nice day! 15:41
kparal #endmeeting 15:41

Generated by irclog2html.py 2.7 by Marius Gedminas - find it at mg.pov.lt!

Retrieved from "https://fedoraproject.org/w/index.php?title=QA/Meetings/20100426&oldid=472368"