15:10:57 #startmeeting fedora-qa-meeting 15:10:57 Meeting started Mon Aug 1 15:10:57 2011 UTC. The chair is jlaska. Information about MeetBot at http://wiki.debian.org/MeetBot. 15:10:57 Useful Commands: #action #agreed #halp #info #idea #link #topic. 15:11:02 #meetingname fedora-qa-meeting 15:11:02 The meeting name has been set to 'fedora-qa-meeting' 15:11:08 #topic Roll Call 15:11:16 * kparal present 15:11:17 * tflink present 15:11:18 * mkrizek is present 15:11:21 * j_dulaney waves from his flying unicorn 15:11:21 okay, raise your hand if you are here ... don't raise it if not here 15:11:23 * athmane is here 15:11:26 * robatino present 15:11:39 * pschindl is here 15:11:49 * jsmith lurks 15:12:09 * mbouffard here 15:12:24 Hello all, thanks for your patience waiting for #startmeeting 15:12:31 who are we missing? 15:12:46 Viking-Ice, jskladan? 15:12:55 iirc, adamw may be off today (public holiday) 15:13:03 * jskladan is here 15:13:06 hey there 15:13:20 okay, let's get started ... we have a light agenda so far, so this _may_ be quick 15:13:29 #topic Previous meeting follow-up 15:13:42 #info j_dulaney - Filing bugs for s-c-* desktop application duplicate names 15:13:58 j_dulaney: does this still need to be completed, are we still tracking this change? 15:14:14 Bug 727204 15:14:20 .Bug 727204 15:14:26 Or was it 15:14:29 @Bug 727204 15:14:38 There we go 15:14:57 are all the affected packages owned by the same maintainer? 15:15:14 I believe so 15:15:36 sorry if we already discussed, my memory is fuzzy on this ... did we already decide which s-c-* packages needed changes? 15:16:20 * jlaska just making sure that nphilipp knows how to proceed with this bug report 15:16:26 jlaska, j_dulaney: This would all be really easy if using Name and GenericName is supported in Gnome now. Is it? 15:16:37 hey nphilipp! 15:16:43 jlaska: Found you! 15:16:58 jlaska: was on vacation until the WE 15:16:58 nphilipp: I think so, yes 15:17:02 nphilipp: good question, I'm afraid I don't know ... if we don't have an answer in meeting here, perhaps that's worth a note to desktop@lists.fedoraproject.org 15:17:52 #info nphilipp asked whether Name and GenericName is now supported in GNOME. j_dulaney indicated it is now supported. 15:18:17 the reason why these tools have generic names as names is because desktop wanted it this way back in the days. I can easily rename them back if that's what's wanted, and use the GenericName tag for the generic names. 15:18:38 That may be the easiest way to handle this 15:19:01 nphilipp: I'm not closely following this issue, but that seems like a good plan (and perhaps worth a heads up on desktop@ to avoid any surprises) 15:19:20 pong 15:19:54 moving on for now... 15:19:56 #info F15 EC2 images - tflink to confirm with rel-eng to see if 8/1 is a reasonable deadline 15:20:13 tflink and athmane have been most active in this area, anything either of you wanted to highlight? 15:20:14 jlaska, j_dulaney: well, according to https://live.gnome.org/GnomeGoals/CorrectDesktopFiles I should be fine with just doing what we discussed above. 15:20:21 nphilipp: perfect! 15:20:26 the cloud sig decided to move forward with the F15 EC2 test day on 8/4 with the BG created AMIs 15:20:30 #link https://fedoraproject.org/wiki/Test_Day:2011-08-04_Cloud_SIG_Fedora_EC2 15:20:41 #info the cloud sig decided to move forward with the F15 EC2 test day on 8/4 with the BG created AMIs 15:20:46 hopefully, we'll have koji-created AMIs for F16 15:20:57 Sweet 15:21:02 jlaska: just checking, this is meant for F-15 onward? 15:21:11 j_dulaney: ^^ 15:21:20 I'll be sending out announcements for the test day today or tomorrow 15:21:32 nphilipp: certainly F16, I'm not clear on whether this is appropriate for f15 15:21:40 tflink: athmane: excellent, thanks for the updates 15:21:42 j_dulaney: Bug 727204 Make system-config-* progs that have naming conflicts with other packages not show up in Gnome - https://bugzilla.redhat.com/show_bug.cgi?id=727204 15:21:59 #info athmane to continue work on Ovirt Node validation testing and matrix; next meeting review if the spin makes the freeze deadline 15:22:10 I believe this was ACK'd in last weeks meeting? 15:22:19 Ovirt not yet approved by SPIN SIG 15:22:31 #link http://lists.fedoraproject.org/pipermail/fedora-spins/2011-July/002036.html 15:22:43 #link http://lists.fedoraproject.org/pipermail/fedora-spins/2011-July/002037.html 15:22:59 #info athmane informed the group that Ovirt is not yet approved by SPIN SIG 15:23:33 looks like some debate on the extent/scope of spin-kickstart changes allowed 15:23:40 thanks for the links athmane 15:23:53 So, the question now becomes will it be since Freeze has passed? 15:24:14 And, if not, need we support official testing? 15:24:26 no, either way 15:24:33 maybe grant an exception 15:24:36 the SPIN is responsible for ensuring their spins are tested 15:25:00 jlaksa: Indeed 15:25:02 of course, we lend time in helping them structure the testing and doing it in a way consistent with our other plans 15:25:05 (thanks to athmane) 15:25:29 okay, the only other item I had here was for announcing the blocker meeting last week ... thanks to tflink for that 15:25:34 #topic Cloud SIG - Fedora 15 on Amazon EC2 15:25:48 Sounds like we may have updates on this topic already 15:25:56 but let's do a quick re-hash for the logs 15:26:08 #info the cloud sig decided to move forward with the F15 EC2 test day on 8/4 with the BG created AMIs 15:26:12 #link https://fedoraproject.org/wiki/Test_Day:2011-08-04_Cloud_SIG_Fedora_EC2 15:26:33 #action tflink - send Cloud SIG test day announcements 15:26:41 anything else to discuss on this topic? 15:27:02 I don't think so 15:27:10 alrighty ... 15:27:15 nothing I guess, everything was at cloud sig meeting 15:27:21 thanks for the updates gentlemen 15:27:25 #topic F16 Alpha status 15:27:35 #link http://rbergero.fedorapeople.org/schedules/f-16/f-16-quality-tasks.html 15:27:51 There has been no Alpha TC1 compose as of yet 15:28:12 When can one be expected? 15:28:14 if you want to follow the action, you can monitor the rel-eng ticket for TC1 compose progress - https://fedorahosted.org/rel-eng/ticket/4844 15:28:23 j_dulaney: I have no ETA from rel-eng 15:28:46 Based no feedback from the blocker meeting, I suspect once we have resolution on two deps problems ... the compose should move forward 15:29:14 on of the issues is already in MODIFIED (gnome-python2-bonobo) 15:29:18 .bug 726743 15:29:20 jlaska: Bug 726743 gnome-python2-bonobo has missing deps - https://bugzilla.redhat.com/show_bug.cgi?id=726743 15:29:49 #info the other compose blocking bug (726744), with help from halfline, may simply involve unblocking a package to allow the compose to proceed 15:30:20 so I think we're just waiting on feedback from halfline's comment ... as far as I know 15:31:11 #info Since TC1 was expected last Tuesday, and RC1 is expected this Thursday ... if history is any indicator, I expect we'll likely slip the Alpha release due to late discovery of ALpha blockers, or insufficient test feedback in time for the go/no_go 15:31:32 it's entirely possible I'm overly skeptical, and when we do get a compose, things will "just work" 15:31:53 Anything is possible -- it's just software :-p 15:31:56 :) 15:32:07 There are not a lot of changes to the blocker lists today - https://fedoraproject.org/wiki/Current_Release_Blockers 15:32:48 so that's the extent of my knowledge about the Alpha 15:32:53 anyone have other updates to share? 15:32:55 I almost wonder if an extra week for Alpha should be added, since we slip by that much anyway 15:33:01 But that's not for here 15:33:35 j_dulaney: it's a fair question, I've included this challenge in the QA retrospective for 2 releases now 15:34:08 after discussion of RATs and the TC1 milestone, it sounds like adamw has an proposal brewing for adding additional TC milestones earlier in the cycle 15:34:25 but more on that from our favorite Canadian after the break 15:34:30 In this case, the bugs are ones that don't seem to be easily found by just running test composes since they block the compose process 15:34:39 right 15:35:02 #topic Upcoming QA events 15:35:07 Just a quick schedule reminder ... 15:35:22 #info 2011-07-21 - Pre-Alpha Rawhide Acceptance Test Plan #3 - images available, testing in progress by twu 15:35:27 #info 2011-07-26 - Test Alpha 'Test Compose' - DELAYED 15:35:37 #info 2011-08-04 - Test Alpha Candidate Compose 15:35:40 #info 2011-08-05 - Alpha Blocker Meeting (f16alpha) #4 15:36:23 Unless anyone is eager to announce the blocker meeting this week, I'll be glad to do that 15:36:40 #action jlaska - announce blocker review meeting #4 15:36:53 #topic Next meeting 15:37:15 anyone want to volunteer to #chair this meeting next week? 15:37:43 c'mon, not all at once 15:37:46 * tflink can do it 15:37:51 I could do it >if needed< 15:37:55 alright tflink ftw! 15:38:01 * jlaska anxious to spread it around 15:38:08 LOL 15:38:28 I don't mind doing it at all ... I'm interested in some variety when it comes to meeting style etc... 15:38:45 Oy 15:38:47 tflink: thank you ... gimme a holler if you want to punt back to me in case testing takes up too much time 15:38:48 I can do it if it was 18:00 15:39:04 #info 2011-08-08 - 15:00 UTC - tflink volunteered to #chair 15:39:11 thanks tflink! 15:39:12 jlaska: ok, shouldn't be a problem 15:39:17 #topic Open Discussion - 15:39:25 okay, I promised a brief agenda 15:39:31 any #topics folks would like to raise? 15:40:08 #topic Open discussion - AutoQA staging hardware 15:40:22 tflink: you were asking me before the meeting about qa08.qa.fedoraproject.org hardware status 15:40:31 yep 15:40:41 the last update I have was to check back in on Tuesday 15:40:49 iirc, nirik has a support ticket opened up 15:41:05 jlaska: yeah, sorry for delay. will try and find something out. 15:41:14 and smooge may be visiting the colo, or opening up a can of whoop_ss to figure that out, on Tuesday? 15:41:41 nirik: no worries, I'm just hoping it's not a hardware problem ... since we've yet to use that system 15:41:47 boooo! I say to that :) 15:42:11 well, at least we're not depending on that system yet :) 15:42:16 right 15:42:38 so when that system is available ... do we have a plan to proceed yet 15:42:41 yeah, not sure what it's issue is. ;( We will get it fixed up. 15:42:48 Where is it physically located? 15:42:55 phx, I assume 15:42:56 or should I just set it up to run autoqa straight from master? 15:43:04 * nirik nods. phx datacenter 15:43:17 Indeed 15:43:22 I have some ideas but haven't finished writing up a proposal yet 15:43:29 tflink: okay 15:43:41 it would probably be good to just testing 0.6.0 on it for now 15:43:44 #info Support ticket opened, nirik will continue investigating 15:44:08 tflink: testing it manually, or packages I build into the -testing repos? 15:44:28 either way is fine with me 15:44:41 okay, we can figure that out later then 15:44:50 #topic Open Discussion - 15:44:52 We should have the mockup infranstructure ready to go shortly 15:45:04 any other items to cover today? 15:45:18 Magical ponies? 15:45:35 heh, are those back on the agenda? 15:45:42 j_dulaney: I didn't know you did much with Django :) 15:45:42 okay, if nothing, I'll #endmeeting in 2 minutes 15:46:00 Lulz 15:46:37 1 minute until #endmeeting 15:46:56 kparal: nothing from Brno today? you guys must be busy getting this next release out :) 15:47:22 I don't think we have any good update 15:47:28 just finishing tickets 15:47:41 alright folks ... that's it for today 15:47:48 I'll follow-up with minutes to the list 15:47:51 thanks for your time! 15:47:52 #endmeeting