16:00:24 #startmeeting Fedora QA meeting 16:00:24 Meeting started Mon Dec 17 16:00:24 2012 UTC. The chair is adamw. Information about MeetBot at http://wiki.debian.org/MeetBot. 16:00:24 Useful Commands: #action #agreed #halp #info #idea #link #topic. 16:00:28 #meetingname fedora-qa 16:00:28 The meeting name has been set to 'fedora-qa' 16:00:30 #topic roll call 16:00:58 * jsmith is here 16:01:08 * mkrizek is here 16:01:10 * satellit listening 16:01:22 * kparal around 16:01:33 * tflink is here 16:02:21 morning all 16:03:37 * jreznik is here 16:05:01 #topic previous meeting follow-up 16:05:06 #chair kparal tflink 16:05:06 Current chairs: adamw kparal tflink 16:05:15 * pschindl is here 16:05:55 "tflink to clarify use of his fedup side repo" 16:06:04 * adamw doesn't quite recall what that was in relation to, tflink? 16:06:46 this was people using the siderepo on my fedorapeople account for actual upgrades, not just upgrade testing 16:07:11 I added a warning to the wiki page containing the url to that repo 16:07:35 tflink: which page? 16:08:16 oh right. good 16:08:36 kparal: https://fedoraproject.org/wiki/QA:Fedora_18_Upgrade_Testing 16:08:43 #info "tflink to clarify use of his fedup side repo" this was done - warning added to https://fedoraproject.org/wiki/QA:Fedora_18_Upgrade_Testing 16:09:03 "viking-ice to let docs team know about advanced storage for release notes" 16:09:05 ah, that's the one I couldn't find today 16:09:07 which is horribly out of date at this point 16:09:17 we appear to be be short one viking this morning, but lemme check the archives 16:10:12 i don't see anything relating to this in the docs list archive 16:10:45 #info "viking-ice to let docs team know about advanced storage for release notes" - viking-ice not present, no indication in docs list archive that this was done 16:10:46 let's roll the action item over for next week 16:10:51 #action viking-ice to let docs team know about advanced storage for release notes 16:11:02 "adamw to put packaging error criterion revision into production" 16:11:22 this is done. the pause at the start of the meeting was not IN ANY WAY AT ALL to do with me doing this. *koff* 16:11:33 #info "adamw to put packaging error criterion revision into production" - this is done 16:12:24 "kparal to follow up on test@ discussion to explain the plan, and let anaconda team know" - i believe this was in relation to kickstart 16:12:54 yes, I replied to the test list and I'll revive the thread and notify anaconda-devel once F18 is out 16:13:00 coolbeans 16:13:08 #info "kparal to follow up on test@ discussion to explain the plan, and let anaconda team know" - kparal has this in hand, test@ was notified 16:14:06 #topic Fedora 18 Final status and blocker review 16:14:14 #info TC2 is out 16:14:28 #info there is a signed shim and various other changes (new anaconda included) we need to get into a TC3 today 16:14:54 I think that both releng and I had issues getting TC3 (ish) to build 16:14:56 #info blocker list is still considerable, i will send out a blocker status mail later today 16:15:03 yeah, i know, that's why it didn't happen yet 16:15:24 lorax complaining about nothing providing shim even though shim-signed does, right? 16:15:32 ok, I didn't end up figuring out why a smoke build didn't work but it sounded like dgilmore understood what was going on a bit better than I did 16:15:37 i don't know why no-one just slapped together a lorax that looked for shim-signed, but hey. 16:15:44 I haven't looked at it since friday night, don't remember 100% ATM 16:15:55 so anyway, we'll clear that up today and get rolling 16:16:21 tflink: i know whats going on should have a fix soon 16:16:31 dgilmore: cool, thanks 16:16:35 dgilmore: awesome to hear 16:16:43 #info dgilmore is on top of tc3 compose problems 16:16:59 should have it this morning 16:17:32 we also have concerns about fedup secure/media-based upgrades, though i guess we can kick that to fesco 16:17:38 I have a subtopic before we move on to blocker review 16:17:41 ok 16:18:31 which is blocker/NTH review - I'm starting to wonder if we just need to have daily meetings until we get through them all since we're so close to release 16:18:47 ... and remove all sharp/dangerous objects from the people in those meetings 16:19:02 s/from/from around/ 16:19:09 it's a terrible idea but better than any other terrible idea i can think of. 16:19:18 we at least need to knock off all the proposed blockers. 16:19:23 I don't like it either but I don't have a better solution right now 16:19:43 I really don't like the idea that we're not through the list this late 16:19:50 btw, a chunk of stuff on the proposed nth list is related, if you didn't catch that - dledford proposed a chunk of bugs related to two updates as nth 16:19:55 yeah, no, i agree 16:20:00 anyone have a less awful idea? 16:20:57 I don't really understand most of them, though - I assume you're talking about the rdma bugs? 16:21:22 ifcfg-ib etc. 16:21:42 yeah. we can talk about that when we get to it anyhow, but when we do, we should take 'em as a pack 16:23:11 unfortunately, I'm not hearing any counter-proposals :( 16:23:18 nope, so bureaucracy it is. 16:23:31 #info there will be daily blocker/nth review meetings this week to try and get through the backlog 16:24:01 on the bright side, I don't think that many NTHs will provoke long discussion 16:24:16 if we ever get to 'em. 16:24:28 for fedup, I just sent wwoods email to clarify media based upgrades... 16:24:33 so, any other general f18 status concerns/thoughts? 16:24:42 #info jreznik trying to clarify media-based upgrade status with wwoods 16:25:24 does being ready for release as planned count? 16:25:41 heh. 16:26:03 actually, shall we do what we did last week, and close this meeting before we do blocker review? 16:26:09 i just had open floor listed after this 16:26:19 works for me 16:27:06 adamw: +1 16:27:15 okay then 16:27:24 #info we'll finish this meeting then go on to blocker review in #fedora-qa 16:27:52 #topic Open floor 16:27:55 so...any other business? 16:30:16 apparently not! 16:30:28 i know this cycle is getting wearing...still, finish line is kinda in sight 16:30:38 pygobject3 16:30:47 oh, for firewalld? 16:30:53 it's on the NTH list, right? 16:30:58 no 16:31:09 yes 16:31:09 that's why I raised it now (or I'm just blind) 16:31:09 https://bugzilla.redhat.com/show_bug.cgi?id=874378 16:31:33 put that one on the nth-high-priority list tflink? 16:31:46 actually it'd be good to weed an NTH high-priority list in today's review 16:31:48 ok, it's still marked as firewalld 16:31:54 jreznik: there are two bugs 16:32:03 i picked that one for nth nomination more or less at random 16:32:13 adamw: yep, high prio as fesco request this to be in final 16:32:19 tflink: i think i already pulled in some proposed NTH fixes to TC requests, so be good to sign off on those 16:32:35 tflink: so, blocker review starting in -qa in a couple of minutes? 16:32:41 -bugzappers 16:32:42 Sorry was dealing with few issues @dayjob 16:32:43 ah 16:32:49 and thanks goes to halfline, the only one who offered the help to fix it :) 16:33:01 Viking-Ice: what's the status of your notifying-docs-team-about-advanced-storage action item? 16:33:55 adamw, I open a bug against documentation which is afaik the proper procedure to do so 16:34:01 ah, cool 16:34:19 885808 16:34:34 #info on action item "viking-ice to let docs team know about advanced storage for release notes" - viking opened a bug, 885808 16:34:48 i'm not gonna #undo all the way back there, but count it as done, i won't put it on next week's follow-up list 16:35:07 I expect the docs team to take it from there 16:35:08 blocker review in -bugzappers in a few minutes, everyone 16:35:12 * adamw sets fuse for 2 minutes 16:35:19 Viking-Ice: yup, sounds right to me 16:35:33 * jreznik is going to take a quick snack before blocker review 16:35:40 * Viking-Ice returns to work 16:36:16 jreznik: Good idea :-) 16:40:11 #endmeeting