From Fedora Project Wiki

< QA‎ | Meetings

m (Updated date)
m (internal link cleaning)
 
(2 intermediate revisions by one other user not shown)
Line 1: Line 1:
= Agenda topics =
= Attendees =
= Attendees =


People present (lines said)
People present (lines said)
* jlaska (141)
* wwoods (30)
* adamw (22)
* kparal (21)
* Viking-Ice (8)
* nirik (5)
* cwickert (5)
* zodbot (4)
* RodrigoPadula (3)
* buggbot (1)
* abadger1999 (1)
* tk009 (1)


Regrets:
Regrets:
Line 12: Line 23:
= Agenda =
= Agenda =
* [http://lists.fedoraproject.org/pipermail/test/2010-January/088008.html Proposed meeting agenda]
* [http://lists.fedoraproject.org/pipermail/test/2010-January/088008.html Proposed meeting agenda]
* [FIXME meetbot summary]
* [http://meetbot.fedoraproject.org/fedora-meeting/2010-01-18/qa.2010-01-18-16.00.html meetbot summary]


== Previous meeting follow-up ==
== Previous meeting follow-up ==


* maxamillion bring back conversation about Xfce 4.8 updato on xfce@lists.fp.o and inform about conclusion
* maxamillion bring back conversation about Xfce 4.8 updato on xfce@lists.fp.o and inform about conclusion
** No updates, save for next week
* Viking-Ice write lxde tests and find a date for the test day
* Viking-Ice write lxde tests and find a date for the test day
** Created [https://fedorahosted.org/fedora-qa/ticket/46 ticket#46], agreed to move future discussion to the ticket
* cwickert to file an infrastruture ticket for the lxde mailing list
* cwickert to file an infrastruture ticket for the lxde mailing list
** https://admin.fedoraproject.org/mailman/listinfo/lxde
* adamw and rhe to discuss ways to add install testing as a QA activity
* adamw and rhe to discuss ways to add install testing as a QA activity
** [[User:rhe|Hurry]] created a new install test home at [[QA/Installation_Test]].  The idea is to have that big explanatory page, and a bit in the 'joining' page which would link to it
** Adamw would look for possibilities to propose integrating the new home with the existing [[QA:Fedora_13_Install_Test_Plan]].
* jlaska to reach out to beland for guidance/ideas on how to document the process (or point to existing documentation) for how bugs are noted (common_bugs, release notes, install guide etc...) How to determine which bugs land in which place?
* jlaska to reach out to beland for guidance/ideas on how to document the process (or point to existing documentation) for how bugs are noted (common_bugs, release notes, install guide etc...) How to determine which bugs land in which place?
** Yuck, no traction on this task, jlaska will get things rolling with this task.


== Security Policy Update ==
== Security Policy Update ==


On Friday's FESCO Meeting, Adam and Will responded to questions concerning building project-wide consensus around a security policy for Fedora (see FESCO [https://fedorahosted.org/fesco/ticket/297 ticket#297]).
On Friday's FESCO Meeting, Adam and Will responded to questions concerning building project-wide consensus around a security policy for Fedora (see FESCO [https://fedorahosted.org/fesco/ticket/297 ticket#297]).
Adam informed the group that FESCO kicked it back to the QA team with a promise that if we come up with some kind of draft policy, people who have a clue about security will be gracious enough to review it.  So as far as FESCo is concerned the next thing that happens is I come back with a draft privilege escalation policy in hand.
Adam noted he would draft something quick'n'dirty using [http://spot.livejournal.com/312216.html Spot's famous blog post] as a foundation, then seek QA team review before approaching FESCO.


== fedora-release-rawhide ==
== fedora-release-rawhide ==


[[User:wwoods|wwoods]] noted that a new fedora-release-rawhide package may impact how we document opting into (and out of) testing rawhide via yum (see [[Releases/Rawhide#Testing_Rawhide]]).
[[User:wwoods|wwoods]] noted that a new fedora-release-rawhide package may impact how we document opting into (and out of) testing rawhide via yum (see [[Releases/Rawhide#Testing_Rawhide]]).
Nirik offered updates to [[Releases/Rawhide]] to help explain how to activate the rawhide repos.  Jlaska suggested that testers on test@l.fp.org would no doubt be able to help review the recommendations.


== AutoQA project update ==
== AutoQA project update ==
Line 41: Line 69:


''This week''
''This week''
* Test results are now being sent to autoqa-results, the next large step is  
* Test results are now sent to autoqa-results, the next large step is ...
* Continue discussing and start requirements gathering for a more formal method for collecting and presenting package update test results (see https://fedorahosted.org/pipermail/autoqa-devel/2010-January/000120.html)
* Continue discussing and start requirements gathering for a more formal method for collecting and presenting package update test results (see https://fedorahosted.org/pipermail/autoqa-devel/2010-January/000120.html)


Line 53: Line 81:


''This week''
''This week''
* lmacken working an API change into the next release of bodhi
* A close to working depsolv test case (see [http://git.fedorahosted.org/git/?p=autoqa.git;a=blob;f=tests/depcheck/depcheck]) is available.  Further clean-up needed.


=== install automation ===
=== install automation ===
Line 64: Line 95:
''This week''
''This week''
* Continue working towards a single python test that will automate a DVD install
* Continue working towards a single python test that will automate a DVD install
* Publish test code using either a public git branch, code on a people page, just a local git checkout


=== packaging/deployment ===
=== packaging/deployment ===
Line 85: Line 117:


== Open discussion - <Your topic here> ==
== Open discussion - <Your topic here> ==
=== When is the next F-13 milestone? ===
Wwoods asked  when the next scheduled rawhide install image drop was (see [[#Upcoming QA events]] below (2010-01-21 - Pre-Alpha Rawhide Acceptance Test Plan #1).  See [https://fedorahosted.org/rel-eng/ticket/3277 rel-eng ticket#3277] for details.
Jlaska also noted that anaconda-13.16 (plus http://clumens.fedorapeople.org/updates.img) had recently gone through an automated rats_install test run.  For results, see http://jlaska.fedorapeople.org/rats.png.


= Upcoming QA events =
= Upcoming QA events =
Line 96: Line 134:


= Action items =
= Action items =
* jlaska - reach out to beland for guidance/ideas on how to document the process for how bugs bubble through different release documents
* adamw to build on the famous spot security blog post and draft something quick'n'dirty for QA review
* nirik intends to update the [[Releases/Rawhide]] wiki page to reflect the changes (help appreciated)


= IRC transcript =
= IRC transcript =
{|
|- id="t16:00:41"
! style="background-color: #407a40" | jlaska
| style="color: #407a40" | #startmeeting Fedora QA Meeting
|| [[#t16:00:41|16:00]]
|- id="t16:00:41"
! style="background-color: #42427e" | zodbot
| style="color: #42427e" | Meeting started Mon Jan 18 16:00:41 2010 UTC.  The chair is jlaska. Information about MeetBot at http://wiki.debian.org/MeetBot.
|| [[#t16:00:41|16:00]]
|- id="t16:00:41"
! style="background-color: #42427e" | zodbot
| style="color: #42427e" | Useful Commands: #action #agreed #halp #info #idea #link #topic.
|| [[#t16:00:41|16:00]]
|- id="t16:00:47"
! style="background-color: #407a40" | jlaska
| style="color: #407a40" | #meetingname qa
|| [[#t16:00:47|16:00]]
|- id="t16:00:47"
! style="background-color: #42427e" | zodbot
| style="color: #42427e" | The meeting name has been set to 'qa'
|| [[#t16:00:47|16:00]]
|- id="t16:00:52"
! style="background-color: #818144" | wwoods
| style="color: #818144" | meeting powers go!
|| [[#t16:00:52|16:00]]
|- id="t16:01:07"
! style="background-color: #407a40" | jlaska
| style="color: #407a40" | queue the robot sounds
|| [[#t16:01:07|16:01]]
|- id="t16:01:10"
! style="background-color: #407a40" | jlaska
| style="color: #407a40" | #topic gathering
|| [[#t16:01:10|16:01]]
|- id="t16:01:12"
| colspan="2" | * kparal is here
|| [[#t16:01:12|16:01]]
|- id="t16:01:20"
! style="background-color: #407a40" | jlaska
| style="color: #407a40" | wwoods: kparal: howdy
|| [[#t16:01:20|16:01]]
|- id="t16:01:35"
! style="background-color: #407a40" | jlaska
| style="color: #407a40" | anyone else primed and ready for another edition of the QA meeting?
|| [[#t16:01:35|16:01]]
|- id="t16:01:47"
| colspan="2" | * tk009
|| [[#t16:01:47|16:01]]
|- id="t16:01:56"
! style="background-color: #854685" | adamw
| style="color: #854685" | morning
|| [[#t16:01:56|16:01]]
|- id="t16:02:01"
! style="background-color: #407a40" | jlaska
| style="color: #407a40" | tk009: adamw hi there
|| [[#t16:02:01|16:02]]
|- id="t16:02:15"
! style="background-color: #854685" | adamw
| style="color: #854685" | sorry, /me is tweaking with stuff again
|| [[#t16:02:15|16:02]]
|- id="t16:02:45"
! style="background-color: #407a40" | jlaska
| style="color: #407a40" | not sure if Viking-Ice or maxamillion are around too
|| [[#t16:02:45|16:02]]
|- id="t16:02:52"
| colspan="2" | * Viking-Ice here
|| [[#t16:02:52|16:02]]
|- id="t16:02:59"
! style="background-color: #407a40" | jlaska
| style="color: #407a40" | Viking-Ice: oh good, welcome!
|| [[#t16:02:59|16:02]]
|- id="t16:03:57"
! style="background-color: #407a40" | jlaska
| style="color: #407a40" | okay, I put a ping out to Adam Miller, but I think he might be busy at the moment
|| [[#t16:03:57|16:03]]
|- id="t16:04:01"
! style="background-color: #407a40" | jlaska
| style="color: #407a40" | so let's get started ...
|| [[#t16:04:01|16:04]]
|- id="t16:04:13"
! style="background-color: #407a40" | jlaska
| style="color: #407a40" | Working off the agenda here http://lists.fedoraproject.org/pipermail/test/2010-January/088008.html
|| [[#t16:04:13|16:04]]
|- id="t16:04:20"
! style="background-color: #407a40" | jlaska
| style="color: #407a40" | #topic Previous meeting follow-up
|| [[#t16:04:20|16:04]]
|- id="t16:04:40"
! style="background-color: #407a40" | jlaska
| style="color: #407a40" | #info maxamillion bring back conversation about Xfce 4.8 updato on xfce@lists.fp.o and inform about conclusion
|| [[#t16:04:40|16:04]]
|- id="t16:05:06"
! style="background-color: #407a40" | jlaska
| style="color: #407a40" | I don't have any updates on this, anyone else?  I'll leave it on the list until we get a chance to sync up with Adam M.
|| [[#t16:05:06|16:05]]
|- id="t16:05:43"
! style="background-color: #407a40" | jlaska
| style="color: #407a40" | moving on
|| [[#t16:05:43|16:05]]
|- id="t16:05:46"
! style="background-color: #407a40" | jlaska
| style="color: #407a40" | #info Viking-Ice write lxde tests and find a date for the test day
|| [[#t16:05:46|16:05]]
|- id="t16:06:05"
! style="background-color: #407a40" | jlaska
| style="color: #407a40" | Viking-Ice: any updates on definingsome LXDE tests for a possible test day?
|| [[#t16:06:05|16:06]]
|- id="t16:06:19"
! style="background-color: #488888" | Viking-Ice
| style="color: #488888" | Not really looking at it..
|| [[#t16:06:19|16:06]]
|- id="t16:06:27"
! style="background-color: #488888" | Viking-Ice
| style="color: #488888" | Created ticket in QA
|| [[#t16:06:27|16:06]]
|- id="t16:06:46"
! style="background-color: #488888" | Viking-Ice
| style="color: #488888" | [Fedora QA] #46: Write Test cases for LXDE components.
|| [[#t16:06:46|16:06]]
|- id="t16:06:58"
! style="background-color: #488888" | Viking-Ice
| style="color: #488888" | To keep track will update there as thing progress..
|| [[#t16:06:58|16:06]]
|- id="t16:07:18"
! style="background-color: #407a40" | jlaska
| style="color: #407a40" | okay thanks, lemme add that to the 'draft' test day schedule too ([[Talk:QA/Fedora_13_test_days)]]
|| [[#t16:07:18|16:07]]
|- id="t16:07:26"
! style="background-color: #488888" | Viking-Ice
| style="color: #488888" | Ok
|| [[#t16:07:26|16:07]]
|- id="t16:07:53"
! style="background-color: #407a40" | jlaska
| style="color: #407a40" | Viking-Ice: thanks for the update
|| [[#t16:07:53|16:07]]
|- id="t16:08:09"
! style="background-color: #407a40" | jlaska
| style="color: #407a40" | next up ....
|| [[#t16:08:09|16:08]]
|- id="t16:08:13"
! style="background-color: #407a40" | jlaska
| style="color: #407a40" | #info  adamw and rhe to discuss ways to add install testing as a QA activity
|| [[#t16:08:13|16:08]]
|- id="t16:08:32"
! style="background-color: #407a40" | jlaska
| style="color: #407a40" | hopefully rhe is sleeping, adamw ... sounds like you two made some progress?
|| [[#t16:08:32|16:08]]
|- id="t16:08:32"
! style="background-color: #854685" | adamw
| style="color: #854685" | well, rhe's not around, so i'll do it
|| [[#t16:08:32|16:08]]
|- id="t16:08:49"
! style="background-color: #854685" | adamw
| style="color: #854685" | rui did, i was too busy playing around with shiny shiny toys. =)
|| [[#t16:08:49|16:08]]
|- id="t16:09:06"
! style="background-color: #854685" | adamw
| style="color: #854685" | rui drafted an  installation testing page:
|| [[#t16:09:06|16:09]]
|- id="t16:09:13"
! style="background-color: #854685" | adamw
| style="color: #854685" | #link lxde fedora list
|| [[#t16:09:13|16:09]]
|- id="t16:09:15"
! style="background-color: #854685" | adamw
| style="color: #854685" | grr!
|| [[#t16:09:15|16:09]]
|- id="t16:09:18"
! style="background-color: #854685" | adamw
| style="color: #854685" | #link [[QA/Installation_Test]]
|| [[#t16:09:18|16:09]]
|- id="t16:09:23"
! style="background-color: #854685" | adamw
| style="color: #854685" | stupid paste buffers
|| [[#t16:09:23|16:09]]
|- id="t16:09:38"
! style="background-color: #854685" | adamw
| style="color: #854685" | the idea is to have that big explanatory page, and a bit in the 'joining' page which would link to it
|| [[#t16:09:38|16:09]]
|- id="t16:10:04"
! style="background-color: #854685" | adamw
| style="color: #854685" | I wondered if the big page should merge with [[QA:Fedora_12_Install_Test_Plan]] in some way; rui thinks not at present
|| [[#t16:10:04|16:10]]
|- id="t16:10:08"
! style="background-color: #407a40" | jlaska
| style="color: #407a40" | #info the idea is to have that big explanatory page, and a bit in the 'joining' page which would link to it
|| [[#t16:10:08|16:10]]
|- id="t16:10:39"
! style="background-color: #854685" | adamw
| style="color: #854685" | i'm going to take some time today to have a look at both pages and see whether I should disagree some more =), do a bit of a proofread, and come up with a draft for the bit to be added to the Joining page
|| [[#t16:10:39|16:10]]
|- id="t16:11:08"
! style="background-color: #407a40" | jlaska
| style="color: #407a40" | adamw: I can see the drive to avoid duplicate content.  Hopefully we can do that while preserving the concept of a 'test plan'
|| [[#t16:11:08|16:11]]
|- id="t16:11:25"
! style="background-color: #854685" | adamw
| style="color: #854685" | ayup
|| [[#t16:11:25|16:11]]
|- id="t16:11:28"
! style="background-color: #407a40" | jlaska
| style="color: #407a40" | rather ... while addressing the same issues that the test plan addresses
|| [[#t16:11:28|16:11]]
|- id="t16:11:38"
! style="background-color: #407a40" | jlaska
| style="color: #407a40" | whether it takes a different form or not
|| [[#t16:11:38|16:11]]
|- id="t16:11:48"
! style="background-color: #407a40" | jlaska
| style="color: #407a40" | cool, nice update
|| [[#t16:11:48|16:11]]
|- id="t16:12:04"
! style="background-color: #407a40" | jlaska
| style="color: #407a40" | next up ...
|| [[#t16:12:04|16:12]]
|- id="t16:12:09"
! style="background-color: #407a40" | jlaska
| style="color: #407a40" | #info jlaska to reach out to beland for guidance/ideas on how to document the process (or point to existing documentation) for how bugs are noted (common_bugs, release notes, install guide etc...) How to determine which bugs land in which place?
|| [[#t16:12:09|16:12]]
|- id="t16:12:51"
! style="background-color: #407a40" | jlaska
| style="color: #407a40" | another week and I've not kicked off this small task :(  I'll prioritize this for today and see if beland and awilliam have some thoughts as to whether there are any ideas for improvement here
|| [[#t16:12:51|16:12]]
|- id="t16:13:16"
! style="background-color: #407a40" | jlaska
| style="color: #407a40" | #action jlaska - reach out to beland for guidance/ideas on how to document the process for how bugs bubble through different release documents
|| [[#t16:13:16|16:13]]
|- id="t16:13:36"
! style="background-color: #407a40" | jlaska
| style="color: #407a40" | cwickert: perfect timeing
|| [[#t16:13:36|16:13]]
|- id="t16:13:37"
! style="background-color: #407a40" | jlaska
| style="color: #407a40" | timing
|| [[#t16:13:37|16:13]]
|- id="t16:13:53"
! style="background-color: #407a40" | jlaska
| style="color: #407a40" | cwickert: there's a previous meeting note to follow-up on ...
|| [[#t16:13:53|16:13]]
|- id="t16:13:57"
! style="background-color: #407a40" | jlaska
| style="color: #407a40" | #info cwickert to file an infrastruture ticket for the lxde mailing list
|| [[#t16:13:57|16:13]]
|- id="t16:14:09"
! style="background-color: #407a40" | jlaska
| style="color: #407a40" | did you have any updates you wanted to share?
|| [[#t16:14:09|16:14]]
|- id="t16:15:27"
! style="background-color: #407a40" | jlaska
| style="color: #407a40" | okay, we can come back to that later
|| [[#t16:15:27|16:15]]
|- id="t16:15:28"
! style="background-color: #8c4a4a" | cwickert
| style="color: #8c4a4a" | jlaska: can be closed
|| [[#t16:15:28|16:15]]
|- id="t16:15:36"
! style="background-color: #407a40" | jlaska
| style="color: #407a40" | cwickert: ah okay, thanks
|| [[#t16:15:36|16:15]]
|- id="t16:15:39"
! style="background-color: #8c4a4a" | cwickert
| style="color: #8c4a4a" | nirik fixed it
|| [[#t16:15:39|16:15]]
|- id="t16:15:44"
! style="background-color: #407a40" | jlaska
| style="color: #407a40" | what's the new list?
|| [[#t16:15:44|16:15]]
|- id="t16:15:59"
! style="background-color: #8c4a4a" | cwickert
| style="color: #8c4a4a" | lxde@lists.fpo
|| [[#t16:15:59|16:15]]
|- id="t16:16:03"
! style="background-color: #407a40" | jlaska
| style="color: #407a40" | #link https://admin.fedoraproject.org/mailman/listinfo/lxde
|| [[#t16:16:03|16:16]]
|- id="t16:16:08"
! style="background-color: #407a40" | jlaska
| style="color: #407a40" | nice, thanks
|| [[#t16:16:08|16:16]]
|- id="t16:16:21"
! style="background-color: #407a40" | jlaska
| style="color: #407a40" | alright, moving along ...
|| [[#t16:16:21|16:16]]
|- id="t16:16:23"
! style="background-color: #407a40" | jlaska
| style="color: #407a40" | #topic Security Policy Update
|| [[#t16:16:23|16:16]]
|- id="t16:16:32"
! style="background-color: #407a40" | jlaska
| style="color: #407a40" | On Friday's FESCO Meeting, Adam and Will responded to questions concerning building project-wide consensus around a security policy for Fedora (see FESCO ticket#297)
|| [[#t16:16:32|16:16]]
|- id="t16:16:56"
! style="background-color: #8c4a4a" | cwickert
| style="color: #8c4a4a" | .fesco 297
|| [[#t16:16:56|16:16]]
|- id="t16:16:57"
! style="background-color: #42427e" | zodbot
| style="color: #42427e" | cwickert: #297 (Please consider the idea of a security (privilege escalation) policy) - FESCo - Trac - https://fedorahosted.org/fesco/ticket/297
|| [[#t16:16:57|16:16]]
|- id="t16:17:02"
! style="background-color: #407a40" | jlaska
| style="color: #407a40" | adamw: can you talk to how things went, and what's next?
|| [[#t16:17:02|16:17]]
|- id="t16:17:09"
! style="background-color: #854685" | adamw
| style="color: #854685" | yeppers
|| [[#t16:17:09|16:17]]
|- id="t16:17:14"
! style="background-color: #854685" | adamw
| style="color: #854685" | short version: they kicked it back to us
|| [[#t16:17:14|16:17]]
|- id="t16:17:32"
! style="background-color: #854685" | adamw
| style="color: #854685" | with a promise that if we come up with some kind of draft policy, people who have a clue about security will be gracious enough to review it
|| [[#t16:17:32|16:17]]
|- id="t16:17:53"
! style="background-color: #854685" | adamw
| style="color: #854685" | so as far as FESCo is concerned the next thing that happens is I come back with a draft privilege escalation policy in hand
|| [[#t16:17:53|16:17]]
|- id="t16:18:13"
! style="background-color: #8c4a4a" | cwickert
| style="color: #8c4a4a" | fesco needs at least some kind of draft
|| [[#t16:18:13|16:18]]
|- id="t16:18:41"
! style="background-color: #407a40" | jlaska
| style="color: #407a40" | #info as far as FESCo is concerned the next thing that happens is I come back with a draft privilege escalation policy in hand
|| [[#t16:18:41|16:18]]
|- id="t16:19:16"
! style="background-color: #407a40" | jlaska
| style="color: #407a40" | adamw: is that something you can absorb for this release?
|| [[#t16:19:16|16:19]]
|- id="t16:19:37"
! style="background-color: #854685" | adamw
| style="color: #854685" | i can write up something quick 'n' dirty based on the famous blog post
|| [[#t16:19:37|16:19]]
|- id="t16:19:43"
! style="background-color: #854685" | adamw
| style="color: #854685" | i'll run it by you lot for review before taking it to fesco
|| [[#t16:19:43|16:19]]
|- id="t16:20:24"
! style="background-color: #407a40" | jlaska
| style="color: #407a40" | #action adamw to build on the famous spot security blog post and draft something quick'n'dirty for QA review
|| [[#t16:20:24|16:20]]
|- id="t16:20:47"
! style="background-color: #407a40" | jlaska
| style="color: #407a40" | adamw: what's this look like when it's all done to your liking?
|| [[#t16:20:47|16:20]]
|- id="t16:21:23"
! style="background-color: #407a40" | jlaska
| style="color: #407a40" | translation ... what does 'finished' look like for the security stuff?
|| [[#t16:21:23|16:21]]
|- id="t16:21:45"
! style="background-color: #488888" | Viking-Ice
| style="color: #488888" | dont we need to have a strong base security policy in place that spinners need to document ( including desktop/ all DE ) on what they differ from that policy ?
|| [[#t16:21:45|16:21]]
|- id="t16:21:57"
! style="background-color: #854685" | adamw
| style="color: #854685" | we have some kind of fesco-approved policy and some test cases for it
|| [[#t16:21:57|16:21]]
|- id="t16:22:07"
! style="background-color: #854685" | adamw
| style="color: #854685" | Viking-Ice: you'd've thought so. :)
|| [[#t16:22:07|16:22]]
|- id="t16:22:35"
! style="background-color: #407a40" | jlaska
| style="color: #407a40" | adamw: okay
|| [[#t16:22:35|16:22]]
|- id="t16:22:35"
! style="background-color: #488888" | Viking-Ice
| style="color: #488888" | It's the only thing that makes sense to do
|| [[#t16:22:35|16:22]]
|- id="t16:24:09"
! style="background-color: #407a40" | jlaska
| style="color: #407a40" | adamw: Viking-Ice: anything else to discuss, otherwise, let's move on
|| [[#t16:24:09|16:24]]
|- id="t16:24:27"
! style="background-color: #854685" | adamw
| style="color: #854685" | nope, i'm okay
|| [[#t16:24:27|16:24]]
|- id="t16:24:47"
! style="background-color: #407a40" | jlaska
| style="color: #407a40" | and kudos for the double contraction :)
|| [[#t16:24:47|16:24]]
|- id="t16:25:02"
! style="background-color: #407a40" | jlaska
| style="color: #407a40" | #topic fedora-release-rawhide
|| [[#t16:25:02|16:25]]
|- id="t16:25:10"
! style="background-color: #407a40" | jlaska
| style="color: #407a40" | #info wwoods noted that a new fedora-release-rawhide package may impact how we document opting into (and out of) testing rawhide via yum (see Releases/Rawhide#Testing_Rawhide)
|| [[#t16:25:10|16:25]]
|- id="t16:25:24"
! style="background-color: #407a40" | jlaska
| style="color: #407a40" | wwoods, got anything you'd like to add on this topic?
|| [[#t16:25:24|16:25]]
|- id="t16:27:10"
! style="background-color: #407a40" | jlaska
| style="color: #407a40" | take that as a no
|| [[#t16:27:10|16:27]]
|- id="t16:27:12"
! style="background-color: #818144" | wwoods
| style="color: #818144" | no, just that we'll need to talk to nirik et. al. to make sure we understand how to get on (and off!) rawhide
|| [[#t16:27:12|16:27]]
|- id="t16:27:24"
! style="background-color: #818144" | wwoods
| style="color: #818144" | and make sure that all the places in the wiki where we talk about that
|| [[#t16:27:24|16:27]]
|- id="t16:27:28"
! style="background-color: #818144" | wwoods
| style="color: #818144" | get updated to reflect the new state of the art
|| [[#t16:27:28|16:27]]
|- id="t16:27:37"
! style="background-color: #407a40" | jlaska
| style="color: #407a40" | ah, good
|| [[#t16:27:37|16:27]]
|- id="t16:27:40"
! style="background-color: #4b904b" | nirik
| style="color: #4b904b" | yeah, I was going to update the Rawhide page when it lands.
|| [[#t16:27:40|16:27]]
|- id="t16:27:43"
! style="background-color: #4b904b" | nirik
| style="color: #4b904b" | any help welcome.
|| [[#t16:27:43|16:27]]
|- id="t16:27:55"
! style="background-color: #407a40" | jlaska
| style="color: #407a40" | nirik: when you say rawhide wiki page ... is that [[Releases/Rawhide]] ?
|| [[#t16:27:55|16:27]]
|- id="t16:28:03"
! style="background-color: #4b904b" | nirik
| style="color: #4b904b" | yeah,
|| [[#t16:28:03|16:28]]
|- id="t16:28:24"
! style="background-color: #407a40" | jlaska
| style="color: #407a40" | I'm sure we can ask for help on test@l.fp.org following any instructions stubbed on the wiki
|| [[#t16:28:24|16:28]]
|- id="t16:28:26"
! style="background-color: #4b904b" | nirik
| style="color: #4b904b" | there really doesn't seem to be any/much other in the way of docs that talks to people about rawhide or how to move to it.
|| [[#t16:28:26|16:28]]
|- id="t16:28:33"
! style="background-color: #407a40" | jlaska
| style="color: #407a40" | esp since rawhide involvement will be heating up again
|| [[#t16:28:33|16:28]]
|- id="t16:29:28"
! style="background-color: #407a40" | jlaska
| style="color: #407a40" | #action nirik intends to update the [[Releases/Rawhide]] wiki page to reflect the changes (help appreciated)
|| [[#t16:29:28|16:29]]
|- id="t16:29:54"
! style="background-color: #407a40" | jlaska
| style="color: #407a40" | that's another area I think beland has some experience in as well, he's helped tweak that page in the past iirc
|| [[#t16:29:54|16:29]]
|- id="t16:30:02"
! style="background-color: #4b904b" | nirik
| style="color: #4b904b" | basically it will just be 'yum install fedora-rawhide-release' then edit /etc/yum.repos.d/fedora-rawhide.repo and set 'enabled=1'
|| [[#t16:30:02|16:30]]
|- id="t16:30:22"
! style="background-color: #407a40" | jlaska
| style="color: #407a40" | cool
|| [[#t16:30:22|16:30]]
|- id="t16:30:38"
! style="background-color: #407a40" | jlaska
| style="color: #407a40" | alrighty ... wwoods, nirik: thanks for the updates
|| [[#t16:30:38|16:30]]
|- id="t16:30:45"
! style="background-color: #407a40" | jlaska
| style="color: #407a40" | moving on ...
|| [[#t16:30:45|16:30]]
|- id="t16:30:57"
! style="background-color: #407a40" | jlaska
| style="color: #407a40" | #topic AutoQA Updates - rpmguard (kparal)
|| [[#t16:30:57|16:30]]
|- id="t16:31:11"
! style="background-color: #4d4d93" | kparal
| style="color: #4d4d93" | right
|| [[#t16:31:11|16:31]]
|- id="t16:31:33"
! style="background-color: #4d4d93" | kparal
| style="color: #4d4d93" | so last week me and james enabled sending the rpmguard results to autoqa-results ML
|| [[#t16:31:33|16:31]]
|- id="t16:31:40"
! style="background-color: #4d4d93" | kparal
| style="color: #4d4d93" | so you can have a look
|| [[#t16:31:40|16:31]]
|- id="t16:31:45"
! style="background-color: #4d4d93" | kparal
| style="color: #4d4d93" | together with rpmlint results
|| [[#t16:31:45|16:31]]
|- id="t16:32:13"
! style="background-color: #4d4d93" | kparal
| style="color: #4d4d93" | in the beginning we experienced some networking issues and many tests failed, but it seems to be working well now
|| [[#t16:32:13|16:32]]
|- id="t16:32:13"
! style="background-color: #407a40" | jlaska
| style="color: #407a40" | #info last week, enabled rpmguard test results to autoqa-results@l.fh.org
|| [[#t16:32:13|16:32]]
|- id="t16:32:27"
! style="background-color: #407a40" | jlaska
| style="color: #407a40" | kparal: I don't think we ever really figured those errors out, did we/
|| [[#t16:32:27|16:32]]
|- id="t16:32:28"
! style="background-color: #407a40" | jlaska
| style="color: #407a40" | ?
|| [[#t16:32:28|16:32]]
|- id="t16:32:33"
! style="background-color: #4d4d93" | kparal
| style="color: #4d4d93" | nope
|| [[#t16:32:33|16:32]]
|- id="t16:32:52"
! style="background-color: #407a40" | jlaska
| style="color: #407a40" | well, it works now :D
|| [[#t16:32:52|16:32]]
|- id="t16:33:09"
! style="background-color: #4d4d93" | kparal
| style="color: #4d4d93" | well, nothing much more about rpmguard, even won't be next week, since I'm doing RHCT
|| [[#t16:33:09|16:33]]
|- id="t16:33:21"
! style="background-color: #407a40" | jlaska
| style="color: #407a40" | Good luck on the RHCT front
|| [[#t16:33:21|16:33]]
|- id="t16:33:29"
! style="background-color: #4d4d93" | kparal
| style="color: #4d4d93" | but I also started some discussion in autoqa-devel about possible autoqa architecture
|| [[#t16:33:29|16:33]]
|- id="t16:33:49"
! style="background-color: #4d4d93" | kparal
| style="color: #4d4d93" | about creating server to receive all results and provide an API to access them
|| [[#t16:33:49|16:33]]
|- id="t16:33:55"
! style="background-color: #4d4d93" | kparal
| style="color: #4d4d93" | so all comments welcome
|| [[#t16:33:55|16:33]]
|- id="t16:34:06"
! style="background-color: #4d4d93" | kparal
| style="color: #4d4d93" | there are even pictures there! ;)
|| [[#t16:34:06|16:34]]
|- id="t16:34:15"
! style="background-color: #818144" | wwoods
| style="color: #818144" | heh!
|| [[#t16:34:15|16:34]]
|- id="t16:34:18"
! style="background-color: #407a40" | jlaska
| style="color: #407a40" | #info initiated discussion on autoqa-devel@ about refactoring capturing test results
|| [[#t16:34:18|16:34]]
|- id="t16:34:21"
! style="background-color: #407a40" | jlaska
| style="color: #407a40" | #link https://fedorahosted.org/pipermail/autoqa-devel/2010-January/000120.html
|| [[#t16:34:21|16:34]]
|- id="t16:34:27"
! style="background-color: #818144" | wwoods
| style="color: #818144" | definitely agree we need *some* better way to store results
|| [[#t16:34:27|16:34]]
|- id="t16:34:52"
! style="background-color: #4d4d93" | kparal
| style="color: #4d4d93" | I miss comments "no, you're completely wrong, it should be this way: ...."
|| [[#t16:34:52|16:34]]
|- id="t16:35:01"
! style="background-color: #407a40" | jlaska
| style="color: #407a40" | heh
|| [[#t16:35:01|16:35]]
|- id="t16:35:02"
! style="background-color: #4d4d93" | kparal
| style="color: #4d4d93" | anyone provide them, please :)
|| [[#t16:35:02|16:35]]
|- id="t16:35:24"
! style="background-color: #4d4d93" | kparal
| style="color: #4d4d93" | ok, that's about it from me
|| [[#t16:35:24|16:35]]
|- id="t16:36:08"
! style="background-color: #407a40" | jlaska
| style="color: #407a40" | kparal: does a larger discussion on the types of package update tests influence the discussion around how to store/present their test results?
|| [[#t16:36:08|16:36]]
|- id="t16:36:19"
! style="background-color: #407a40" | jlaska
| style="color: #407a40" | or is that something that can happen in parallel?
|| [[#t16:36:19|16:36]]
|- id="t16:36:59"
! style="background-color: #4d4d93" | kparal
| style="color: #4d4d93" | well, the package update tests will probably have very similar set of output information that should be stored in the results database
|| [[#t16:36:59|16:36]]
|- id="t16:37:31"
! style="background-color: #4d4d93" | kparal
| style="color: #4d4d93" | so we can do it simmultaneously I believe, we don't have to wait for it to finish
|| [[#t16:37:31|16:37]]
|- id="t16:37:46"
! style="background-color: #407a40" | jlaska
| style="color: #407a40" | okay, gotcha.  thanks
|| [[#t16:37:46|16:37]]
|- id="t16:38:11"
! style="background-color: #407a40" | jlaska
| style="color: #407a40" | #info next steps ... continue discussion around improving the mechanism for storing test results
|| [[#t16:38:11|16:38]]
|- id="t16:38:21"
! style="background-color: #407a40" | jlaska
| style="color: #407a40" | alright, moving on to ...
|| [[#t16:38:21|16:38]]
|- id="t16:38:32"
! style="background-color: #407a40" | jlaska
| style="color: #407a40" | #topic AutoQA Updates - deps/conflicts prevention (wwoods)
|| [[#t16:38:32|16:38]]
|- id="t16:38:59"
! style="background-color: #407a40" | jlaska
| style="color: #407a40" | okay, so the notes I have from last week are that work is underway w/ lmacken to figure out how to gather information for a post-bodhi-update trigger
|| [[#t16:38:59|16:38]]
|- id="t16:39:16"
! style="background-color: #818144" | wwoods
| style="color: #818144" | yeah, it turns out there's some API calls that alllmost do what we need
|| [[#t16:39:16|16:39]]
|- id="t16:39:57"
! style="background-color: #818144" | wwoods
| style="color: #818144" | lmacken said he was would work on adding the call we need in the next bodhi code update
|| [[#t16:39:57|16:39]]
|- id="t16:40:20"
! style="background-color: #818144" | wwoods
| style="color: #818144" | so in the meantime I started work on the depcheck test itself
|| [[#t16:40:20|16:40]]
|- id="t16:40:34"
! style="background-color: #818144" | wwoods
| style="color: #818144" | which is.. *close* to working, but not quite there. it's tricky business.
|| [[#t16:40:34|16:40]]
|- id="t16:41:05"
! style="background-color: #818144" | wwoods
| style="color: #818144" | the code is in git: http://git.fedorahosted.org/git/?p=autoqa.git;a=blob;f=tests/depcheck/depcheck
|| [[#t16:41:05|16:41]]
|- id="t16:41:21"
! style="background-color: #818144" | wwoods
| style="color: #818144" | hah whoops I forgot to add the GPLv2 boilerplate text
|| [[#t16:41:21|16:41]]
|- id="t16:41:28"
! style="background-color: #407a40" | jlaska
| style="color: #407a40" | if it involves prco sets, I think my brain will melt! :D
|| [[#t16:41:28|16:41]]
|- id="t16:42:01"
! style="background-color: #818144" | wwoods
| style="color: #818144" | yeah it's kind of complicated - involves PRCO data and package sacks and processing obsoletes and whatnot
|| [[#t16:42:01|16:42]]
|- id="t16:42:07"
! style="background-color: #818144" | wwoods
| style="color: #818144" | but not insurmountable
|| [[#t16:42:07|16:42]]
|- id="t16:42:15"
! style="background-color: #818144" | wwoods
| style="color: #818144" | just gonna take some time to get it right
|| [[#t16:42:15|16:42]]
|- id="t16:42:33"
! style="background-color: #407a40" | jlaska
| style="color: #407a40" | I like how it's another test designed to be run by hand first
|| [[#t16:42:33|16:42]]
|- id="t16:42:52"
! style="background-color: #407a40" | jlaska
| style="color: #407a40" | you and kparal are trailblazers there :)
|| [[#t16:42:52|16:42]]
|- id="t16:43:13"
! style="background-color: #818144" | wwoods
| style="color: #818144" | right, that's the design - you give it the name of a repo to check against and a set of new packages to test
|| [[#t16:43:13|16:43]]
|- id="t16:43:23"
! style="background-color: #407a40" | jlaska
| style="color: #407a40" | #info lmacken is working on adding a missing API call into the next bodhi code update
|| [[#t16:43:23|16:43]]
|- id="t16:43:51"
! style="background-color: #818144" | wwoods
| style="color: #818144" | it checks all the dropped provides, added requires, new conflicts, etc.
|| [[#t16:43:51|16:43]]
|- id="t16:43:53"
! style="background-color: #407a40" | jlaska
| style="color: #407a40" | #info wwoods started design on an initial depcheck test ... not 100% complete, but close
|| [[#t16:43:53|16:43]]
|- id="t16:43:59"
! style="background-color: #407a40" | jlaska
| style="color: #407a40" | #link http://git.fedorahosted.org/git/?p=autoqa.git;a=blob;f=tests/depcheck/depcheck
|| [[#t16:43:59|16:43]]
|- id="t16:44:22"
! style="background-color: #818144" | wwoods
| style="color: #818144" | and returns failure if there's any problems that would break repoclosure
|| [[#t16:44:22|16:44]]
|- id="t16:44:35"
! style="background-color: #818144" | wwoods
| style="color: #818144" | it typically takes only a few seconds to run, even when downloading the metadata
|| [[#t16:44:35|16:44]]
|- id="t16:44:44"
! style="background-color: #407a40" | jlaska
| style="color: #407a40" | that's not too bad at all
|| [[#t16:44:44|16:44]]
|- id="t16:44:56"
! style="background-color: #818144" | wwoods
| style="color: #818144" | which means we can very likely run it for every new rawhide package build / bodhi update
|| [[#t16:44:56|16:44]]
|- id="t16:45:10"
! style="background-color: #818144" | wwoods
| style="color: #818144" | without too much trouble
|| [[#t16:45:10|16:45]]
|- id="t16:45:49"
! style="background-color: #97974f" | abadger1999
| style="color: #97974f" | nim-nim: ping
|| [[#t16:45:49|16:45]]
|- id="t16:46:16"
! style="background-color: #818144" | wwoods
| style="color: #818144" | so that's depcheck.
|| [[#t16:46:16|16:46]]
|- id="t16:46:41"
! style="background-color: #407a40" | jlaska
| style="color: #407a40" | sweet, anything else on the depcheck/conflicts front you want to note?
|| [[#t16:46:41|16:46]]
|- id="t16:47:14"
! style="background-color: #407a40" | jlaska
| style="color: #407a40" | I think you said so already, not sure if there were other non-depcheck items to discuss
|| [[#t16:47:14|16:47]]
|- id="t16:47:57"
! style="background-color: #407a40" | jlaska
| style="color: #407a40" | I'm going to move on just to keep things going ... but we can come back if needed
|| [[#t16:47:57|16:47]]
|- id="t16:48:05"
! style="background-color: #818144" | wwoods
| style="color: #818144" | nothing comes to mind
|| [[#t16:48:05|16:48]]
|- id="t16:48:13"
! style="background-color: #407a40" | jlaska
| style="color: #407a40" | wwoods: okay, thanks for the updates!
|| [[#t16:48:13|16:48]]
|- id="t16:48:24"
! style="background-color: #407a40" | jlaska
| style="color: #407a40" | #topic AutoQA Updates - install automation (lili/rhe)
|| [[#t16:48:24|16:48]]
|- id="t16:49:04"
! style="background-color: #407a40" | jlaska
| style="color: #407a40" | no big updates to share just yet ... I discussed with lili last week and he is refining a sample python script that automates a virt DVD install
|| [[#t16:49:04|16:49]]
|- id="t16:49:47"
! style="background-color: #407a40" | jlaska
| style="color: #407a40" | the plan is to get that working, refine it per the requirements discussed in previous meeting around what inputs an automated virt install test would need to accept
|| [[#t16:49:47|16:49]]
|- id="t16:50:30"
! style="background-color: #407a40" | jlaska
| style="color: #407a40" | wwoods: kparal: while lili is refining his test, do you two have any thoughts on a good way to share his test development progress?
|| [[#t16:50:30|16:50]]
|- id="t16:50:56"
! style="background-color: #407a40" | jlaska
| style="color: #407a40" | meaning, should I ask lili to contribute the script into git ... or should we continue working it outside of git until it's at a stable point?
|| [[#t16:50:56|16:50]]
|- id="t16:51:35"
! style="background-color: #4d4d93" | kparal
| style="color: #4d4d93" | I think it can surely be in git right now, that's what we have VCS for
|| [[#t16:51:35|16:51]]
|- id="t16:51:52"
! style="background-color: #407a40" | jlaska
| style="color: #407a40" | that was my thought, but wasn't sure how you two felt about it
|| [[#t16:51:52|16:51]]
|- id="t16:51:55"
! style="background-color: #4d4d93" | kparal
| style="color: #4d4d93" | it can be a separate branch
|| [[#t16:51:55|16:51]]
|- id="t16:51:59"
! style="background-color: #4d4d93" | kparal
| style="color: #4d4d93" | and merged later
|| [[#t16:51:59|16:51]]
|- id="t16:52:11"
! style="background-color: #818144" | wwoods
| style="color: #818144" | yeah - does he already have commit access?
|| [[#t16:52:11|16:52]]
|- id="t16:52:30"
! style="background-color: #407a40" | jlaska
| style="color: #407a40" | wwoods: I don't believe he does yet.  He's still new to git and python
|| [[#t16:52:30|16:52]]
|- id="t16:52:37"
! style="background-color: #818144" | wwoods
| style="color: #818144" | branches are cheap and (fairly) easy in git
|| [[#t16:52:37|16:52]]
|- id="t16:53:05"
! style="background-color: #818144" | wwoods
| style="color: #818144" | but if he's more comfortable just working on a local git repo until he's satisfied
|| [[#t16:53:05|16:53]]
|- id="t16:53:09"
! style="background-color: #818144" | wwoods
| style="color: #818144" | and sending patches to the list for review
|| [[#t16:53:09|16:53]]
|- id="t16:53:19"
! style="background-color: #818144" | wwoods
| style="color: #818144" | that works too
|| [[#t16:53:19|16:53]]
|- id="t16:53:36"
! style="background-color: #407a40" | jlaska
| style="color: #407a40" | wwoods: kparal okay thanks gents ... I'll be sure to pass that along
|| [[#t16:53:36|16:53]]
|- id="t16:53:45"
! style="background-color: #407a40" | jlaska
| style="color: #407a40" | and lili can choose which route he is more comfortable with
|| [[#t16:53:45|16:53]]
|- id="t16:54:02"
! style="background-color: #407a40" | jlaska
| style="color: #407a40" | #info next steps - continue refining virt dvd install test
|| [[#t16:54:02|16:54]]
|- id="t16:54:21"
! style="background-color: #407a40" | jlaska
| style="color: #407a40" | #info next steps - look for ways to contribute tests back into git (private checkout, or public branch)
|| [[#t16:54:21|16:54]]
|- id="t16:54:28"
! style="background-color: #407a40" | jlaska
| style="color: #407a40" | okay, next up ...
|| [[#t16:54:28|16:54]]
|- id="t16:54:35"
! style="background-color: #407a40" | jlaska
| style="color: #407a40" | #topic AutoQA Updates - packaging/deployment (jlaska)
|| [[#t16:54:35|16:54]]
|- id="t16:54:49"
! style="background-color: #407a40" | jlaska
| style="color: #407a40" | my two tasks last week were
|| [[#t16:54:49|16:54]]
|- id="t16:55:21"
! style="background-color: #407a40" | jlaska
| style="color: #407a40" | #info respond to package review feedback for autotest-client (bug#548522)
|| [[#t16:55:21|16:55]]
|- id="t16:55:22"
! style="background-color: #9b519b" | buggbot
| style="color: #9b519b" | Bug https://bugzilla.redhat.com/bugzilla/show_bug.cgi?id=548522 medium, medium, ---, nobody, NEW, Review Request: autotest-client - Autotest is a framework for fully automated testing
|| [[#t16:55:22|16:55]]
|- id="t16:55:43"
! style="background-color: #407a40" | jlaska
| style="color: #407a40" | #info scope out packaging work required for building the autotest BuildRequires gwt (and all of it's bundled deps)
|| [[#t16:55:43|16:55]]
|- id="t16:56:04"
! style="background-color: #407a40" | jlaska
| style="color: #407a40" | I've got some re-work I'll be attempting with permissions on the autotest-client package
|| [[#t16:56:04|16:56]]
|- id="t16:56:11"
! style="background-color: #407a40" | jlaska
| style="color: #407a40" | should have that in this week
|| [[#t16:56:11|16:56]]
|- id="t16:56:34"
! style="background-color: #407a40" | jlaska
| style="color: #407a40" | I'm getting a better handle on the effort required to package gwt (and deps)
|| [[#t16:56:34|16:56]]
|- id="t16:56:37"
! style="background-color: #407a40" | jlaska
| style="color: #407a40" | #link [[User:Jlaska/gwt]]
|| [[#t16:56:37|16:56]]
|- id="t16:57:02"
! style="background-color: #407a40" | jlaska
| style="color: #407a40" | #info I'll be spending time this week to identify action plans for each of the items listed under 'status uncertain'
|| [[#t16:57:02|16:57]]
|- id="t16:57:44"
! style="background-color: #407a40" | jlaska
| style="color: #407a40" | once autotest-client is blessed ... I'll file a review request for autoqa
|| [[#t16:57:44|16:57]]
|- id="t16:57:58"
! style="background-color: #407a40" | jlaska
| style="color: #407a40" | after that ... we should have all we need to deploy the results front-ends in Fedora infrastructure
|| [[#t16:57:58|16:57]]
|- id="t16:58:06"
! style="background-color: #407a40" | jlaska
| style="color: #407a40" | That's all I have on the packaging/deploy front
|| [[#t16:58:06|16:58]]
|- id="t16:58:07"
! style="background-color: #818144" | wwoods
| style="color: #818144" | yaaay
|| [[#t16:58:07|16:58]]
|- id="t16:58:40"
! style="background-color: #407a40" | jlaska
| style="color: #407a40" | okay, so let's open things up ...
|| [[#t16:58:40|16:58]]
|- id="t16:58:43"
! style="background-color: #407a40" | jlaska
| style="color: #407a40" | #topic Open discussion - &lt;Your topic here&gt;
|| [[#t16:58:43|16:58]]
|- id="t16:58:54"
! style="background-color: #407a40" | jlaska
| style="color: #407a40" | anything folks would like to discuss before closing out the meeting?
|| [[#t16:58:54|16:58]]
|- id="t16:59:40"
! style="background-color: #818144" | wwoods
| style="color: #818144" | when are we scheduled to get rawhide install images?
|| [[#t16:59:40|16:59]]
|- id="t16:59:46"
! style="background-color: #407a40" | jlaska
| style="color: #407a40" | wwoods: aha, thanks for bringing that up!
|| [[#t16:59:46|16:59]]
|- id="t17:00:05"
! style="background-color: #407a40" | jlaska
| style="color: #407a40" | so this Thursday (1/21) is a scheduled install image drop to run the rawhide acceptance test plan
|| [[#t17:00:05|17:00]]
|- id="t17:00:19"
! style="background-color: #407a40" | jlaska
| style="color: #407a40" | #topic open discussion - When is next rawhide install image drop?
|| [[#t17:00:19|17:00]]
|- id="t17:00:26"
! style="background-color: #407a40" | jlaska
| style="color: #407a40" | #info so this Thursday (1/21) is a scheduled install image drop to run the rawhide acceptance test plan
|| [[#t17:00:26|17:00]]
|- id="t17:00:42"
! style="background-color: #407a40" | jlaska
| style="color: #407a40" | #link http://poelstra.fedorapeople.org/schedules/f-12/f-12-quality-tasks.html
|| [[#t17:00:42|17:00]]
|- id="t17:01:04"
! style="background-color: #407a40" | jlaska
| style="color: #407a40" | I sent an email out to dcantrell and jkeating for guidance on indentifing who is doing what for this drop
|| [[#t17:01:04|17:01]]
|- id="t17:01:12"
! style="background-color: #407a40" | jlaska
| style="color: #407a40" | and filed a rel-eng ticket just to track creating the images
|| [[#t17:01:12|17:01]]
|- id="t17:01:13"
| colspan="2" | * jlaska finds link
|| [[#t17:01:13|17:01]]
|- id="t17:01:26"
! style="background-color: #407a40" | jlaska
| style="color: #407a40" | #info https://fedorahosted.org/rel-eng/ticket/3277
|| [[#t17:01:26|17:01]]
|- id="t17:02:05"
! style="background-color: #407a40" | jlaska
| style="color: #407a40" | so we ran through rats_install (finished up last monday) ... and this time should include some bug fixes for issues identified
|| [[#t17:02:05|17:02]]
|- id="t17:03:52"
! style="background-color: #407a40" | jlaska
| style="color: #407a40" | Rats test results against anaconda-13.16 (using http://clumens.fedorapeople.org/updates.img) - http://jlaska.fedorapeople.org/rats.png
|| [[#t17:03:52|17:03]]
|- id="t17:03:59"
! style="background-color: #407a40" | jlaska
| style="color: #407a40" | #topic open discussion - &lt;your topic here&gt;
|| [[#t17:03:59|17:03]]
|- id="t17:04:12"
! style="background-color: #407a40" | jlaska
| style="color: #407a40" | wwoods thanks for reminding me! :D
|| [[#t17:04:12|17:04]]
|- id="t17:04:19"
! style="background-color: #4d4d93" | kparal
| style="color: #4d4d93" | all nicely green
|| [[#t17:04:19|17:04]]
|- id="t17:04:35"
! style="background-color: #407a40" | jlaska
| style="color: #407a40" | an i386 compose wasn't created ... so there were no results
|| [[#t17:04:35|17:04]]
|- id="t17:04:56"
! style="background-color: #539e9e" | RodrigoPadula
| style="color: #539e9e" | hi
|| [[#t17:04:56|17:04]]
|- id="t17:05:23"
! style="background-color: #407a40" | jlaska
| style="color: #407a40" | any other issues to discuss?  Otherwise, let's close things out and get back to work
|| [[#t17:05:23|17:05]]
|- id="t17:05:34"
! style="background-color: #407a40" | jlaska
| style="color: #407a40" | RodrigoPadula: hi
|| [[#t17:05:34|17:05]]
|- id="t17:05:53"
! style="background-color: #539e9e" | RodrigoPadula
| style="color: #539e9e" | famsco meeting ?
|| [[#t17:05:53|17:05]]
|- id="t17:06:05"
! style="background-color: #407a40" | jlaska
| style="color: #407a40" | RodrigoPadula: one moment, wrapping up fedora-qa meeting
|| [[#t17:06:05|17:06]]
|- id="t17:06:11"
! style="background-color: #407a40" | jlaska
| style="color: #407a40" | okay gang ... thanks for your attention
|| [[#t17:06:11|17:06]]
|- id="t17:06:12"
! style="background-color: #539e9e" | RodrigoPadula
| style="color: #539e9e" | ops.. soryy
|| [[#t17:06:12|17:06]]
|- id="t17:06:21"
! style="background-color: #407a40" | jlaska
| style="color: #407a40" | as usual, I'll follow-up to the list with minutes
|| [[#t17:06:21|17:06]]
|- id="t17:06:27"
! style="background-color: #407a40" | jlaska
| style="color: #407a40" | #endmeeting
|| [[#t17:06:27|17:06]]
|}
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:00, 18 September 2016

Attendees

People present (lines said)

  • jlaska (141)
  • wwoods (30)
  • adamw (22)
  • kparal (21)
  • Viking-Ice (8)
  • nirik (5)
  • cwickert (5)
  • zodbot (4)
  • RodrigoPadula (3)
  • buggbot (1)
  • abadger1999 (1)
  • tk009 (1)

Regrets:

Agenda

Previous meeting follow-up

  • maxamillion bring back conversation about Xfce 4.8 updato on xfce@lists.fp.o and inform about conclusion
    • No updates, save for next week
  • Viking-Ice write lxde tests and find a date for the test day
    • Created ticket#46, agreed to move future discussion to the ticket
  • adamw and rhe to discuss ways to add install testing as a QA activity
    • Hurry created a new install test home at QA/Installation_Test. The idea is to have that big explanatory page, and a bit in the 'joining' page which would link to it
    • Adamw would look for possibilities to propose integrating the new home with the existing QA:Fedora_13_Install_Test_Plan.
  • jlaska to reach out to beland for guidance/ideas on how to document the process (or point to existing documentation) for how bugs are noted (common_bugs, release notes, install guide etc...) How to determine which bugs land in which place?
    • Yuck, no traction on this task, jlaska will get things rolling with this task.

Security Policy Update

On Friday's FESCO Meeting, Adam and Will responded to questions concerning building project-wide consensus around a security policy for Fedora (see FESCO ticket#297).

Adam informed the group that FESCO kicked it back to the QA team with a promise that if we come up with some kind of draft policy, people who have a clue about security will be gracious enough to review it. So as far as FESCo is concerned the next thing that happens is I come back with a draft privilege escalation policy in hand.

Adam noted he would draft something quick'n'dirty using Spot's famous blog post as a foundation, then seek QA team review before approaching FESCO.


fedora-release-rawhide

wwoods noted that a new fedora-release-rawhide package may impact how we document opting into (and out of) testing rawhide via yum (see Releases/Rawhide#Testing_Rawhide).

Nirik offered updates to Releases/Rawhide to help explain how to activate the rawhide repos. Jlaska suggested that testers on test@l.fp.org would no doubt be able to help review the recommendations.

AutoQA project update

rpmguard package comparison

Last week

  • the small task ahead is to start sending output to autoqa-results and address any issues that surface

This week

Deps/conflicts prevention

Last week

  • working w/ lmacken to figure out how to gather information for a post-bodhi-update trigger

This week

  • lmacken working an API change into the next release of bodhi
  • A close to working depsolv test case (see [1]) is available. Further clean-up needed.


install automation

Last week

  • User:lili and User:rhe have started exploring test design using the rats_install/install.py test as a starting point.

This week

  • Continue working towards a single python test that will automate a DVD install
  • Publish test code using either a public git branch, code on a people page, just a local git checkout

packaging/deployment

Last week

  • Looking for autotest-client help with reviewing the package
  • Scope out effort required to package autotest, gwt (BuildRequires) and all of it's BuildRequires - see User:Jlaska/gwt

This week

  • Continue to harden the next-steps for JARs in the uncertain (see User:Jlaska/gwt#Status_uncertain)
  • Attempt to rework some directory permissions as requested in autotest-client review

Current status on packaging:

Open discussion - <Your topic here>

When is the next F-13 milestone?

Wwoods asked when the next scheduled rawhide install image drop was (see #Upcoming QA events below (2010-01-21 - Pre-Alpha Rawhide Acceptance Test Plan #1). See rel-eng ticket#3277 for details.

Jlaska also noted that anaconda-13.16 (plus http://clumens.fedorapeople.org/updates.img) had recently gone through an automated rats_install test run. For results, see http://jlaska.fedorapeople.org/rats.png.

Upcoming QA events

  • 2010-01-21 - Pre-Alpha Rawhide Acceptance Test Plan #1
  • 2010-01-28 - Pre-Alpha Rawhide Acceptance Test Plan #2
  • 2010-02-04 - Pre-Alpha Rawhide Acceptance Test Plan #3
  • 2010-02-05 - Alpha Blocker Meeting (F13Alpha) #1
  • 2010-02-11 - Test Alpha 'Test Compose' (boot media testing)
  • 2010-02-12 - Alpha Blocker Meeting (F13Alpha) #2

Action items

  • jlaska - reach out to beland for guidance/ideas on how to document the process for how bugs bubble through different release documents
  • adamw to build on the famous spot security blog post and draft something quick'n'dirty for QA review
  • nirik intends to update the Releases/Rawhide wiki page to reflect the changes (help appreciated)


IRC transcript

jlaska #startmeeting Fedora QA Meeting 16:00
zodbot Meeting started Mon Jan 18 16:00:41 2010 UTC. The chair is jlaska. Information about MeetBot at http://wiki.debian.org/MeetBot. 16:00
zodbot Useful Commands: #action #agreed #halp #info #idea #link #topic. 16:00
jlaska #meetingname qa 16:00
zodbot The meeting name has been set to 'qa' 16:00
wwoods meeting powers go! 16:00
jlaska queue the robot sounds 16:01
jlaska #topic gathering 16:01
* kparal is here 16:01
jlaska wwoods: kparal: howdy 16:01
jlaska anyone else primed and ready for another edition of the QA meeting? 16:01
* tk009 16:01
adamw morning 16:01
jlaska tk009: adamw hi there 16:02
adamw sorry, /me is tweaking with stuff again 16:02
jlaska not sure if Viking-Ice or maxamillion are around too 16:02
* Viking-Ice here 16:02
jlaska Viking-Ice: oh good, welcome! 16:02
jlaska okay, I put a ping out to Adam Miller, but I think he might be busy at the moment 16:03
jlaska so let's get started ... 16:04
jlaska Working off the agenda here http://lists.fedoraproject.org/pipermail/test/2010-January/088008.html 16:04
jlaska #topic Previous meeting follow-up 16:04
jlaska #info maxamillion bring back conversation about Xfce 4.8 updato on xfce@lists.fp.o and inform about conclusion 16:04
jlaska I don't have any updates on this, anyone else? I'll leave it on the list until we get a chance to sync up with Adam M. 16:05
jlaska moving on 16:05
jlaska #info Viking-Ice write lxde tests and find a date for the test day 16:05
jlaska Viking-Ice: any updates on definingsome LXDE tests for a possible test day? 16:06
Viking-Ice Not really looking at it.. 16:06
Viking-Ice Created ticket in QA 16:06
Viking-Ice [Fedora QA] #46: Write Test cases for LXDE components. 16:06
Viking-Ice To keep track will update there as thing progress.. 16:06
jlaska okay thanks, lemme add that to the 'draft' test day schedule too (Talk:QA/Fedora_13_test_days) 16:07
Viking-Ice Ok 16:07
jlaska Viking-Ice: thanks for the update 16:07
jlaska next up .... 16:08
jlaska #info adamw and rhe to discuss ways to add install testing as a QA activity 16:08
jlaska hopefully rhe is sleeping, adamw ... sounds like you two made some progress? 16:08
adamw well, rhe's not around, so i'll do it 16:08
adamw rui did, i was too busy playing around with shiny shiny toys. =) 16:08
adamw rui drafted an installation testing page: 16:09
adamw #link lxde fedora list 16:09
adamw grr! 16:09
adamw #link QA/Installation_Test 16:09
adamw stupid paste buffers 16:09
adamw the idea is to have that big explanatory page, and a bit in the 'joining' page which would link to it 16:09
adamw I wondered if the big page should merge with QA:Fedora_12_Install_Test_Plan in some way; rui thinks not at present 16:10
jlaska #info the idea is to have that big explanatory page, and a bit in the 'joining' page which would link to it 16:10
adamw i'm going to take some time today to have a look at both pages and see whether I should disagree some more =), do a bit of a proofread, and come up with a draft for the bit to be added to the Joining page 16:10
jlaska adamw: I can see the drive to avoid duplicate content. Hopefully we can do that while preserving the concept of a 'test plan' 16:11
adamw ayup 16:11
jlaska rather ... while addressing the same issues that the test plan addresses 16:11
jlaska whether it takes a different form or not 16:11
jlaska cool, nice update 16:11
jlaska next up ... 16:12
jlaska #info jlaska to reach out to beland for guidance/ideas on how to document the process (or point to existing documentation) for how bugs are noted (common_bugs, release notes, install guide etc...) How to determine which bugs land in which place? 16:12
jlaska another week and I've not kicked off this small task :( I'll prioritize this for today and see if beland and awilliam have some thoughts as to whether there are any ideas for improvement here 16:12
jlaska #action jlaska - reach out to beland for guidance/ideas on how to document the process for how bugs bubble through different release documents 16:13
jlaska cwickert: perfect timeing 16:13
jlaska timing 16:13
jlaska cwickert: there's a previous meeting note to follow-up on ... 16:13
jlaska #info cwickert to file an infrastruture ticket for the lxde mailing list 16:13
jlaska did you have any updates you wanted to share? 16:14
jlaska okay, we can come back to that later 16:15
cwickert jlaska: can be closed 16:15
jlaska cwickert: ah okay, thanks 16:15
cwickert nirik fixed it 16:15
jlaska what's the new list? 16:15
cwickert lxde@lists.fpo 16:15
jlaska #link https://admin.fedoraproject.org/mailman/listinfo/lxde 16:16
jlaska nice, thanks 16:16
jlaska alright, moving along ... 16:16
jlaska #topic Security Policy Update 16:16
jlaska On Friday's FESCO Meeting, Adam and Will responded to questions concerning building project-wide consensus around a security policy for Fedora (see FESCO ticket#297) 16:16
cwickert .fesco 297 16:16
zodbot cwickert: #297 (Please consider the idea of a security (privilege escalation) policy) - FESCo - Trac - https://fedorahosted.org/fesco/ticket/297 16:16
jlaska adamw: can you talk to how things went, and what's next? 16:17
adamw yeppers 16:17
adamw short version: they kicked it back to us 16:17
adamw with a promise that if we come up with some kind of draft policy, people who have a clue about security will be gracious enough to review it 16:17
adamw so as far as FESCo is concerned the next thing that happens is I come back with a draft privilege escalation policy in hand 16:17
cwickert fesco needs at least some kind of draft 16:18
jlaska #info as far as FESCo is concerned the next thing that happens is I come back with a draft privilege escalation policy in hand 16:18
jlaska adamw: is that something you can absorb for this release? 16:19
adamw i can write up something quick 'n' dirty based on the famous blog post 16:19
adamw i'll run it by you lot for review before taking it to fesco 16:19
jlaska #action adamw to build on the famous spot security blog post and draft something quick'n'dirty for QA review 16:20
jlaska adamw: what's this look like when it's all done to your liking? 16:20
jlaska translation ... what does 'finished' look like for the security stuff? 16:21
Viking-Ice dont we need to have a strong base security policy in place that spinners need to document ( including desktop/ all DE ) on what they differ from that policy ? 16:21
adamw we have some kind of fesco-approved policy and some test cases for it 16:21
adamw Viking-Ice: you'd've thought so. :) 16:22
jlaska adamw: okay 16:22
Viking-Ice It's the only thing that makes sense to do 16:22
jlaska adamw: Viking-Ice: anything else to discuss, otherwise, let's move on 16:24
adamw nope, i'm okay 16:24
jlaska and kudos for the double contraction :) 16:24
jlaska #topic fedora-release-rawhide 16:25
jlaska #info wwoods noted that a new fedora-release-rawhide package may impact how we document opting into (and out of) testing rawhide via yum (see Releases/Rawhide#Testing_Rawhide) 16:25
jlaska wwoods, got anything you'd like to add on this topic? 16:25
jlaska take that as a no 16:27
wwoods no, just that we'll need to talk to nirik et. al. to make sure we understand how to get on (and off!) rawhide 16:27
wwoods and make sure that all the places in the wiki where we talk about that 16:27
wwoods get updated to reflect the new state of the art 16:27
jlaska ah, good 16:27
nirik yeah, I was going to update the Rawhide page when it lands. 16:27
nirik any help welcome. 16:27
jlaska nirik: when you say rawhide wiki page ... is that Releases/Rawhide ? 16:27
nirik yeah, 16:28
jlaska I'm sure we can ask for help on test@l.fp.org following any instructions stubbed on the wiki 16:28
nirik there really doesn't seem to be any/much other in the way of docs that talks to people about rawhide or how to move to it. 16:28
jlaska esp since rawhide involvement will be heating up again 16:28
jlaska #action nirik intends to update the Releases/Rawhide wiki page to reflect the changes (help appreciated) 16:29
jlaska that's another area I think beland has some experience in as well, he's helped tweak that page in the past iirc 16:29
nirik basically it will just be 'yum install fedora-rawhide-release' then edit /etc/yum.repos.d/fedora-rawhide.repo and set 'enabled=1' 16:30
jlaska cool 16:30
jlaska alrighty ... wwoods, nirik: thanks for the updates 16:30
jlaska moving on ... 16:30
jlaska #topic AutoQA Updates - rpmguard (kparal) 16:30
kparal right 16:31
kparal so last week me and james enabled sending the rpmguard results to autoqa-results ML 16:31
kparal so you can have a look 16:31
kparal together with rpmlint results 16:31
kparal in the beginning we experienced some networking issues and many tests failed, but it seems to be working well now 16:32
jlaska #info last week, enabled rpmguard test results to autoqa-results@l.fh.org 16:32
jlaska kparal: I don't think we ever really figured those errors out, did we/ 16:32
jlaska ? 16:32
kparal nope 16:32
jlaska well, it works now :D 16:32
kparal well, nothing much more about rpmguard, even won't be next week, since I'm doing RHCT 16:33
jlaska Good luck on the RHCT front 16:33
kparal but I also started some discussion in autoqa-devel about possible autoqa architecture 16:33
kparal about creating server to receive all results and provide an API to access them 16:33
kparal so all comments welcome 16:33
kparal there are even pictures there! ;) 16:34
wwoods heh! 16:34
jlaska #info initiated discussion on autoqa-devel@ about refactoring capturing test results 16:34
jlaska #link https://fedorahosted.org/pipermail/autoqa-devel/2010-January/000120.html 16:34
wwoods definitely agree we need *some* better way to store results 16:34
kparal I miss comments "no, you're completely wrong, it should be this way: ...." 16:34
jlaska heh 16:35
kparal anyone provide them, please :) 16:35
kparal ok, that's about it from me 16:35
jlaska kparal: does a larger discussion on the types of package update tests influence the discussion around how to store/present their test results? 16:36
jlaska or is that something that can happen in parallel? 16:36
kparal well, the package update tests will probably have very similar set of output information that should be stored in the results database 16:36
kparal so we can do it simmultaneously I believe, we don't have to wait for it to finish 16:37
jlaska okay, gotcha. thanks 16:37
jlaska #info next steps ... continue discussion around improving the mechanism for storing test results 16:38
jlaska alright, moving on to ... 16:38
jlaska #topic AutoQA Updates - deps/conflicts prevention (wwoods) 16:38
jlaska okay, so the notes I have from last week are that work is underway w/ lmacken to figure out how to gather information for a post-bodhi-update trigger 16:38
wwoods yeah, it turns out there's some API calls that alllmost do what we need 16:39
wwoods lmacken said he was would work on adding the call we need in the next bodhi code update 16:39
wwoods so in the meantime I started work on the depcheck test itself 16:40
wwoods which is.. *close* to working, but not quite there. it's tricky business. 16:40
wwoods the code is in git: http://git.fedorahosted.org/git/?p=autoqa.git;a=blob;f=tests/depcheck/depcheck 16:41
wwoods hah whoops I forgot to add the GPLv2 boilerplate text 16:41
jlaska if it involves prco sets, I think my brain will melt! :D 16:41
wwoods yeah it's kind of complicated - involves PRCO data and package sacks and processing obsoletes and whatnot 16:42
wwoods but not insurmountable 16:42
wwoods just gonna take some time to get it right 16:42
jlaska I like how it's another test designed to be run by hand first 16:42
jlaska you and kparal are trailblazers there :) 16:42
wwoods right, that's the design - you give it the name of a repo to check against and a set of new packages to test 16:43
jlaska #info lmacken is working on adding a missing API call into the next bodhi code update 16:43
wwoods it checks all the dropped provides, added requires, new conflicts, etc. 16:43
jlaska #info wwoods started design on an initial depcheck test ... not 100% complete, but close 16:43
jlaska #link http://git.fedorahosted.org/git/?p=autoqa.git;a=blob;f=tests/depcheck/depcheck 16:43
wwoods and returns failure if there's any problems that would break repoclosure 16:44
wwoods it typically takes only a few seconds to run, even when downloading the metadata 16:44
jlaska that's not too bad at all 16:44
wwoods which means we can very likely run it for every new rawhide package build / bodhi update 16:44
wwoods without too much trouble 16:45
abadger1999 nim-nim: ping 16:45
wwoods so that's depcheck. 16:46
jlaska sweet, anything else on the depcheck/conflicts front you want to note? 16:46
jlaska I think you said so already, not sure if there were other non-depcheck items to discuss 16:47
jlaska I'm going to move on just to keep things going ... but we can come back if needed 16:47
wwoods nothing comes to mind 16:48
jlaska wwoods: okay, thanks for the updates! 16:48
jlaska #topic AutoQA Updates - install automation (lili/rhe) 16:48
jlaska no big updates to share just yet ... I discussed with lili last week and he is refining a sample python script that automates a virt DVD install 16:49
jlaska the plan is to get that working, refine it per the requirements discussed in previous meeting around what inputs an automated virt install test would need to accept 16:49
jlaska wwoods: kparal: while lili is refining his test, do you two have any thoughts on a good way to share his test development progress? 16:50
jlaska meaning, should I ask lili to contribute the script into git ... or should we continue working it outside of git until it's at a stable point? 16:50
kparal I think it can surely be in git right now, that's what we have VCS for 16:51
jlaska that was my thought, but wasn't sure how you two felt about it 16:51
kparal it can be a separate branch 16:51
kparal and merged later 16:51
wwoods yeah - does he already have commit access? 16:52
jlaska wwoods: I don't believe he does yet. He's still new to git and python 16:52
wwoods branches are cheap and (fairly) easy in git 16:52
wwoods but if he's more comfortable just working on a local git repo until he's satisfied 16:53
wwoods and sending patches to the list for review 16:53
wwoods that works too 16:53
jlaska wwoods: kparal okay thanks gents ... I'll be sure to pass that along 16:53
jlaska and lili can choose which route he is more comfortable with 16:53
jlaska #info next steps - continue refining virt dvd install test 16:54
jlaska #info next steps - look for ways to contribute tests back into git (private checkout, or public branch) 16:54
jlaska okay, next up ... 16:54
jlaska #topic AutoQA Updates - packaging/deployment (jlaska) 16:54
jlaska my two tasks last week were 16:54
jlaska #info respond to package review feedback for autotest-client (bug#548522) 16:55
buggbot Bug https://bugzilla.redhat.com/bugzilla/show_bug.cgi?id=548522 medium, medium, ---, nobody, NEW, Review Request: autotest-client - Autotest is a framework for fully automated testing 16:55
jlaska #info scope out packaging work required for building the autotest BuildRequires gwt (and all of it's bundled deps) 16:55
jlaska I've got some re-work I'll be attempting with permissions on the autotest-client package 16:56
jlaska should have that in this week 16:56
jlaska I'm getting a better handle on the effort required to package gwt (and deps) 16:56
jlaska #link User:Jlaska/gwt 16:56
jlaska #info I'll be spending time this week to identify action plans for each of the items listed under 'status uncertain' 16:57
jlaska once autotest-client is blessed ... I'll file a review request for autoqa 16:57
jlaska after that ... we should have all we need to deploy the results front-ends in Fedora infrastructure 16:57
jlaska That's all I have on the packaging/deploy front 16:58
wwoods yaaay 16:58
jlaska okay, so let's open things up ... 16:58
jlaska #topic Open discussion - <Your topic here> 16:58
jlaska anything folks would like to discuss before closing out the meeting? 16:58
wwoods when are we scheduled to get rawhide install images? 16:59
jlaska wwoods: aha, thanks for bringing that up! 16:59
jlaska so this Thursday (1/21) is a scheduled install image drop to run the rawhide acceptance test plan 17:00
jlaska #topic open discussion - When is next rawhide install image drop? 17:00
jlaska #info so this Thursday (1/21) is a scheduled install image drop to run the rawhide acceptance test plan 17:00
jlaska #link http://poelstra.fedorapeople.org/schedules/f-12/f-12-quality-tasks.html 17:00
jlaska I sent an email out to dcantrell and jkeating for guidance on indentifing who is doing what for this drop 17:01
jlaska and filed a rel-eng ticket just to track creating the images 17:01
* jlaska finds link 17:01
jlaska #info https://fedorahosted.org/rel-eng/ticket/3277 17:01
jlaska so we ran through rats_install (finished up last monday) ... and this time should include some bug fixes for issues identified 17:02
jlaska Rats test results against anaconda-13.16 (using http://clumens.fedorapeople.org/updates.img) - http://jlaska.fedorapeople.org/rats.png 17:03
jlaska #topic open discussion - <your topic here> 17:03
jlaska wwoods thanks for reminding me! :D 17:04
kparal all nicely green 17:04
jlaska an i386 compose wasn't created ... so there were no results 17:04
RodrigoPadula hi 17:04
jlaska any other issues to discuss? Otherwise, let's close things out and get back to work 17:05
jlaska RodrigoPadula: hi 17:05
RodrigoPadula famsco meeting ? 17:05
jlaska RodrigoPadula: one moment, wrapping up fedora-qa meeting 17:06
jlaska okay gang ... thanks for your attention 17:06
RodrigoPadula ops.. soryy 17:06
jlaska as usual, I'll follow-up to the list with minutes 17:06
jlaska #endmeeting 17:06

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