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