From Fedora Project Wiki

< QA‎ | Meetings

m (Add agenda link)
m (Updated minutes)
 
(2 intermediate revisions by the same user not shown)
Line 2: Line 2:


People Present (lines said):
People Present (lines said):
 
* jlaska (111)
* adamw (38)
* wwoods (25)
* Oxf13 (24)
* kparal1 (17)
* skvidal (15)
* buggbot (5)
* poelcat (4)
* zodbot (2)
* brunowolff_ (1)
* Sir_Limpsalot (1)


Regrets:
Regrets:
* Liam Li (lili)
* Liam Li (lili)
* He Rui (rhe)
* He Rui (rhe)
* David Pravec (dpravec)


<!--
<!--
Line 36: Line 47:


* [https://www.redhat.com/archives/fedora-test-list/2009-October/msg00071.html Proposed meeting agenda]
* [https://www.redhat.com/archives/fedora-test-list/2009-October/msg00071.html Proposed meeting agenda]
* [FIXME meetbot summary]
* [http://meetbot.fedoraproject.org/fedora-meeting/2009-10-05/fedora-meeting.2009-10-05-16.00.html meetbot summary]


== Preview Meeting follow-up ==
== Preview Meeting follow-up ==


http://meetbot.fedoraproject.org/fedora-meeting/2009-09-28/fedora-meeting.2009-09-28-16.00.html
http://meetbot.fedoraproject.org/fedora-meeting/2009-09-28/fedora-meeting.2009-09-28-16.00.html
=== Anaconda dependency follow-up ===
Adamw reminded the group that we hadn't yet followed up on the previous topic raised by dpravec around installer dependencies changing out from under it.
F13 noted that there were discussions with RHT management reminding folks that it was too late to make general (or feature) changes in F-12. 
Jlaska asked what specific issues initiated this discussion.  Adamw and f13 noted the recent nfs the lvm changes.


== AutoQA update ==
== AutoQA update ==
Wwoods wired up the UI, so members of the 'qa' group can now add/remove test results for the manual tests (see [http://wwoods.fedorapeople.org/screenshots/irb.png screenshot).  Also decided to defer:
# sweet ajax UI junk and
# automating the yum/network tests until after irb.com completes
Reminder of the current roadmap: https://fedorahosted.org/autoqa/milestone/israwhidebroken.com.  Current tasks include:
# get links back from israwhidebroken to autotest
# get it all running in production in public
Jlaska took an action item to sync up w/ mmcgrath to identify next steps when the AutoQA hardware arrives in PHX2.
=== Packagediff update ===
Next, kparal updated the group on his packagediff activities.  The intention is to alert on important changes between packages, hopefully part of autoqa project in the future. 
Currently working 2 tickets:
# https://fedorahosted.org/autoqa/ticket/53 - Investigate what rpmdiff offers to our tests
# https://fedorahosted.org/autoqa/ticket/54 - Write rpmdiff test
The code currently highlights changed dependencies, changed config files, changed file modes and such stuff.  Wwoods suggested also falgging added/removed binaries. 
Some discussion surfaced around whether Kparal's efforts were based on an older RHT internal project called 'rpmdiff'.  Kparal's efforts are entirely based on the ''rpmlint'' implementation of ''rpmdiff''.  Kparal is currently waiting for some feedback on a few rpmdiff issues.  Skvidal recommended reaching out to ville skytta.


== F-12-Beta QA Readiness ==
== F-12-Beta QA Readiness ==
Jlaska asked the team for help preparing for the upcoming Go/No Go decision at the upcoming rel-eng meeting.  The team informally walked the remaining [https://bugzilla.redhat.com/showdependencytree.cgi?id=F12Beta&hide_resolved=1 F12Beta blocker bugs].
F13 asked if any blocker bug candidates came out of the Test Day.  Aside from {{bz|517260}} it wasn't clear yet whether any of the recorded test day bugs (https://www.redhat.com/archives/fedora-test-list/2009-October/msg00058.html) where beta blockers.  Jlaska took an action item to catch up with clumens to help review the list.  So far, the only Test day bugs raised to the beta blocker list are:
* {{bz|526842}} ASSIGNED - Firstboot not run after installation
* {{bz|517260}} ASSIGNED - liveinst fails at partitioning screeen
* {{bz|523862}} CLOSED RAWHIDE - mdadm craps at boot
Adamw expressed concern around the missing panel icon bug noted on the list by Chuck Anderson (see https://www.redhat.com/archives/fedora-test-list/2009-October/msg00058.html).  Turns out this is {{bz|510249}}.  Mclasen already evaluated and recommended fixing this issue post-Beta.
Jlaska asked for wwoods and skvidal expertise on rhe's preupgrade {{bz|526208}}.  It's a bug in the F-11 package, but would potentially impact anyone using preupgrade to upgrade from F-11 to F-12.  Skvidal intended to investigate the UI issue after the meeting.
Jlaska asked if {{bz|526535}} should be moved into MODIFIED given a package was built and testing requested on fedora-devel-list (see https://www.redhat.com/archives/fedora-devel-list/2009-October/msg00154.html).  Adamw asked what the policy is with regards to MODIFIED bugs.  Does MODIFIED mean a package is built and a tag request is submitted?  F13 proposed that MODIFIED means a fix is available, but not yet tested or included in the product.  This seems to hold when adding the freeze 'tagging' procedure into the mix.


== Upcoming QA events ==
== Upcoming QA events ==
Jlaska did a ''speedy'' walk through of upcoming QA related events


* 2009-10-05 - F12 Beta go/no_go meeting (@  18:00pm - rel-eng meeting)
* 2009-10-05 - F12 Beta go/no_go meeting (@  18:00pm - rel-eng meeting)
Line 55: Line 112:


== Open floor - <your topic here> ==
== Open floor - <your topic here> ==
No open discussion topics were raised.


= Action items =
= Action items =
# jlaska to catch up with mmcgrath on delivery of autoqa hardware to PHX
# jlaska - sync-up with clumens to identify any blocking issues from https://www.redhat.com/archives/fedora-test-list/2009-October/msg00073.html
# poelcat to check in on beta blocker status of 510249


= IRC transcript =
= IRC transcript =
{|
|- id="t16:00:39"
! style="background-color: #407a40" | jlaska
| style="color: #407a40" | #startmeeting Fedora QA meeting
|| [[#t16:00:39|16:00]]
|- id="t16:00:39"
! style="background-color: #42427e" | zodbot
| style="color: #42427e" | Meeting started Mon Oct  5 16:00:39 2009 UTC.  The chair is jlaska. Information about MeetBot at http://wiki.debian.org/MeetBot.
|| [[#t16:00:39|16:00]]
|- id="t16:00:39"
! style="background-color: #42427e" | zodbot
| style="color: #42427e" | Useful Commands: #action #agreed #halp #info #idea #link #topic.
|| [[#t16:00:39|16:00]]
|- id="t16:00:51"
! style="background-color: #407a40" | jlaska
| style="color: #407a40" | #topic Gathering able bodied persons
|| [[#t16:00:51|16:00]]
|- id="t16:00:53"
! style="background-color: #818144" | adamw
| style="color: #818144" | morning
|| [[#t16:00:53|16:00]]
|- id="t16:01:03"
| colspan="2" | * kparal1 says hi
|| [[#t16:01:03|16:01]]
|- id="t16:01:11"
! style="background-color: #818144" | adamw
| style="color: #818144" | that topic is discriminatory against disabled qa people.
|| [[#t16:01:11|16:01]]
|- id="t16:01:18"
! style="background-color: #818144" | adamw
| style="color: #818144" | i say this only half in jest, because, well, it actually is =)
|| [[#t16:01:18|16:01]]
|- id="t16:01:54"
! style="background-color: #854685" | kparal1
| style="color: #854685" | but only for english people, i myself didn't get that :)
|| [[#t16:01:54|16:01]]
|- id="t16:02:26"
! style="background-color: #407a40" | jlaska
| style="color: #407a40" | adamw: Well certainly no ill will intended ... of course will adjust in the future
|| [[#t16:02:26|16:02]]
|- id="t16:02:41"
! style="background-color: #818144" | adamw
| style="color: #818144" | interesting where a running joke can get you, hehe
|| [[#t16:02:41|16:02]]
|- id="t16:02:45"
! style="background-color: #407a40" | jlaska
| style="color: #407a40" | ;)
|| [[#t16:02:45|16:02]]
|- id="t16:03:07"
! style="background-color: #407a40" | jlaska
| style="color: #407a40" | I thought I was safe not limiting the meeting to gender
|| [[#t16:03:07|16:03]]
|- id="t16:03:18"
! style="background-color: #818144" | adamw
| style="color: #818144" | ah, it's never that easy
|| [[#t16:03:18|16:03]]
|- id="t16:03:24"
! style="background-color: #407a40" | jlaska
| style="color: #407a40" | indeed
|| [[#t16:03:24|16:03]]
|- id="t16:03:28"
! style="background-color: #407a40" | jlaska
| style="color: #407a40" | okay, who else do we have
|| [[#t16:03:28|16:03]]
|- id="t16:03:29"
! style="background-color: #818144" | adamw
| style="color: #818144" | aaaaaanyway
|| [[#t16:03:29|16:03]]
|- id="t16:03:47"
! style="background-color: #407a40" | jlaska
| style="color: #407a40" | I sense the presence of wwoods ... lurking in the shadows
|| [[#t16:03:47|16:03]]
|- id="t16:04:05"
| colspan="2" | * wwoods rolls a Stealth check
|| [[#t16:04:05|16:04]]
|- id="t16:04:24"
! style="background-color: #407a40" | jlaska
| style="color: #407a40" | Oxf13 is around too I believe
|| [[#t16:04:24|16:04]]
|- id="t16:04:30"
| colspan="2" | * Oxf13
|| [[#t16:04:30|16:04]]
|- id="t16:05:05"
! style="background-color: #407a40" | jlaska
| style="color: #407a40" | We'll be missing dpravec today
|| [[#t16:05:05|16:05]]
|- id="t16:05:17"
! style="background-color: #407a40" | jlaska
| style="color: #407a40" | so let's get started
|| [[#t16:05:17|16:05]]
|- id="t16:05:24"
! style="background-color: #407a40" | jlaska
| style="color: #407a40" | #topic Previous Meeting Follow-up
|| [[#t16:05:24|16:05]]
|- id="t16:05:30"
! style="background-color: #407a40" | jlaska
| style="color: #407a40" | First ... an apology
|| [[#t16:05:30|16:05]]
|- id="t16:05:54"
! style="background-color: #407a40" | jlaska
| style="color: #407a40" | there will only be 1 QA meeting right now ... contrary to the dueling agendas posted to the list
|| [[#t16:05:54|16:05]]
|- id="t16:06:12"
| colspan="2" | * adamw leads his followers to #confederate-fedora-meeting
|| [[#t16:06:12|16:06]]
|- id="t16:06:26"
! style="background-color: #407a40" | jlaska
| style="color: #407a40" | adamw: take the action items with you please!
|| [[#t16:06:26|16:06]]
|- id="t16:06:31"
! style="background-color: #818144" | adamw
| style="color: #818144" | =)
|| [[#t16:06:31|16:06]]
|- id="t16:06:50"
! style="background-color: #407a40" | jlaska
| style="color: #407a40" | I didn't have any recorded action items from last weeks meeting
|| [[#t16:06:50|16:06]]
|- id="t16:06:53"
| colspan="2" | * jlaska looking at http://meetbot.fedoraproject.org/fedora-meeting/2009-09-28/fedora-meeting.2009-09-28-16.00.html
|| [[#t16:06:53|16:06]]
|- id="t16:07:05"
! style="background-color: #407a40" | jlaska
| style="color: #407a40" | adamw: was there anything not recorded that you wanted to discuss from last week?
|| [[#t16:07:05|16:07]]
|- id="t16:07:33"
! style="background-color: #818144" | adamw
| style="color: #818144" | nothing specific from last week that i can think of, but we could follow up on the discussion of development issues from a couple of weeks ago, now more people are here
|| [[#t16:07:33|16:07]]
|- id="t16:07:36"
! style="background-color: #818144" | adamw
| style="color: #818144" | esp. oxf13
|| [[#t16:07:36|16:07]]
|- id="t16:07:52"
! style="background-color: #818144" | adamw
| style="color: #818144" | Oxf13: you remember that? the talk about anaconda dependencies and rhel changes parachuted into fedora...
|| [[#t16:07:52|16:07]]
|- id="t16:08:23"
! style="background-color: #488888" | Oxf13
| style="color: #488888" | vaguely
|| [[#t16:08:23|16:08]]
|- id="t16:08:39"
! style="background-color: #818144" | adamw
| style="color: #818144" | you mentioned there were meetings at which some of those issues could be raised - gone anywhere with that?
|| [[#t16:08:39|16:08]]
|- id="t16:09:05"
! style="background-color: #488888" | Oxf13
| style="color: #488888" | yeah, we re-affirmed to RHT management that it is too late to make feature changes in F12
|| [[#t16:09:05|16:09]]
|- id="t16:09:12"
! style="background-color: #818144" | adamw
| style="color: #818144" | great
|| [[#t16:09:12|16:09]]
|- id="t16:09:36"
! style="background-color: #818144" | adamw
| style="color: #818144" | was there any pushback?
|| [[#t16:09:36|16:09]]
|- id="t16:10:02"
! style="background-color: #488888" | Oxf13
| style="color: #488888" | not yet
|| [[#t16:10:02|16:10]]
|- id="t16:10:32"
! style="background-color: #407a40" | jlaska
| style="color: #407a40" | I don't have the full history of this discussion topic ... was this anaconda specific ... or general changes?
|| [[#t16:10:32|16:10]]
|- id="t16:10:59"
! style="background-color: #818144" | adamw
| style="color: #818144" | jlaska: it was a wide-ranging discussion :)
|| [[#t16:10:59|16:10]]
|- id="t16:11:12"
! style="background-color: #407a40" | jlaska
| style="color: #407a40" | that's my guess based on recent f-d-list threads
|| [[#t16:11:12|16:11]]
|- id="t16:11:30"
! style="background-color: #818144" | adamw
| style="color: #818144" | jlaska: it started with someone (dpravec iirc) raising anaconda team's concerns that things anaconda depended on were being changed in major ways too close to the beta
|| [[#t16:11:30|16:11]]
|- id="t16:11:46"
! style="background-color: #488888" | Oxf13
| style="color: #488888" | eg nfs
|| [[#t16:11:46|16:11]]
|- id="t16:11:50"
! style="background-color: #407a40" | jlaska
| style="color: #407a40" | gotcha .. yeah a fair concern
|| [[#t16:11:50|16:11]]
|- id="t16:11:51"
! style="background-color: #818144" | adamw
| style="color: #818144" | it broadened out a bit from there into general issues causing undesirable changes in late pre-pre-release phases
|| [[#t16:11:51|16:11]]
|- id="t16:11:51"
! style="background-color: #407a40" | jlaska
| style="color: #407a40" | lvm
|| [[#t16:11:51|16:11]]
|- id="t16:12:03"
! style="background-color: #818144" | adamw
| style="color: #818144" | yeah that stuff
|| [[#t16:12:03|16:12]]
|- id="t16:12:04"
! style="background-color: #488888" | Oxf13
| style="color: #488888" | right and lvm
|| [[#t16:12:04|16:12]]
|- id="t16:12:13"
! style="background-color: #818144" | adamw
| style="color: #818144" | though the discussion was right before the lvm storm broke iirc
|| [[#t16:12:13|16:12]]
|- id="t16:12:28"
! style="background-color: #407a40" | jlaska
| style="color: #407a40" | dcantrell has some interesting testing that's maturing ... but could potentially be used to highlight these types of issues in the future
|| [[#t16:12:28|16:12]]
|- id="t16:13:15"
! style="background-color: #407a40" | jlaska
| style="color: #407a40" | might be worth having a presentation/discussion as his tests mature at FUDCon perhaps
|| [[#t16:13:15|16:13]]
|- id="t16:13:37"
! style="background-color: #818144" | adamw
| style="color: #818144" | roger
|| [[#t16:13:37|16:13]]
|- id="t16:13:40"
! style="background-color: #407a40" | jlaska
| style="color: #407a40" | certainly won't solve all the worlds problems, but might help give the anaconda team a heads up when things they rely on are changed out from under them
|| [[#t16:13:40|16:13]]
|- id="t16:14:18"
! style="background-color: #407a40" | jlaska
| style="color: #407a40" | #idea How can the QA team support dcantrell's anaconda A[BP]I checking routines
|| [[#t16:14:18|16:14]]
|- id="t16:14:26"
! style="background-color: #407a40" | jlaska
| style="color: #407a40" | any other points on this topic?
|| [[#t16:14:26|16:14]]
|- id="t16:15:07"
! style="background-color: #407a40" | jlaska
| style="color: #407a40" | if so ... we might choose to make this a repeating topic
|| [[#t16:15:07|16:15]]
|- id="t16:15:22"
! style="background-color: #818144" | adamw
| style="color: #818144" | i'd rather not, meetings are long enough as it isw
|| [[#t16:15:22|16:15]]
|- id="t16:15:32"
! style="background-color: #818144" | adamw
| style="color: #818144" | i just wanted to follow up on the discussion, and we couldn't do it last week as jesse wasn't here
|| [[#t16:15:32|16:15]]
|- id="t16:15:38"
! style="background-color: #407a40" | jlaska
| style="color: #407a40" | roger
|| [[#t16:15:38|16:15]]
|- id="t16:16:06"
! style="background-color: #407a40" | jlaska
| style="color: #407a40" | alrighty ... next up we've got a quick check-in on the AutoQA front
|| [[#t16:16:06|16:16]]
|- id="t16:16:12"
! style="background-color: #407a40" | jlaska
| style="color: #407a40" | #topic AutoQA update
|| [[#t16:16:12|16:16]]
|- id="t16:16:23"
! style="background-color: #407a40" | jlaska
| style="color: #407a40" | wwoods: you've got the floor
|| [[#t16:16:23|16:16]]
|- id="t16:16:32"
! style="background-color: #8c4a4a" | wwoods
| style="color: #8c4a4a" | let's see
|| [[#t16:16:32|16:16]]
|- id="t16:17:02"
! style="background-color: #8c4a4a" | wwoods
| style="color: #8c4a4a" | last week I wired up the UI, so members of the 'qa' group can now add/remove test results for the manual tests
|| [[#t16:17:02|16:17]]
|- id="t16:17:27"
! style="background-color: #8c4a4a" | wwoods
| style="color: #8c4a4a" | (this is for the israwhidebroken mini-frontend)
|| [[#t16:17:27|16:17]]
|- id="t16:17:34"
! style="background-color: #407a40" | jlaska
| style="color: #407a40" | #link http://wwoods.fedorapeople.org/screenshots/irb.png
|| [[#t16:17:34|16:17]]
|- id="t16:18:03"
! style="background-color: #8c4a4a" | wwoods
| style="color: #8c4a4a" | we decided to defer a) sweet ajax UI junk and b) automating the yum/network tests until later
|| [[#t16:18:03|16:18]]
|- id="t16:18:31"
! style="background-color: #8c4a4a" | wwoods
| style="color: #8c4a4a" | so here's the current roadmap: https://fedorahosted.org/autoqa/milestone/israwhidebroken.com
|| [[#t16:18:31|16:18]]
|- id="t16:18:52"
! style="background-color: #8c4a4a" | wwoods
| style="color: #8c4a4a" | basically it comes down to: 1) get links back from israwhidebroken to autotest
|| [[#t16:18:52|16:18]]
|- id="t16:19:01"
! style="background-color: #8c4a4a" | wwoods
| style="color: #8c4a4a" | and then 2) get it all running in production in public
|| [[#t16:19:01|16:19]]
|- id="t16:19:36"
! style="background-color: #407a40" | jlaska
| style="color: #407a40" | #action jlaska to catch up with mmcgrath on delivery of autoqa hardware to PHX
|| [[#t16:19:36|16:19]]
|- id="t16:19:54"
! style="background-color: #8c4a4a" | wwoods
| style="color: #8c4a4a" | yeah there's rumors that our autoqa hardware may be arriving soon?
|| [[#t16:19:54|16:19]]
|- id="t16:20:04"
! style="background-color: #407a40" | jlaska
| style="color: #407a40" | I got word on Friday that "it's in the mail"
|| [[#t16:20:04|16:20]]
|- id="t16:20:19"
! style="background-color: #8c4a4a" | wwoods
| style="color: #8c4a4a" | nice
|| [[#t16:20:19|16:20]]
|- id="t16:20:58"
! style="background-color: #407a40" | jlaska
| style="color: #407a40" | definitely!  I took an action to sync up with infrastructure to figure out what we need to do once the hardware lands
|| [[#t16:20:58|16:20]]
|- id="t16:21:01"
! style="background-color: #8c4a4a" | wwoods
| style="color: #8c4a4a" | so yeah, getting the backreferences to autotest turns out to be nontrivial but I've been talking with upstream and we'll work something out
|| [[#t16:21:01|16:21]]
|- id="t16:21:23"
! style="background-color: #8c4a4a" | wwoods
| style="color: #8c4a4a" | after that it's all ready to go into "production"
|| [[#t16:21:23|16:21]]
|- id="t16:21:38"
| colspan="2" | * jlaska queues the suspense music
|| [[#t16:21:38|16:21]]
|- id="t16:21:42"
! style="background-color: #8c4a4a" | wwoods
| style="color: #8c4a4a" | for values of "production" roughly equal to "public early beta"
|| [[#t16:21:42|16:21]]
|- id="t16:22:01"
! style="background-color: #8c4a4a" | wwoods
| style="color: #8c4a4a" | still: woo!
|| [[#t16:22:01|16:22]]
|- id="t16:22:14"
! style="background-color: #407a40" | jlaska
| style="color: #407a40" | right on ... I second that 'woo'
|| [[#t16:22:14|16:22]]
|- id="t16:22:26"
! style="background-color: #8c4a4a" | wwoods
| style="color: #8c4a4a" | think that's all from mem
|| [[#t16:22:26|16:22]]
|- id="t16:22:27"
! style="background-color: #8c4a4a" | wwoods
| style="color: #8c4a4a" | err, me
|| [[#t16:22:27|16:22]]
|- id="t16:22:34"
! style="background-color: #407a40" | jlaska
| style="color: #407a40" | wwoods: thanks for the update!
|| [[#t16:22:34|16:22]]
|- id="t16:22:52"
! style="background-color: #407a40" | jlaska
| style="color: #407a40" | kparal1: any updates on the packagediff piece you're investigating?
|| [[#t16:22:52|16:22]]
|- id="t16:23:20"
! style="background-color: #854685" | kparal1
| style="color: #854685" | well, i have started to write a test for comparing old and new rpm package
|| [[#t16:23:20|16:23]]
|- id="t16:23:32"
! style="background-color: #854685" | kparal1
| style="color: #854685" | it will be hopefully part of autqa in the future
|| [[#t16:23:32|16:23]]
|- id="t16:23:52"
! style="background-color: #854685" | kparal1
| style="color: #854685" | the intention is to alert on important changes between packages
|| [[#t16:23:52|16:23]]
|- id="t16:24:28"
! style="background-color: #854685" | kparal1
| style="color: #854685" | currently i'm announcing changed dependencies, changed config files, changed file modes and such stuff
|| [[#t16:24:28|16:24]]
|- id="t16:24:50"
! style="background-color: #8c4a4a" | wwoods
| style="color: #8c4a4a" | nice!
|| [[#t16:24:50|16:24]]
|- id="t16:25:00"
! style="background-color: #854685" | kparal1
| style="color: #854685" | developing goes slowly because i can't devote it much time but i hope it will be usable soon
|| [[#t16:25:00|16:25]]
|- id="t16:25:13"
! style="background-color: #8c4a4a" | wwoods
| style="color: #8c4a4a" | adding/removing binaries should definitely be announced as well
|| [[#t16:25:13|16:25]]
|- id="t16:25:30"
! style="background-color: #854685" | kparal1
| style="color: #854685" | yes, that's in the plan: https://fedorahosted.org/autoqa/ticket/53
|| [[#t16:25:30|16:25]]
|- id="t16:25:41"
| colspan="2" | * wwoods reviews
|| [[#t16:25:41|16:25]]
|- id="t16:25:49"
! style="background-color: #854685" | kparal1
| style="color: #854685" | you can see my code, i have put it online: https://fedorahosted.org/autoqa/ticket/54
|| [[#t16:25:49|16:25]]
|- id="t16:25:51"
! style="background-color: #8c4a4a" | wwoods
| style="color: #8c4a4a" | pretty sure we talked about all that stuff before so I'm sure it's all here
|| [[#t16:25:51|16:25]]
|- id="t16:26:07"
! style="background-color: #854685" | kparal1
| style="color: #854685" | it's just a first shot and i'm learning python with it, so be mercifull :)
|| [[#t16:26:07|16:26]]
|- id="t16:26:28"
! style="background-color: #854685" | kparal1
| style="color: #854685" | i think that's all from me
|| [[#t16:26:28|16:26]]
|- id="t16:26:52"
! style="background-color: #407a40" | jlaska
| style="color: #407a40" | kparal1: hah!  you've taken on quite a challenge for first time python (e.g. rpm libs)
|| [[#t16:26:52|16:26]]
|- id="t16:27:32"
! style="background-color: #854685" | kparal1
| style="color: #854685" | also there are some bugs waiting in rpmdiff to be fixed, but the rpmlint project seems a little dead now (trac not working properly, mailing list halted)
|| [[#t16:27:32|16:27]]
|- id="t16:27:41"
! style="background-color: #854685" | kparal1
| style="color: #854685" | but hopefully skvidal will help me with that
|| [[#t16:27:41|16:27]]
|- id="t16:27:47"
| colspan="2" | * skvidal looks up
|| [[#t16:27:47|16:27]]
|- id="t16:28:00"
! style="background-color: #4b904b" | skvidal
| style="color: #4b904b" | kparal1: ah yes - your email from last week
|| [[#t16:28:00|16:28]]
|- id="t16:28:23"
! style="background-color: #488888" | Oxf13
| style="color: #488888" | kparal1: is this working from existing rpmdiff code?
|| [[#t16:28:23|16:28]]
|- id="t16:28:33"
! style="background-color: #4b904b" | skvidal
| style="color: #4b904b" | Oxf13: not the rhel rpmdiff
|| [[#t16:28:33|16:28]]
|- id="t16:28:38"
! style="background-color: #488888" | Oxf13
| style="color: #488888" | right
|| [[#t16:28:38|16:28]]
|- id="t16:28:39"
! style="background-color: #4b904b" | skvidal
| style="color: #4b904b" | Oxf13: the rpmlint, rpmdiff
|| [[#t16:28:39|16:28]]
|- id="t16:28:41"
! style="background-color: #488888" | Oxf13
| style="color: #488888" | that one is still closed
|| [[#t16:28:41|16:28]]
|- id="t16:28:44"
! style="background-color: #854685" | kparal1
| style="color: #854685" | Oxf13: yes, i'm using the public rpmdiff in my script
|| [[#t16:28:44|16:28]]
|- id="t16:28:45"
! style="background-color: #488888" | Oxf13
| style="color: #488888" | *stab*
|| [[#t16:28:45|16:28]]
|- id="t16:28:49"
! style="background-color: #4b904b" | skvidal
| style="color: #4b904b" | Oxf13: and will, afaict, never be opened
|| [[#t16:28:49|16:28]]
|- id="t16:29:09"
! style="background-color: #407a40" | jlaska
| style="color: #407a40" | in my best ed mcmahon "you sir, are correct sir"
|| [[#t16:29:09|16:29]]
|- id="t16:29:13"
! style="background-color: #4b904b" | skvidal
| style="color: #4b904b" | kparal1: I think I should talk to Ville - see if he has any thoughts
|| [[#t16:29:13|16:29]]
|- id="t16:29:36"
! style="background-color: #854685" | kparal1
| style="color: #854685" | Ville is irc nick?
|| [[#t16:29:36|16:29]]
|- id="t16:29:41"
! style="background-color: #4b904b" | skvidal
| style="color: #4b904b" | jlaska: you realize how old that makes you sound that 1. you know who ed mcmahon is 2. you know who he would say that to 3. you know the snl bit about that
|| [[#t16:29:41|16:29]]
|- id="t16:29:50"
! style="background-color: #4b904b" | skvidal
| style="color: #4b904b" | kparal1: he's almost never on irc - ville skytta
|| [[#t16:29:50|16:29]]
|- id="t16:29:54"
! style="background-color: #407a40" | jlaska
| style="color: #407a40" | skvidal: ;)
|| [[#t16:29:54|16:29]]
|- id="t16:29:58"
! style="background-color: #854685" | kparal1
| style="color: #854685" | skvidal: ok, thx
|| [[#t16:29:58|16:29]]
|- id="t16:30:03"
! style="background-color: #4b904b" | skvidal
| style="color: #4b904b" | kparal1: when he is on irc he's scop
|| [[#t16:30:03|16:30]]
|- id="t16:31:01"
! style="background-color: #407a40" | jlaska
| style="color: #407a40" | alrighty ... aside from just a quick run through of upcoming QA events ... I wanted to spend some time surveying the group for our Beta readiness
|| [[#t16:31:01|16:31]]
|- id="t16:31:07"
! style="background-color: #407a40" | jlaska
| style="color: #407a40" | #topic F-12-Beta QA readiness
|| [[#t16:31:07|16:31]]
|- id="t16:31:24"
! style="background-color: #407a40" | jlaska
| style="color: #407a40" | Oxf13 will be hosting a go/no_go discussion on the beta today during the rel-eng meeting (@ 18:00 UTC)
|| [[#t16:31:24|16:31]]
|- id="t16:31:54"
! style="background-color: #407a40" | jlaska
| style="color: #407a40" | but I thought we could spend a few minutes here making sure that all the _hot_ issues are on the radar ... and see if anything is stuck in process
|| [[#t16:31:54|16:31]]
|- id="t16:32:07"
! style="background-color: #488888" | Oxf13
| style="color: #488888" | looking pretty no-go at this point
|| [[#t16:32:07|16:32]]
|- id="t16:32:27"
! style="background-color: #818144" | adamw
| style="color: #818144" | yeah, not much movement on bugs over the weekend :/
|| [[#t16:32:27|16:32]]
|- id="t16:32:30"
! style="background-color: #407a40" | jlaska
| style="color: #407a40" | pulling up the F12Beta blocker bug report ...
|| [[#t16:32:30|16:32]]
|- id="t16:32:32"
! style="background-color: #407a40" | jlaska
| style="color: #407a40" | https://bugzilla.redhat.com/showdependencytree.cgi?id=F12Beta&amp;hide_resolved=1
|| [[#t16:32:32|16:32]]
|- id="t16:32:33"
! style="background-color: #488888" | Oxf13
| style="color: #488888" | still no first boot, nm-gnome crashes, ppc64 netboot missing, and aliveinst failure?
|| [[#t16:32:33|16:32]]
|- id="t16:32:38"
! style="background-color: #4d4d93" | brunowolff_
| style="color: #4d4d93" | mdadm got fixed
|| [[#t16:32:38|16:32]]
|- id="t16:32:49"
! style="background-color: #488888" | Oxf13
| style="color: #488888" | adamw: party my fault.  I didn't look at the tag queue last night, got tied up with family stuff
|| [[#t16:32:49|16:32]]
|- id="t16:33:07"
! style="background-color: #407a40" | jlaska
| style="color: #407a40" | and the util-linux-ng issue has a build+tag request in I believe
|| [[#t16:33:07|16:33]]
|- id="t16:33:36"
! style="background-color: #488888" | Oxf13
| style="color: #488888" | yeah, some stuff needs testing to clear the tag queue
|| [[#t16:33:36|16:33]]
|- id="t16:33:49"
! style="background-color: #818144" | adamw
| style="color: #818144" | hum
|| [[#t16:33:49|16:33]]
|- id="t16:34:01"
! style="background-color: #818144" | adamw
| style="color: #818144" | important point: that's an entirely different networkmanager crash report from the one we worked on in the meeting
|| [[#t16:34:01|16:34]]
|- id="t16:34:04"
! style="background-color: #818144" | adamw
| style="color: #818144" | it's been tagged as a blocker independently
|| [[#t16:34:04|16:34]]
|- id="t16:34:09"
! style="background-color: #818144" | adamw
| style="color: #818144" | may be a dupe of the other report
|| [[#t16:34:09|16:34]]
|- id="t16:34:10"
! style="background-color: #818144" | adamw
| style="color: #818144" | i will check
|| [[#t16:34:10|16:34]]
|- id="t16:34:25"
! style="background-color: #488888" | Oxf13
| style="color: #488888" | ok
|| [[#t16:34:25|16:34]]
|- id="t16:35:53"
! style="background-color: #407a40" | jlaska
| style="color: #407a40" | while adamw's looking for that NM issue ... are there any other bugs that aren't represented on the current blocker list that folks are concerned about?
|| [[#t16:35:53|16:35]]
|- id="t16:37:11"
! style="background-color: #818144" | adamw
| style="color: #818144" | that 'invisible icons' bug from the list looks icky
|| [[#t16:37:11|16:37]]
|- id="t16:37:17"
! style="background-color: #818144" | adamw
| style="color: #818144" | though i'm not clear on the exact symptoms
|| [[#t16:37:17|16:37]]
|- id="t16:38:46"
! style="background-color: #488888" | Oxf13
| style="color: #488888" | jlaska: anything come up in the anaconda test day?
|| [[#t16:38:46|16:38]]
|- id="t16:38:51"
! style="background-color: #407a40" | jlaska
| style="color: #407a40" | https://www.redhat.com/archives/fedora-test-list/2009-October/msg00058.html
|| [[#t16:38:51|16:38]]
|- id="t16:38:58"
| colspan="2" | * Sir_Limpsalot sneaks inn..
|| [[#t16:38:58|16:38]]
|- id="t16:39:03"
! style="background-color: #488888" | Oxf13
| style="color: #488888" | as far as blocker worthy bugs
|| [[#t16:39:03|16:39]]
|- id="t16:40:08"
! style="background-color: #407a40" | jlaska
| style="color: #407a40" | Oxf13: a few bugs ... but don't have enough info yet as to whether they are common or exceptions
|| [[#t16:40:08|16:40]]
|- id="t16:40:25"
! style="background-color: #818144" | adamw
| style="color: #818144" | hi there
|| [[#t16:40:25|16:40]]
|- id="t16:40:34"
! style="background-color: #407a40" | jlaska
| style="color: #407a40" | we have the ongoing pain with yaboot not properly booting after some scenarios (bug#523754)
|| [[#t16:40:34|16:40]]
|- id="t16:40:35"
! style="background-color: #97974f" | buggbot
| style="color: #97974f" | Bug https://bugzilla.redhat.com/bugzilla/show_bug.cgi?id=523754 is not accessible.
|| [[#t16:40:35|16:40]]
|- id="t16:41:12"
! style="background-color: #407a40" | jlaska
| style="color: #407a40" | hmm, that's not the right bz ...  try bug#523754
|| [[#t16:41:12|16:41]]
|- id="t16:41:29"
! style="background-color: #407a40" | jlaska
| style="color: #407a40" | oh perms on the bz ... odd
|| [[#t16:41:29|16:41]]
|- id="t16:41:30"
! style="background-color: #818144" | adamw
| style="color: #818144" | that's the same number you just said
|| [[#t16:41:30|16:41]]
|- id="t16:41:35"
! style="background-color: #407a40" | jlaska
| style="color: #407a40" | sure is :)
|| [[#t16:41:35|16:41]]
|- id="t16:42:02"
! style="background-color: #407a40" | jlaska
| style="color: #407a40" | there's a few like that against Fedora ... specific to ppc ... and I Think they're all related to the same core yaboot issue
|| [[#t16:42:02|16:42]]
|- id="t16:42:11"
! style="background-color: #407a40" | jlaska
| style="color: #407a40" | this is going off my gut feel from testing, so could be wrong
|| [[#t16:42:11|16:42]]
|- id="t16:42:22"
! style="background-color: #407a40" | jlaska
| style="color: #407a40" | it's not a new problem though, so I wouldn't raise this is a beta blocker
|| [[#t16:42:22|16:42]]
|- id="t16:43:41"
! style="background-color: #407a40" | jlaska
| style="color: #407a40" | it looks like the anaconda-devel team has already started working the test day bugs ... I'll see if I can get clumens to help identify and alarming storage issues in the list
|| [[#t16:43:41|16:43]]
|- id="t16:44:06"
! style="background-color: #407a40" | jlaska
| style="color: #407a40" | #action jlaska - sync-up with clumens to identify any blocking issues from https://www.redhat.com/archives/fedora-test-list/2009-October/msg00073.html
|| [[#t16:44:06|16:44]]
|- id="t16:44:22"
! style="background-color: #407a40" | jlaska
| style="color: #407a40" | there were a few RAID related issues, but as brunowolff_ said ... a fix is already tagged for that
|| [[#t16:44:22|16:44]]
|- id="t16:45:22"
! style="background-color: #407a40" | jlaska
| style="color: #407a40" | adamw: anything else on the invisible icon thread? https://www.redhat.com/archives/fedora-test-list/2009-October/msg00058.html
|| [[#t16:45:22|16:45]]
|- id="t16:45:58"
! style="background-color: #407a40" | jlaska
| style="color: #407a40" | mclasen called out bug#510249 on this issue
|| [[#t16:45:58|16:45]]
|- id="t16:46:00"
! style="background-color: #97974f" | buggbot
| style="color: #97974f" | Bug https://bugzilla.redhat.com/bugzilla/show_bug.cgi?id=510249 medium, low, ---, mclasen, ASSIGNED, Missing panel applets on gnome login; "Glib-GObject-CRITICAL" messages....
|| [[#t16:46:00|16:46]]
|- id="t16:46:10"
! style="background-color: #407a40" | jlaska
| style="color: #407a40" | which is currently marked as a F12Blocker
|| [[#t16:46:10|16:46]]
|- id="t16:46:20"
! style="background-color: #818144" | adamw
| style="color: #818144" | jlaska: no, i just saw it this morning, haven't looked into it much yet
|| [[#t16:46:20|16:46]]
|- id="t16:46:53"
! style="background-color: #407a40" | jlaska
| style="color: #407a40" | The live install experience has become pretty annoying ... not sure if other see that as well
|| [[#t16:46:53|16:46]]
|- id="t16:47:31"
! style="background-color: #407a40" | jlaska
| style="color: #407a40" | in that nautilus windows keep popping up while you're formatting the disks (bug#527091)
|| [[#t16:47:31|16:47]]
|- id="t16:47:33"
! style="background-color: #97974f" | buggbot
| style="color: #97974f" | Bug https://bugzilla.redhat.com/bugzilla/show_bug.cgi?id=527091 medium, low, ---, anaconda-maint-list, NEW, Installer causes a number of popups when creating filesystems
|| [[#t16:47:33|16:47]]
|- id="t16:47:43"
! style="background-color: #9b519b" | poelcat
| style="color: #9b519b" | jlaska: should 510249 be a beta blocker?
|| [[#t16:47:43|16:47]]
|- id="t16:47:53"
| colspan="2" | * poelcat read the bug last night... wasn't sure
|| [[#t16:47:53|16:47]]
|- id="t16:48:12"
! style="background-color: #407a40" | jlaska
| style="color: #407a40" | poelcat: that's the one from the thread adamw noted
|| [[#t16:48:12|16:48]]
|- id="t16:48:35"
! style="background-color: #9b519b" | poelcat
| style="color: #9b519b" | right... it's blocking final, but not beta
|| [[#t16:48:35|16:48]]
|- id="t16:49:18"
! style="background-color: #407a40" | jlaska
| style="color: #407a40" | claimed fixed for Alpha, then reopened it seems
|| [[#t16:49:18|16:49]]
|- id="t16:49:41"
! style="background-color: #407a40" | jlaska
| style="color: #407a40" | someone want to take an action on this to follow-up w/ mclasen on this bug?
|| [[#t16:49:41|16:49]]
|- id="t16:51:08"
| colspan="2" | * poelcat will post to f-desktop-list
|| [[#t16:51:08|16:51]]
|- id="t16:51:36"
! style="background-color: #407a40" | jlaska
| style="color: #407a40" | #action poelcat to check in on beta blocker status of 510249
|| [[#t16:51:36|16:51]]
|- id="t16:51:39"
! style="background-color: #407a40" | jlaska
| style="color: #407a40" | poelcat: thx!
|| [[#t16:51:39|16:51]]
|- id="t16:51:52"
! style="background-color: #407a40" | jlaska
| style="color: #407a40" | there are several other action items we addressed in the Friday bug meeting ... https://www.redhat.com/archives/fedora-test-list/2009-October/msg00046.html
|| [[#t16:51:52|16:51]]
|- id="t16:52:55"
! style="background-color: #407a40" | jlaska
| style="color: #407a40" | in response to that meeting ... there is a new NM available for testing from dcbw (see https://www.redhat.com/archives/fedora-devel-list/2009-October/msg00154.html)
|| [[#t16:52:55|16:52]]
|- id="t16:53:01"
! style="background-color: #407a40" | jlaska
| style="color: #407a40" | testing against that would be appreciated!
|| [[#t16:53:01|16:53]]
|- id="t16:53:59"
! style="background-color: #407a40" | jlaska
| style="color: #407a40" | any other beta concerns not currently on the list?
|| [[#t16:53:59|16:53]]
|- id="t16:54:33"
! style="background-color: #488888" | Oxf13
| style="color: #488888" | I need to get a new fedora-release out there
|| [[#t16:54:33|16:54]]
|- id="t16:54:38"
! style="background-color: #488888" | Oxf13
| style="color: #488888" | forgot to do that
|| [[#t16:54:38|16:54]]
|- id="t16:54:42"
! style="background-color: #407a40" | jlaska
| style="color: #407a40" | wwoods: I noticed that irb.com still has the Oct 02 images ... I gather rawhide hasn't built since then?
|| [[#t16:54:42|16:54]]
|- id="t16:55:02"
! style="background-color: #488888" | Oxf13
| style="color: #488888" | today has been built, but it is taking a long time to sync
|| [[#t16:55:02|16:55]]
|- id="t16:55:04"
! style="background-color: #488888" | Oxf13
| style="color: #488888" | due to signed rpms
|| [[#t16:55:04|16:55]]
|- id="t16:55:11"
! style="background-color: #407a40" | jlaska
| style="color: #407a40" | Oxf13: gotcha, thx
|| [[#t16:55:11|16:55]]
|- id="t16:56:17"
! style="background-color: #8c4a4a" | wwoods
| style="color: #8c4a4a" | jlaska: that'd be my first guess
|| [[#t16:56:17|16:56]]
|- id="t16:56:47"
! style="background-color: #407a40" | jlaska
| style="color: #407a40" | wwoods: did you or skvidal have any thoughts on that F-11 preupgrade bug that F-12-Beta testers would hit?
|| [[#t16:56:47|16:56]]
|- id="t16:57:00"
! style="background-color: #4b904b" | skvidal
| style="color: #4b904b" | jlaska: which one
|| [[#t16:57:00|16:57]]
|- id="t16:57:04"
! style="background-color: #8c4a4a" | wwoods
| style="color: #8c4a4a" | haven't had time to trace it
|| [[#t16:57:04|16:57]]
|- id="t16:57:15"
! style="background-color: #4b904b" | skvidal
| style="color: #4b904b" | jlaska:  there are 2 bugs I've seen
|| [[#t16:57:15|16:57]]
|- id="t16:57:21"
! style="background-color: #407a40" | jlaska
| style="color: #407a40" | I think it's bug#526208
|| [[#t16:57:21|16:57]]
|- id="t16:57:22"
! style="background-color: #97974f" | buggbot
| style="color: #97974f" | Bug https://bugzilla.redhat.com/bugzilla/show_bug.cgi?id=526208 low, low, ---, skvidal, ASSIGNED, preupgrade failed from old release(f10, f11)
|| [[#t16:57:22|16:57]]
|- id="t16:57:27"
! style="background-color: #4b904b" | skvidal
| style="color: #4b904b" | 1. is the doesn't-update-display thing that wwoods mentioned
|| [[#t16:57:27|16:57]]
|- id="t16:57:29"
! style="background-color: #8c4a4a" | wwoods
| style="color: #8c4a4a" | that's the UI-hang bug
|| [[#t16:57:29|16:57]]
|- id="t16:57:36"
! style="background-color: #407a40" | jlaska
| style="color: #407a40" | wwoods: yeah, that's the one
|| [[#t16:57:36|16:57]]
|- id="t16:57:43"
! style="background-color: #4b904b" | skvidal
| style="color: #4b904b" | 2. is the createrepo/yum bug if they are not using latest yum
|| [[#t16:57:43|16:57]]
|- id="t16:58:15"
! style="background-color: #4b904b" | skvidal
| style="color: #4b904b" | wwoods: I find 1 odd - I thought it might be a urlgrabber thing but if you can make it happen on pure f11 then not so much
|| [[#t16:58:15|16:58]]
|- id="t16:58:32"
! style="background-color: #8c4a4a" | wwoods
| style="color: #8c4a4a" | yeah, plain uptodate F11
|| [[#t16:58:32|16:58]]
|- id="t16:59:22"
! style="background-color: #407a40" | jlaska
| style="color: #407a40" | adamw: should bug#526535 be moved to MODIFIED now?
|| [[#t16:59:22|16:59]]
|- id="t16:59:23"
! style="background-color: #97974f" | buggbot
| style="color: #97974f" | Bug https://bugzilla.redhat.com/bugzilla/show_bug.cgi?id=526535 medium, low, ---, dcbw, NEW, [abrt] crash detected in NetworkManager-gnome-1:0.7.996-3.git20090928.fc12
|| [[#t16:59:23|16:59]]
|- id="t16:59:40"
! style="background-color: #818144" | adamw
| style="color: #818144" | jlaska: we're working on the tagging status
|| [[#t16:59:40|16:59]]
|- id="t17:00:01"
! style="background-color: #407a40" | jlaska
| style="color: #407a40" | for my own clarification ... it can't go into MODIFIED unless it's also tagged?
|| [[#t17:00:01|17:00]]
|- id="t17:00:03"
! style="background-color: #818144" | adamw
| style="color: #818144" | jlaska: i'm not sure when we should use MODIFIED when we're in a freeze situation...
|| [[#t17:00:03|17:00]]
|- id="t17:00:03"
! style="background-color: #4b904b" | skvidal
| style="color: #4b904b" | wwoods: I'll make the bizarro bug my main problem today
|| [[#t17:00:03|17:00]]
|- id="t17:00:10"
! style="background-color: #818144" | adamw
| style="color: #818144" | jlaska: i'm not sure either :)
|| [[#t17:00:10|17:00]]
|- id="t17:00:45"
! style="background-color: #407a40" | jlaska
| style="color: #407a40" | skvidal: wwoods: thanks gents
|| [[#t17:00:45|17:00]]
|- id="t17:01:26"
! style="background-color: #407a40" | jlaska
| style="color: #407a40" | Oxf13: do you have any take on the tagging and MODIFIED bz state?
|| [[#t17:01:26|17:01]]
|- id="t17:02:14"
! style="background-color: #407a40" | jlaska
| style="color: #407a40" | I would think we can mark it as MODIFIED if a package is built, but it can't be tested (and therefore CLOSED RAWHIDE) until it's tagged and readily available.  Is that wrong?
|| [[#t17:02:14|17:02]]
|- id="t17:02:15"
! style="background-color: #488888" | Oxf13
| style="color: #488888" | my take is that MODIFIED means something changed, either upstream or locally, but it hasn't been confirmed or built/tagged for rawhide
|| [[#t17:02:15|17:02]]
|- id="t17:02:26"
! style="background-color: #488888" | Oxf13
| style="color: #488888" | just don't /close/ anything unless it gets tagged
|| [[#t17:02:26|17:02]]
|- id="t17:02:32"
! style="background-color: #407a40" | jlaska
| style="color: #407a40" | agreed
|| [[#t17:02:32|17:02]]
|- id="t17:03:02"
! style="background-color: #407a40" | jlaska
| style="color: #407a40" | adamw: any objections?
|| [[#t17:03:02|17:03]]
|- id="t17:03:43"
! style="background-color: #8c4a4a" | wwoods
| style="color: #8c4a4a" | (insert caveats about preupgrade fixes not requiring f12 tags per se here)
|| [[#t17:03:43|17:03]]
|- id="t17:03:53"
! style="background-color: #407a40" | jlaska
| style="color: #407a40" | wwoods: true, good point
|| [[#t17:03:53|17:03]]
|- id="t17:04:36"
! style="background-color: #818144" | adamw
| style="color: #818144" | jlaska: um. that's probably okay. you can argue it either way, really. just pick an answer and write it down in the lifecycle page :)
|| [[#t17:04:36|17:04]]
|- id="t17:05:01"
! style="background-color: #407a40" | jlaska
| style="color: #407a40" | adamw: cool, I think we have one then
|| [[#t17:05:01|17:05]]
|- id="t17:05:20"
! style="background-color: #407a40" | jlaska
| style="color: #407a40" | there's a gap here that leaves ambiguity, but that's not something I'm interested in touching on at the moment
|| [[#t17:05:20|17:05]]
|- id="t17:05:39"
! style="background-color: #407a40" | jlaska
| style="color: #407a40" | Alrighty ... let's move on to a quick recap of upcoming events
|| [[#t17:05:39|17:05]]
|- id="t17:05:46"
! style="background-color: #407a40" | jlaska
| style="color: #407a40" | #topic Upcoming QA events
|| [[#t17:05:46|17:05]]
|- id="t17:06:12"
! style="background-color: #407a40" | jlaska
| style="color: #407a40" | All of the discussion for the last 25 minutes has been around the beta go / no_go meeting coming up in 1 hour
|| [[#t17:06:12|17:06]]
|- id="t17:06:15"
! style="background-color: #407a40" | jlaska
| style="color: #407a40" | Beta Blocker Bug (go/no go) - Mon 2009-10-05
|| [[#t17:06:15|17:06]]
|- id="t17:06:29"
! style="background-color: #407a40" | jlaska
| style="color: #407a40" | based on the outcome of that meeting, we may or may not have a ...
|| [[#t17:06:29|17:06]]
|- id="t17:06:32"
! style="background-color: #407a40" | jlaska
| style="color: #407a40" | * Beta Project Wide Release Readiness Meeting - Wed 2009-10-07
|| [[#t17:06:32|17:06]]
|- id="t17:06:50"
! style="background-color: #407a40" | jlaska
| style="color: #407a40" | however, either way ... we've got another test day queued up for this thursday
|| [[#t17:06:50|17:06]]
|- id="t17:06:53"
! style="background-color: #407a40" | jlaska
| style="color: #407a40" | * RAID Test Day - Thu 2009-10-08
|| [[#t17:06:53|17:06]]
|- id="t17:07:19"
! style="background-color: #407a40" | jlaska
| style="color: #407a40" | If anyone has dmraid hardware, we could use your feedback this thursday
|| [[#t17:07:19|17:07]]
|- id="t17:07:29"
! style="background-color: #407a40" | jlaska
| style="color: #407a40" | (or any hardware RAID for that matter)
|| [[#t17:07:29|17:07]]
|- id="t17:08:01"
! style="background-color: #407a40" | jlaska
| style="color: #407a40" | So that's all I have listed for upcoming events ... let's move on to 'open floor'
|| [[#t17:08:01|17:08]]
|- id="t17:08:10"
! style="background-color: #407a40" | jlaska
| style="color: #407a40" | #topic Open floor - &lt;insert your topic&gt;
|| [[#t17:08:10|17:08]]
|- id="t17:08:24"
! style="background-color: #407a40" | jlaska
| style="color: #407a40" | Any items folks would like to discuss during the meeting?
|| [[#t17:08:24|17:08]]
|- id="t17:10:23"
! style="background-color: #407a40" | jlaska
| style="color: #407a40" | quiet ... I'm assuming folks went off for some lunch before the rel-eng meeting then
|| [[#t17:10:23|17:10]]
|- id="t17:10:37"
! style="background-color: #488888" | Oxf13
| style="color: #488888" | something like that
|| [[#t17:10:37|17:10]]
|- id="t17:11:22"
! style="background-color: #818144" | adamw
| style="color: #818144" | i am just aiming not to prolong the meeting :)
|| [[#t17:11:22|17:11]]
|- id="t17:11:34"
! style="background-color: #407a40" | jlaska
| style="color: #407a40" | alrighty ... let's close it out then
|| [[#t17:11:34|17:11]]
|- id="t17:11:36"
| colspan="2" | * kparal1 still here, but no issues
|| [[#t17:11:36|17:11]]
|- id="t17:11:39"
! style="background-color: #407a40" | jlaska
| style="color: #407a40" | please follow-up to the list for any other concerns
|| [[#t17:11:39|17:11]]
|- id="t17:12:05"
! style="background-color: #407a40" | jlaska
| style="color: #407a40" | thanks for baring with me through the slooooow bug review part of todays meeting :)
|| [[#t17:12:05|17:12]]
|- id="t17:12:11"
! style="background-color: #407a40" | jlaska
| style="color: #407a40" | #endmeetings
|| [[#t17:12:11|17:12]]
|- id="t17:12:13"
! style="background-color: #407a40" | jlaska
| style="color: #407a40" | #endmeeting
|| [[#t17:12:13|17:12]]
|}
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 20:21, 5 October 2009

Attendees

People Present (lines said):

  • jlaska (111)
  • adamw (38)
  • wwoods (25)
  • Oxf13 (24)
  • kparal1 (17)
  • skvidal (15)
  • buggbot (5)
  • poelcat (4)
  • zodbot (2)
  • brunowolff_ (1)
  • Sir_Limpsalot (1)

Regrets:

  • Liam Li (lili)
  • He Rui (rhe)
  • David Pravec (dpravec)


Agenda

Preview Meeting follow-up

http://meetbot.fedoraproject.org/fedora-meeting/2009-09-28/fedora-meeting.2009-09-28-16.00.html

Anaconda dependency follow-up

Adamw reminded the group that we hadn't yet followed up on the previous topic raised by dpravec around installer dependencies changing out from under it.

F13 noted that there were discussions with RHT management reminding folks that it was too late to make general (or feature) changes in F-12.

Jlaska asked what specific issues initiated this discussion. Adamw and f13 noted the recent nfs the lvm changes.

AutoQA update

Wwoods wired up the UI, so members of the 'qa' group can now add/remove test results for the manual tests (see [http://wwoods.fedorapeople.org/screenshots/irb.png screenshot). Also decided to defer:

  1. sweet ajax UI junk and
  2. automating the yum/network tests until after irb.com completes

Reminder of the current roadmap: https://fedorahosted.org/autoqa/milestone/israwhidebroken.com. Current tasks include:

  1. get links back from israwhidebroken to autotest
  2. get it all running in production in public

Jlaska took an action item to sync up w/ mmcgrath to identify next steps when the AutoQA hardware arrives in PHX2.

Packagediff update

Next, kparal updated the group on his packagediff activities. The intention is to alert on important changes between packages, hopefully part of autoqa project in the future.

Currently working 2 tickets:

  1. https://fedorahosted.org/autoqa/ticket/53 - Investigate what rpmdiff offers to our tests
  2. https://fedorahosted.org/autoqa/ticket/54 - Write rpmdiff test

The code currently highlights changed dependencies, changed config files, changed file modes and such stuff. Wwoods suggested also falgging added/removed binaries.

Some discussion surfaced around whether Kparal's efforts were based on an older RHT internal project called 'rpmdiff'. Kparal's efforts are entirely based on the rpmlint implementation of rpmdiff. Kparal is currently waiting for some feedback on a few rpmdiff issues. Skvidal recommended reaching out to ville skytta.

F-12-Beta QA Readiness

Jlaska asked the team for help preparing for the upcoming Go/No Go decision at the upcoming rel-eng meeting. The team informally walked the remaining F12Beta blocker bugs.

F13 asked if any blocker bug candidates came out of the Test Day. Aside from RHBZ #517260 it wasn't clear yet whether any of the recorded test day bugs (https://www.redhat.com/archives/fedora-test-list/2009-October/msg00058.html) where beta blockers. Jlaska took an action item to catch up with clumens to help review the list. So far, the only Test day bugs raised to the beta blocker list are:

  • RHBZ #526842 ASSIGNED - Firstboot not run after installation
  • RHBZ #517260 ASSIGNED - liveinst fails at partitioning screeen
  • RHBZ #523862 CLOSED RAWHIDE - mdadm craps at boot

Adamw expressed concern around the missing panel icon bug noted on the list by Chuck Anderson (see https://www.redhat.com/archives/fedora-test-list/2009-October/msg00058.html). Turns out this is RHBZ #510249. Mclasen already evaluated and recommended fixing this issue post-Beta.

Jlaska asked for wwoods and skvidal expertise on rhe's preupgrade RHBZ #526208. It's a bug in the F-11 package, but would potentially impact anyone using preupgrade to upgrade from F-11 to F-12. Skvidal intended to investigate the UI issue after the meeting.

Jlaska asked if RHBZ #526535 should be moved into MODIFIED given a package was built and testing requested on fedora-devel-list (see https://www.redhat.com/archives/fedora-devel-list/2009-October/msg00154.html). Adamw asked what the policy is with regards to MODIFIED bugs. Does MODIFIED mean a package is built and a tag request is submitted? F13 proposed that MODIFIED means a fix is available, but not yet tested or included in the product. This seems to hold when adding the freeze 'tagging' procedure into the mix.

Upcoming QA events

Jlaska did a speedy walk through of upcoming QA related events

  • 2009-10-05 - F12 Beta go/no_go meeting (@ 18:00pm - rel-eng meeting)
  • 2009-10-06 - BugZappers/Meetings
  • 2009-10-07 - Beta Project Wide Release Readiness Meeting
  • 2009-10-08 - RAID Test Day
  • 2009-10-13 - F12 Beta availability

Open floor - <your topic here>

No open discussion topics were raised.

Action items

  1. jlaska to catch up with mmcgrath on delivery of autoqa hardware to PHX
  2. jlaska - sync-up with clumens to identify any blocking issues from https://www.redhat.com/archives/fedora-test-list/2009-October/msg00073.html
  3. poelcat to check in on beta blocker status of 510249

IRC transcript

jlaska #startmeeting Fedora QA meeting 16:00
zodbot Meeting started Mon Oct 5 16:00:39 2009 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 #topic Gathering able bodied persons 16:00
adamw morning 16:00
* kparal1 says hi 16:01
adamw that topic is discriminatory against disabled qa people. 16:01
adamw i say this only half in jest, because, well, it actually is =) 16:01
kparal1 but only for english people, i myself didn't get that :) 16:01
jlaska adamw: Well certainly no ill will intended ... of course will adjust in the future 16:02
adamw interesting where a running joke can get you, hehe 16:02
jlaska ;) 16:02
jlaska I thought I was safe not limiting the meeting to gender 16:03
adamw ah, it's never that easy 16:03
jlaska indeed 16:03
jlaska okay, who else do we have 16:03
adamw aaaaaanyway 16:03
jlaska I sense the presence of wwoods ... lurking in the shadows 16:03
* wwoods rolls a Stealth check 16:04
jlaska Oxf13 is around too I believe 16:04
* Oxf13 16:04
jlaska We'll be missing dpravec today 16:05
jlaska so let's get started 16:05
jlaska #topic Previous Meeting Follow-up 16:05
jlaska First ... an apology 16:05
jlaska there will only be 1 QA meeting right now ... contrary to the dueling agendas posted to the list 16:05
* adamw leads his followers to #confederate-fedora-meeting 16:06
jlaska adamw: take the action items with you please! 16:06
adamw =) 16:06
jlaska I didn't have any recorded action items from last weeks meeting 16:06
* jlaska looking at http://meetbot.fedoraproject.org/fedora-meeting/2009-09-28/fedora-meeting.2009-09-28-16.00.html 16:06
jlaska adamw: was there anything not recorded that you wanted to discuss from last week? 16:07
adamw nothing specific from last week that i can think of, but we could follow up on the discussion of development issues from a couple of weeks ago, now more people are here 16:07
adamw esp. oxf13 16:07
adamw Oxf13: you remember that? the talk about anaconda dependencies and rhel changes parachuted into fedora... 16:07
Oxf13 vaguely 16:08
adamw you mentioned there were meetings at which some of those issues could be raised - gone anywhere with that? 16:08
Oxf13 yeah, we re-affirmed to RHT management that it is too late to make feature changes in F12 16:09
adamw great 16:09
adamw was there any pushback? 16:09
Oxf13 not yet 16:10
jlaska I don't have the full history of this discussion topic ... was this anaconda specific ... or general changes? 16:10
adamw jlaska: it was a wide-ranging discussion :) 16:10
jlaska that's my guess based on recent f-d-list threads 16:11
adamw jlaska: it started with someone (dpravec iirc) raising anaconda team's concerns that things anaconda depended on were being changed in major ways too close to the beta 16:11
Oxf13 eg nfs 16:11
jlaska gotcha .. yeah a fair concern 16:11
adamw it broadened out a bit from there into general issues causing undesirable changes in late pre-pre-release phases 16:11
jlaska lvm 16:11
adamw yeah that stuff 16:12
Oxf13 right and lvm 16:12
adamw though the discussion was right before the lvm storm broke iirc 16:12
jlaska dcantrell has some interesting testing that's maturing ... but could potentially be used to highlight these types of issues in the future 16:12
jlaska might be worth having a presentation/discussion as his tests mature at FUDCon perhaps 16:13
adamw roger 16:13
jlaska certainly won't solve all the worlds problems, but might help give the anaconda team a heads up when things they rely on are changed out from under them 16:13
jlaska #idea How can the QA team support dcantrell's anaconda A[BP]I checking routines 16:14
jlaska any other points on this topic? 16:14
jlaska if so ... we might choose to make this a repeating topic 16:15
adamw i'd rather not, meetings are long enough as it isw 16:15
adamw i just wanted to follow up on the discussion, and we couldn't do it last week as jesse wasn't here 16:15
jlaska roger 16:15
jlaska alrighty ... next up we've got a quick check-in on the AutoQA front 16:16
jlaska #topic AutoQA update 16:16
jlaska wwoods: you've got the floor 16:16
wwoods let's see 16:16
wwoods last week I wired up the UI, so members of the 'qa' group can now add/remove test results for the manual tests 16:17
wwoods (this is for the israwhidebroken mini-frontend) 16:17
jlaska #link http://wwoods.fedorapeople.org/screenshots/irb.png 16:17
wwoods we decided to defer a) sweet ajax UI junk and b) automating the yum/network tests until later 16:18
wwoods so here's the current roadmap: https://fedorahosted.org/autoqa/milestone/israwhidebroken.com 16:18
wwoods basically it comes down to: 1) get links back from israwhidebroken to autotest 16:18
wwoods and then 2) get it all running in production in public 16:19
jlaska #action jlaska to catch up with mmcgrath on delivery of autoqa hardware to PHX 16:19
wwoods yeah there's rumors that our autoqa hardware may be arriving soon? 16:19
jlaska I got word on Friday that "it's in the mail" 16:20
wwoods nice 16:20
jlaska definitely! I took an action to sync up with infrastructure to figure out what we need to do once the hardware lands 16:20
wwoods so yeah, getting the backreferences to autotest turns out to be nontrivial but I've been talking with upstream and we'll work something out 16:21
wwoods after that it's all ready to go into "production" 16:21
* jlaska queues the suspense music 16:21
wwoods for values of "production" roughly equal to "public early beta" 16:21
wwoods still: woo! 16:22
jlaska right on ... I second that 'woo' 16:22
wwoods think that's all from mem 16:22
wwoods err, me 16:22
jlaska wwoods: thanks for the update! 16:22
jlaska kparal1: any updates on the packagediff piece you're investigating? 16:22
kparal1 well, i have started to write a test for comparing old and new rpm package 16:23
kparal1 it will be hopefully part of autqa in the future 16:23
kparal1 the intention is to alert on important changes between packages 16:23
kparal1 currently i'm announcing changed dependencies, changed config files, changed file modes and such stuff 16:24
wwoods nice! 16:24
kparal1 developing goes slowly because i can't devote it much time but i hope it will be usable soon 16:25
wwoods adding/removing binaries should definitely be announced as well 16:25
kparal1 yes, that's in the plan: https://fedorahosted.org/autoqa/ticket/53 16:25
* wwoods reviews 16:25
kparal1 you can see my code, i have put it online: https://fedorahosted.org/autoqa/ticket/54 16:25
wwoods pretty sure we talked about all that stuff before so I'm sure it's all here 16:25
kparal1 it's just a first shot and i'm learning python with it, so be mercifull :) 16:26
kparal1 i think that's all from me 16:26
jlaska kparal1: hah! you've taken on quite a challenge for first time python (e.g. rpm libs) 16:26
kparal1 also there are some bugs waiting in rpmdiff to be fixed, but the rpmlint project seems a little dead now (trac not working properly, mailing list halted) 16:27
kparal1 but hopefully skvidal will help me with that 16:27
* skvidal looks up 16:27
skvidal kparal1: ah yes - your email from last week 16:28
Oxf13 kparal1: is this working from existing rpmdiff code? 16:28
skvidal Oxf13: not the rhel rpmdiff 16:28
Oxf13 right 16:28
skvidal Oxf13: the rpmlint, rpmdiff 16:28
Oxf13 that one is still closed 16:28
kparal1 Oxf13: yes, i'm using the public rpmdiff in my script 16:28
Oxf13 *stab* 16:28
skvidal Oxf13: and will, afaict, never be opened 16:28
jlaska in my best ed mcmahon "you sir, are correct sir" 16:29
skvidal kparal1: I think I should talk to Ville - see if he has any thoughts 16:29
kparal1 Ville is irc nick? 16:29
skvidal jlaska: you realize how old that makes you sound that 1. you know who ed mcmahon is 2. you know who he would say that to 3. you know the snl bit about that 16:29
skvidal kparal1: he's almost never on irc - ville skytta 16:29
jlaska skvidal: ;) 16:29
kparal1 skvidal: ok, thx 16:29
skvidal kparal1: when he is on irc he's scop 16:30
jlaska alrighty ... aside from just a quick run through of upcoming QA events ... I wanted to spend some time surveying the group for our Beta readiness 16:31
jlaska #topic F-12-Beta QA readiness 16:31
jlaska Oxf13 will be hosting a go/no_go discussion on the beta today during the rel-eng meeting (@ 18:00 UTC) 16:31
jlaska but I thought we could spend a few minutes here making sure that all the _hot_ issues are on the radar ... and see if anything is stuck in process 16:31
Oxf13 looking pretty no-go at this point 16:32
adamw yeah, not much movement on bugs over the weekend :/ 16:32
jlaska pulling up the F12Beta blocker bug report ... 16:32
jlaska https://bugzilla.redhat.com/showdependencytree.cgi?id=F12Beta&hide_resolved=1 16:32
Oxf13 still no first boot, nm-gnome crashes, ppc64 netboot missing, and aliveinst failure? 16:32
brunowolff_ mdadm got fixed 16:32
Oxf13 adamw: party my fault. I didn't look at the tag queue last night, got tied up with family stuff 16:32
jlaska and the util-linux-ng issue has a build+tag request in I believe 16:33
Oxf13 yeah, some stuff needs testing to clear the tag queue 16:33
adamw hum 16:33
adamw important point: that's an entirely different networkmanager crash report from the one we worked on in the meeting 16:34
adamw it's been tagged as a blocker independently 16:34
adamw may be a dupe of the other report 16:34
adamw i will check 16:34
Oxf13 ok 16:34
jlaska while adamw's looking for that NM issue ... are there any other bugs that aren't represented on the current blocker list that folks are concerned about? 16:35
adamw that 'invisible icons' bug from the list looks icky 16:37
adamw though i'm not clear on the exact symptoms 16:37
Oxf13 jlaska: anything come up in the anaconda test day? 16:38
jlaska https://www.redhat.com/archives/fedora-test-list/2009-October/msg00058.html 16:38
* Sir_Limpsalot sneaks inn.. 16:38
Oxf13 as far as blocker worthy bugs 16:39
jlaska Oxf13: a few bugs ... but don't have enough info yet as to whether they are common or exceptions 16:40
adamw hi there 16:40
jlaska we have the ongoing pain with yaboot not properly booting after some scenarios (bug#523754) 16:40
buggbot Bug https://bugzilla.redhat.com/bugzilla/show_bug.cgi?id=523754 is not accessible. 16:40
jlaska hmm, that's not the right bz ... try bug#523754 16:41
jlaska oh perms on the bz ... odd 16:41
adamw that's the same number you just said 16:41
jlaska sure is :) 16:41
jlaska there's a few like that against Fedora ... specific to ppc ... and I Think they're all related to the same core yaboot issue 16:42
jlaska this is going off my gut feel from testing, so could be wrong 16:42
jlaska it's not a new problem though, so I wouldn't raise this is a beta blocker 16:42
jlaska it looks like the anaconda-devel team has already started working the test day bugs ... I'll see if I can get clumens to help identify and alarming storage issues in the list 16:43
jlaska #action jlaska - sync-up with clumens to identify any blocking issues from https://www.redhat.com/archives/fedora-test-list/2009-October/msg00073.html 16:44
jlaska there were a few RAID related issues, but as brunowolff_ said ... a fix is already tagged for that 16:44
jlaska adamw: anything else on the invisible icon thread? https://www.redhat.com/archives/fedora-test-list/2009-October/msg00058.html 16:45
jlaska mclasen called out bug#510249 on this issue 16:45
buggbot Bug https://bugzilla.redhat.com/bugzilla/show_bug.cgi?id=510249 medium, low, ---, mclasen, ASSIGNED, Missing panel applets on gnome login; "Glib-GObject-CRITICAL" messages.... 16:46
jlaska which is currently marked as a F12Blocker 16:46
adamw jlaska: no, i just saw it this morning, haven't looked into it much yet 16:46
jlaska The live install experience has become pretty annoying ... not sure if other see that as well 16:46
jlaska in that nautilus windows keep popping up while you're formatting the disks (bug#527091) 16:47
buggbot Bug https://bugzilla.redhat.com/bugzilla/show_bug.cgi?id=527091 medium, low, ---, anaconda-maint-list, NEW, Installer causes a number of popups when creating filesystems 16:47
poelcat jlaska: should 510249 be a beta blocker? 16:47
* poelcat read the bug last night... wasn't sure 16:47
jlaska poelcat: that's the one from the thread adamw noted 16:48
poelcat right... it's blocking final, but not beta 16:48
jlaska claimed fixed for Alpha, then reopened it seems 16:49
jlaska someone want to take an action on this to follow-up w/ mclasen on this bug? 16:49
* poelcat will post to f-desktop-list 16:51
jlaska #action poelcat to check in on beta blocker status of 510249 16:51
jlaska poelcat: thx! 16:51
jlaska there are several other action items we addressed in the Friday bug meeting ... https://www.redhat.com/archives/fedora-test-list/2009-October/msg00046.html 16:51
jlaska in response to that meeting ... there is a new NM available for testing from dcbw (see https://www.redhat.com/archives/fedora-devel-list/2009-October/msg00154.html) 16:52
jlaska testing against that would be appreciated! 16:53
jlaska any other beta concerns not currently on the list? 16:53
Oxf13 I need to get a new fedora-release out there 16:54
Oxf13 forgot to do that 16:54
jlaska wwoods: I noticed that irb.com still has the Oct 02 images ... I gather rawhide hasn't built since then? 16:54
Oxf13 today has been built, but it is taking a long time to sync 16:55
Oxf13 due to signed rpms 16:55
jlaska Oxf13: gotcha, thx 16:55
wwoods jlaska: that'd be my first guess 16:56
jlaska wwoods: did you or skvidal have any thoughts on that F-11 preupgrade bug that F-12-Beta testers would hit? 16:56
skvidal jlaska: which one 16:57
wwoods haven't had time to trace it 16:57
skvidal jlaska: there are 2 bugs I've seen 16:57
jlaska I think it's bug#526208 16:57
buggbot Bug https://bugzilla.redhat.com/bugzilla/show_bug.cgi?id=526208 low, low, ---, skvidal, ASSIGNED, preupgrade failed from old release(f10, f11) 16:57
skvidal 1. is the doesn't-update-display thing that wwoods mentioned 16:57
wwoods that's the UI-hang bug 16:57
jlaska wwoods: yeah, that's the one 16:57
skvidal 2. is the createrepo/yum bug if they are not using latest yum 16:57
skvidal wwoods: I find 1 odd - I thought it might be a urlgrabber thing but if you can make it happen on pure f11 then not so much 16:58
wwoods yeah, plain uptodate F11 16:58
jlaska adamw: should bug#526535 be moved to MODIFIED now? 16:59
buggbot Bug https://bugzilla.redhat.com/bugzilla/show_bug.cgi?id=526535 medium, low, ---, dcbw, NEW, [abrt] crash detected in NetworkManager-gnome-1:0.7.996-3.git20090928.fc12 16:59
adamw jlaska: we're working on the tagging status 16:59
jlaska for my own clarification ... it can't go into MODIFIED unless it's also tagged? 17:00
adamw jlaska: i'm not sure when we should use MODIFIED when we're in a freeze situation... 17:00
skvidal wwoods: I'll make the bizarro bug my main problem today 17:00
adamw jlaska: i'm not sure either :) 17:00
jlaska skvidal: wwoods: thanks gents 17:00
jlaska Oxf13: do you have any take on the tagging and MODIFIED bz state? 17:01
jlaska I would think we can mark it as MODIFIED if a package is built, but it can't be tested (and therefore CLOSED RAWHIDE) until it's tagged and readily available. Is that wrong? 17:02
Oxf13 my take is that MODIFIED means something changed, either upstream or locally, but it hasn't been confirmed or built/tagged for rawhide 17:02
Oxf13 just don't /close/ anything unless it gets tagged 17:02
jlaska agreed 17:02
jlaska adamw: any objections? 17:03
wwoods (insert caveats about preupgrade fixes not requiring f12 tags per se here) 17:03
jlaska wwoods: true, good point 17:03
adamw jlaska: um. that's probably okay. you can argue it either way, really. just pick an answer and write it down in the lifecycle page :) 17:04
jlaska adamw: cool, I think we have one then 17:05
jlaska there's a gap here that leaves ambiguity, but that's not something I'm interested in touching on at the moment 17:05
jlaska Alrighty ... let's move on to a quick recap of upcoming events 17:05
jlaska #topic Upcoming QA events 17:05
jlaska All of the discussion for the last 25 minutes has been around the beta go / no_go meeting coming up in 1 hour 17:06
jlaska Beta Blocker Bug (go/no go) - Mon 2009-10-05 17:06
jlaska based on the outcome of that meeting, we may or may not have a ... 17:06
jlaska * Beta Project Wide Release Readiness Meeting - Wed 2009-10-07 17:06
jlaska however, either way ... we've got another test day queued up for this thursday 17:06
jlaska * RAID Test Day - Thu 2009-10-08 17:06
jlaska If anyone has dmraid hardware, we could use your feedback this thursday 17:07
jlaska (or any hardware RAID for that matter) 17:07
jlaska So that's all I have listed for upcoming events ... let's move on to 'open floor' 17:08
jlaska #topic Open floor - <insert your topic> 17:08
jlaska Any items folks would like to discuss during the meeting? 17:08
jlaska quiet ... I'm assuming folks went off for some lunch before the rel-eng meeting then 17:10
Oxf13 something like that 17:10
adamw i am just aiming not to prolong the meeting :) 17:11
jlaska alrighty ... let's close it out then 17:11
* kparal1 still here, but no issues 17:11
jlaska please follow-up to the list for any other concerns 17:11
jlaska thanks for baring with me through the slooooow bug review part of todays meeting :) 17:12
jlaska #endmeetings 17:12
jlaska #endmeeting 17:12

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/20091005&oldid=128350"