16:00:34 #startmeeting Fedora QA meeting 16:00:34 Meeting started Mon Nov 24 16:00:34 2014 UTC. The chair is adamw. Information about MeetBot at http://wiki.debian.org/MeetBot. 16:00:34 Useful Commands: #action #agreed #halp #info #idea #link #topic. 16:00:38 #meetingname fedora-qa 16:00:38 The meeting name has been set to 'fedora-qa' 16:00:45 #topic Roll cal 16:00:47 .hello roshi 16:00:48 roshi: roshi 'Mike Ruckman' 16:00:49 #undo 16:00:49 Removing item from minutes: 16:00:53 #topic Roll call 16:01:05 ahoy mateys, line up on the poop deck 16:01:15 .hello smccann 16:01:17 smccann: smccann 'Shawn McCann' 16:01:18 * pschindl is here 16:01:25 * kparal waves 16:01:26 * pwhalen is here 16:02:30 * jreznik is here 16:03:49 .fire kparal pirates don't wave 16:03:49 adamw fires kparal pirates don't wave 16:04:02 * nirik lurks around back and sneaks a doughnut from the snack table 16:04:09 well, they ride waves 16:04:26 we have doughnuts? 16:04:59 * kparal jumps off the board into the ocean 16:05:11 dognut? 16:05:21 roshi: they're poisoned, it's a trap for releng people who lurk around at the back of meetings. 16:05:40 #topic Fedora 21 Final status 16:05:45 * nirik chokes and falls down on the floor. ;) 16:05:52 * adamw ignores nirik's rattlings 16:05:58 so! how's TC3 looking? 16:06:03 aren't we short supply on releng people? 16:06:09 lol 16:06:11 wow, we're off to a ruthless start this morning 16:07:11 this is QA afterall 16:07:12 :) 16:07:25 icon bugs persist 16:07:28 my install over the weekend of TC3 looks good 16:07:29 THIS IS QAAAAAAAAAAAAAAAAAAAAAAAA 16:07:37 Wasn't TC3 supposed to be cut later today? 16:07:51 * nirik would love to get a RC1 before holidays... but not sure how practical that will be 16:07:52 is the little server logo supposed to be on anaconda somewhere? 16:07:56 There's a bunch of stuff that we approved conditionally at the last Blocker Bugs meeting for landing today in time for a TC3 16:07:58 TC3 is out 16:08:00 * pwhalen just started TC3 testing 16:08:01 sgallagh: nope, saturday. 16:08:08 sgallagh: tc3 already happened. ;) 16:08:30 sgallagh: if interesting stuff lands today we can always do a tc4... 16:08:30 Right, so are we willing to run a TC4 today to catch the pile of stuff that finally landed in stable this morning? 16:08:53 sgallagh: bits that address blocker/FE bugs and that were already available on friday probably are in it. 16:08:58 in tc3* 16:09:04 what were you thinking of specifically?> 16:09:13 Right, but several (like Cockpit and FreeIPA) missed the bus, I think 16:11:35 * adamw looks 16:12:24 * mclasen has another build for bug 1160499 16:13:00 ok, yeah, the latest build of those two are not in tc4 16:13:09 FWIW, I think we should gather what we can today and fire a TC4 tonight... I'm seeing a number of NEW things so probibly no RC1. 16:13:13 we can certainly do a tc4 today (at least from qa end, i assume it's ok with releng?) 16:13:24 absolutely. 16:14:54 #agreed TC4 to go today with cockpit and freeipa fixes (and something from mclasen for #1160499) 16:15:47 so there are still some holes in test coverage for final 16:16:09 on https://www.happyassassin.net/testcase_stats/21/ we need to be looking at the non-optional tests which haven't been run since beta 16:16:46 when's the next blocker review? 16:16:49 * kinokoio pulls in a chair 16:17:11 wednesday, like usual 16:17:30 * roshi is going to send the announcement after this meeting 16:17:53 well, I fear many people will be gone wed and the rest of the week (developer wise) 16:18:06 Need some help? 16:18:16 oh yeah, there's a thing this week isn't there 16:18:31 perhaps we could do something later in this meeting? or today? 16:18:35 we can run one after the meeting 16:18:41 it's really best if we announce it ahead of time though 16:18:46 yeah 16:18:50 nirik: yep, it's a good idea, actually for some reason I expected it today 16:18:50 last cycle we got into a swing of announcing a blocker after the monday meeting 16:19:01 blocker review meeting* 16:19:05 I guess I shoulda thought about that and sent an announcement htis weekend 16:19:17 yeah, if we could get approvals today we can try and get developers to work on stuff today/tomorrow... 16:19:46 and possibly get a rc1 wed... which would be nice because people could hammer on it as they like over the holiday 16:20:09 sgtm 16:20:09 i'm up for doing blocker review after the meeting if enough other folks are 16:20:13 sure 16:20:15 we can postpone anything contentious to wed 16:20:20 europe will be working this, so it depends on what's going to be accepted/who's maintainer 16:20:23 just get the obvious ones agreed at least 16:20:27 * nirik can help 16:20:37 jreznik_2nd: true. 16:20:46 so we can nag some people here to help 16:21:31 #agreed we'll run a blocker review meeting after this meeting (yay meetings) 16:22:28 whee! 16:23:26 * kparal celebrates with a bottle of beer 16:23:43 or maybe something stronger 16:23:44 we have one accepted blocker that's waiting for verification of fix - https://bugzilla.redhat.com/show_bug.cgi?id=1165261 . it's freeipa, but doesn't really need a TC4 to test. sgallagh, did your testing of the update include verifying that bug? 16:24:01 .fire kparal no drinks weaker than cask-strength whisk(e)y acceptable on this ship 16:24:01 adamw fires kparal no drinks weaker than cask-strength whisk(e)y acceptable on this ship 16:24:27 fivebeers are honorably excepted 16:24:35 /me reviews that BZ 16:24:42 * kparal changes to slivovice 16:24:45 I did not experience the issue. 16:25:08 sgallagh: did you do an ipa-server-install ? 16:25:23 adamw: Yes, that's done under the hood with rolekit, which I tested 16:25:59 I'm comfortable saying that this is fixed until proven otherwise. 16:26:04 then I believe we can mark it VERIFIED 16:26:20 done 16:27:14 so with that we're doing well on blocker fix validation i think. 16:28:19 on the release criteria + test case subtopic...I'm still in the process of writing test cases for all sgallagh's new server criteria, but i think we have the full set of criteria that are wanted for Final 16:28:51 do we have any criteria work outstanding for cloud, roshi? mclasen, anything for workstation? I think we decided the criteria for workstation are OK now too 16:28:53 I had a question about criteria, but for cloud 16:29:06 I mailed the list 16:29:08 https://lists.fedoraproject.org/pipermail/test/2014-November/123936.html 16:29:40 got no feedback 16:29:45 seems fine by me 16:29:48 * adamw will +1 the ticket 16:30:08 adamw: don't know about criteria, but I just attached icons to https://bugzilla.redhat.com/show_bug.cgi?id=1130794 - may want to do a setroubleshoot build with those included 16:30:10 sorry i didn't see it earlier 16:30:26 mclasen: thanks, let's try and find someone to do the setroubleshoot build... 16:30:45 I'll go ahead and add it to the final criteria then 16:30:57 I just wanted some QA eyes on it before i went changing things 16:31:09 adamw: for workstation, are high contrast really that important to be in criteria? but it's really up to workstation guys and mclasen 16:31:33 I don't think it justifies blocking the release, tbh 16:31:46 jreznik_2nd: it's an a11y thing I believe. I think all of us who were around the last time we had these sorts of criteria were a bit worried based on past experience 16:32:22 but it is nice to have some pressure for getting those gaps closed 16:32:23 mclasen: thanks for setroubleshoot icon, I'll make sure mgrepl builds it asap 16:32:31 mclasen: so the requirement comes in via https://fedoraproject.org/wiki/Workstation/Guidelines/Applications_and_Launchers 16:32:48 mclasen: which is under control of the ws WG, so if we don't really want to block release on it, it could be changed into a SHOULD 16:33:08 mclasen: I understand it's nice to have pressure and seems it helps but we can do it more in step by step way 16:33:37 i'm not a fan of using the blocker process as a way to get 'some pressure' on things, it doesn't work out well in the end (you end up with the RHEL situation where you can't tell the blockers from the not-really-blocking-the-release-but-someone-wanted-it-on-a-priority-list bugs) 16:34:54 we can discuss it on desktop@ i guess 16:35:20 I know and yes, we can discuss it on the list 16:36:26 okey dokey 16:36:31 anything else for f21? 16:36:42 #action adamw to mail desktop@ about release blocking status of high-contrast icons 16:36:50 adamw: thanks 16:37:15 * jreznik_2nd thinks it's all for F21, it's shaping out well 16:40:35 OK, moving on 16:40:39 oh, oops 16:40:44 #chair jreznik_2nd mclasen roshi 16:40:45 Current chairs: adamw jreznik_2nd mclasen roshi 16:40:58 #topic Test Days 16:41:09 I just wanted to check in on test day status since I haven't been following it super closely 16:41:17 for those who have, has it been going OK? do we have any more coming? 16:41:22 last testday I was tracking was Atomic 16:41:24 which we just had 16:41:32 went off without a hitch I think 16:41:42 jzb: do you concur? 16:42:40 * roshi double checks, but doesn't think there are any more coming 16:43:31 #info last test day, Atomic, went off OK, that should be the end of the F21 Test Days - thanks all who helped out 16:45:24 i like simple topics! 16:45:45 proposals for more test days can always be filed in trac, of course 16:45:52 alrighty, on to... 16:45:54 #topic Open floor 16:46:07 anyone have anything we should discuss that hasn't come up yet? 16:46:57 not I 16:47:14 we have 8 proposed blockers and 7 proposed FEs though 16:47:16 * jreznik_2nd neither, blocker, blockers! 16:47:31 boy howdy, I love blocker review. 16:47:39 me too 16:47:43 best part of the week 16:47:44 * adamw grabs the meths 16:47:57 blocker review at the top of the hour? 16:48:03 sgtm 16:48:10 BYOB 16:48:55 sigh, ok 16:49:07 I can't make the blocker review today, though I did vote in one ticket. 16:49:28 thanks sgallagh 16:49:36 ack, time to grab at least some apple in the office as emergency solution 16:49:58 * adamw ties sgallagh to the mast 16:50:13 /me can see his house from here! 16:52:57 okey dokey, thanks for coming, folks 16:53:02 nice to be on time for a change :) 16:53:05 #endmeeting