16:02:15 #startmeeting F22-blocker-review 16:02:15 Meeting started Wed Jan 7 16:02:15 2015 UTC. The chair is roshi. Information about MeetBot at http://wiki.debian.org/MeetBot. 16:02:15 Useful Commands: #action #agreed #halp #info #idea #link #topic. 16:02:15 #meetingname F22-blocker-review 16:02:15 The meeting name has been set to 'f22-blocker-review' 16:02:16 #topic Roll Call 16:02:26 * pschindl is here 16:02:29 who's around for some blockery fun? 16:02:38 here 16:02:44 * kparal is here for a short time (30 minutes) 16:03:02 Sure, why not? 16:03:52 we'll try to get the most out of you in 30 minutes that we can, kparal :p 16:04:07 welcome apatel, sgallagh :) 16:04:15 * nirik is lurking in the back near the coffee machine. 16:04:17 adamw: danofsatx|w ? 16:04:18 roshi: The floggings will continue until morale improves? 16:04:30 something like that 16:04:44 I was thinking about discussing the possibility of moving these meetings to monday as the first item on the today's list 16:04:55 haven't reinstalled the flogging module since unplugging it before leaving for the holidays 16:05:10 sounds good to me 16:05:41 #topic Change blocker review time discussion 16:05:54 I'm not at all against the idea 16:05:58 so, the proposal is to move this meeting to monday 17:00 utc 16:06:05 that's one hour later than now 16:06:06 +1 for Mondays. 16:06:17 it would follow after the regular qa meeting 16:06:25 I don't mind to spend whole evening on meeting :) 16:06:44 so those coming to the qa meeting and blocker review would have a meeting block of 1600-2000 16:06:48 That would be easier on me, actually 16:06:56 then we can't do it 16:06:57 great. what about others? 16:07:03 I will not be able to make it until the next semester starts (I'm in high school) 16:07:04 :p 16:07:14 * satellit_e listening 16:07:16 After though, I will be able to make it 16:07:26 no worries apatel :) 16:07:56 once F22 is Branched, we can again shift the time if needed. or anytime sooner, if required 16:08:07 but for the short future, monday would work better for me 16:08:14 adamw said on list he didn't have an issue with it 16:08:18 * satellit_e I will be unable to make Mondays 1 hr later have Dr appointment mon wed fri at 9:30AM 16:08:31 (although, I can't attend on Wednesdays, which might be *better for me* :P ) 16:08:42 #proposed Hold next blocker review on Monday 2014-01-12 16:09:27 satellit_e: every single week? 16:09:57 afraid so have to do rehab on treadmill 30X 16:10:07 that's less than fun 16:10:14 but I can read scroolback 16:10:30 you could also vote in the bugs, then we can take it into account here in the meeting 16:10:41 k 16:10:47 provided you do it before the meeting, I guess 16:11:06 apart from satellit_e, I think everyone is pretty much for the idea 16:11:10 so let's shift it 16:11:21 sorry satellit_e 16:11:25 Related: should we treat things like in FESCo, where we don't attempt to vote on bugs that come in with less than 24 hours before the meeting (at least outside of Freeze?) 16:11:53 sgallagh: let's close this topic first 16:12:05 roshi: put #accepted? 16:12:07 /me nods 16:12:15 sure 16:12:16 or #agreed or whatever it is 16:12:36 #agreed Hold next blocker review on Monday 2014-01-12 16:12:38 yep 16:12:49 thanks. I'll adjust fedocal 16:13:07 sgallagh: probably best to discuss that in the QA meeting? 16:13:21 ok 16:13:35 * kparal doesn't mind either way 16:13:35 in this meeting, we just execute the law without worrying about the process :p 16:14:05 onto the blockers? 16:14:09 yes 16:14:24 #chair kparal sgallagh adamw 16:14:24 Current chairs: adamw kparal roshi sgallagh 16:14:27 #topic Introduction 16:14:27 Why are we here? 16:14:28 #info Our purpose in this meeting is to review proposed blocker and nice-to-have bugs and decide whether to accept them, and to monitor the progress of fixing existing accepted blocker and nice-to-have bugs. 16:14:31 #info We'll be following the process outlined at: 16:14:34 #link https://fedoraproject.org/wiki/QA:SOP_Blocker_Bug_Meeting 16:14:36 #info The bugs up for review today are available at: 16:14:39 #link http://qa.fedoraproject.org/blockerbugs/current 16:14:41 #info The criteria for release blocking bugs can be found at: 16:14:44 #link https://fedoraproject.org/wiki/Fedora_22_Alpha_Release_Criteria 16:14:47 #link https://fedoraproject.org/wiki/Fedora_22_Beta_Release_Criteria 16:14:50 #link https://fedoraproject.org/wiki/Fedora_22_Final_Release_Criteria 16:14:53 also remember, for this meeting, we're going over all the milestones 16:15:07 Alpha has 3 proposed 16:15:07 #topic (1169019) UnicodeDecodeError: 'ascii' codec can't decode byte 0xe4 in position 11: ordinal not in range(128) 16:15:10 #link https://bugzilla.redhat.com/show_bug.cgi?id=1169019 16:15:13 #info Proposed Blocker, anaconda, ASSIGNED 16:16:03 This one was caused by accidentally pulling in a development version of blivet into the F21 stream. It was reverted. 16:16:24 We *do* want to see it fixed for F22, since they'll be rebasing blivet 16:18:02 It's ambiguous in the guidelines whether all languages must work in Alpha 16:19:20 this seems to be a pretty widespread problem, many languages affected, IIRC 16:19:24 yeah 16:19:31 it affects multiple langs 16:19:35 Yeah, but not *mine* ;-) 16:19:44 fixed in F21, but we want it fixed for F22 16:19:47 because of that, I think it's reasonable to make it block Alpha 16:20:00 I'm +1 - I could see arguing to make it later (beta or something) 16:20:06 but we haven't branched yet 16:20:22 I think there's time and it'd be good to get fixed 16:21:12 True enough. I guess it would be pretty terrible to ship the Alpha like that. 16:22:17 everyone +1? 16:22:22 +1 16:22:25 +1 16:22:28 +1 16:22:31 yep 16:22:41 +1 16:23:02 +1 16:23:28 Even though it would be nice to have it done by alpha, it seems wrong to make it a blocker without matching any criterion for alpha. 16:24:01 proposed #agreed - 1169019 - AcceptedBlocker - This bug is a clear violation of the Alpha criterion: The installer must be able to complete an installation to a single disk using automatic partitioning. 16:24:20 Maybe the criterion for alpha needs to be modified? 16:24:21 brunowolff: the quoted criterion was Alpha, "Disk layouts" 16:24:24 it's conditional 16:24:39 so let me reword that 16:24:50 proposed #agreed - 1169019 - AcceptedBlocker - This bug is a conditional violation of the Alpha criterion: The installer must be able to complete an installation to a single disk using automatic partitioning. 16:25:29 I agree with adamws explanation: the condition being that you're using an affected translation (at least Russian, I haven't checked exactly which languages have non-ASCII characters in translations of text that appears in pyparted unicode objects, which I think is the problem here). 16:25:38 from comment 41 16:25:48 ack/nack/patch? 16:25:59 acl 16:26:01 *ack 16:26:32 ack 16:26:35 ack 16:27:01 #agreed - 1169019 - AcceptedBlocker - This bug is a conditional violation of the Alpha criterion: The installer must be able to complete an installation to a single disk using automatic partitioning. 16:27:25 since kparal has to leave soonish, any volunteers to secretarialize? 16:28:21 ack, but I think that people feel that major translation breakage should be an alpha blocker and it may be a good idea to add an explicit criterion and note that working just in English isn't good enough. 16:28:24 leave how soon? 16:28:36 I can try it. Not sure how it will end :) 16:28:37 in a few minutes 16:29:13 same kparal, my lunch period is almost over 16:29:36 not a bad idea brunowolff 16:29:51 tbh, I thought that was a criteria :) though maybe not for alpha 16:30:01 thanks pschindl 16:30:15 I can help out if you have any questions 16:30:54 next bug! 16:30:55 #topic (1179362) boot.iso installs result in console login 16:30:55 #link https://bugzilla.redhat.com/show_bug.cgi?id=1179362 16:30:56 #info Proposed Blocker, anaconda, ASSIGNED 16:31:10 thanks everyone, need to go 16:32:30 how in the hail did I miss this? last I saw in channel was that there was no meeting today 16:32:58 * danofsatx|w needs remedial reading, apparently 16:33:11 This sounds like a pretty obvious blocker 16:33:11 lol 16:33:16 welcome danofsatx|w 16:33:18 yeah 16:33:33 I suspect that adamw is right about the cause: the sssd-common breakage likely has a lot of fallout. 16:33:42 That should be fixed by tomorrow 16:33:49 +1 16:33:55 +1 16:34:27 or rather, the catalyst; not the cause 16:34:27 +1 16:34:27 +1 16:34:38 +1 16:34:45 proposed #agreed - 1179362 - AcceptedBlocker - This bug is a clear violation of the Alpha Package Sets criterion: When doing a graphical install using the dedicated installer images, the installer must be able to install each of the release blocking desktops, as well as the minimal package set. 16:34:46 Probably DNF is quietly ignoring the chain of failures, which is... bad 16:34:56 yeah, it is :) 16:35:05 ack 16:35:13 ack 16:35:14 If we fix the SSSD tonight, we can see if that makes this go away. 16:35:18 If so, we have more information to work with 16:35:38 yup 16:35:49 #agreed - 1179362 - AcceptedBlocker - This bug is a clear violation of the Alpha Package Sets criterion: When doing a graphical install using the dedicated installer images, the installer must be able to install each of the release blocking desktops, as well as the minimal package set. 16:35:55 next blocker! 16:35:59 last one for alpha 16:36:05 #topic (1170803) calls e2fsck on all ext volumes, provides no status indicator, and hangs indefinitely if e2fsck doesn't exit 16:36:08 #link https://bugzilla.redhat.com/show_bug.cgi?id=1170803 16:36:11 #info Proposed Blocker, e2fsprogs, NEW 16:38:41 What criteria covers "annoyances"? 16:39:43 Yeah, this seems like something we wouldn't want to block alpha or beta over. 16:39:59 I'm not sure this is strictly an annoyance 16:40:27 In the originally-reported case, they had a USB drive attached that hung on e2fsck 16:40:32 at which milestone would this behaviour be acceptable? 16:40:39 It should not have ever *run* on that drive 16:40:54 I would say none 16:41:06 even though I don't have machines that are affected 16:43:30 I'd probably call this an Alpha FE and a Beta Blocker, personally 16:44:23 you don't think this falls under the showstopper criterion cited? 16:44:24 Even looking through the final criteria for resizing, I don't get the impression that overly long resize processes should be a blocker. 16:44:55 roshi: I missed that criteria. What was it? 16:45:03 Installation Interfaces on alpha 16:45:09 brunowolff: overly long, no. Hung, yes. 16:45:11 under showstoppers 16:45:23 I got the impression that the original report was actually hung, not just taking forever. 16:45:26 Or did I misread? 16:45:30 and I would argue, if the user isn't given any feedback and can *think* it's hung 16:45:37 Is it really hanging or just taking very long? 16:45:54 taking forever, and now giving any feedback - aiui 16:46:06 which to a user who can't know what's happening, that might as well be the same thing 16:46:10 now or not? 16:46:31 to a user there's no difference between dead, and mostly dead 16:47:12 troy blave... 16:47:17 :) 16:47:26 which means to bluff! 16:48:07 I'd say +1 blocker on this one - since a user has no way to know things haven't hung 16:48:10 But if the person did want to use that filesystem and it needed a long time to do this, then things may be working correctly, making the lack of feedback a problem. 16:48:27 I'd be fine with it being beta, but I think it can fit here just as well 16:48:46 imo, the lack of feedback is the real issue 16:48:54 either don't do a long process or provide feedback 16:48:56 I'm fine with granting it blocker status, given that the person who's going to fix it made that request 16:49:09 So we know it's likely to happen 16:49:12 votes? 16:49:13 true 16:49:15 +1 16:49:17 +1 16:49:24 Just because it is bad behavior (which I think we all agree on), doesn't make it a blocker. 16:49:34 -1 16:49:44 What exactly are we voting on? 16:50:11 if this is a blocker or not 16:50:16 I'm -1 alpha blocker, -1 beta blocker, 0 final blocker 16:50:44 proposed #agreed - 1170803 - AcceptedBlocker - This bug conditionally violates the Installation Interfaces criterion: When using a dedicated installer image, the installer must be able to complete an installation using the text, graphical and VNC installation interfaces. (under the showstoppers clause) 16:50:47 it's more of a feature request IMHO 16:50:54 any other no votes? 16:51:06 right now we have 2/2 16:51:21 I just wanted to finish writing that :p 16:52:00 2/2/0 sounds like a punt. 16:52:01 I'm going to switch to 0 16:52:13 The maintainer sounds like he'll fix it either way 16:52:17 And there's plenty of time 16:52:34 I can't find a criteria here that I want 16:53:00 I feel like it should block *at some point* because it doesn't let the user know what it's doing - which can make it appear broke 16:53:04 works for me 16:53:26 appearances are deceiving. ;) 16:53:48 I'm assuming that the process is just taking a long time and eventually would finish, if it is established that it really hangs, then I'd modify my vote. 16:54:07 proposed #agreed - 1170803 - RejectedBlocker - This bug doesn't clearly violate any criteria and looks to be getting worked on either way. Please repropose if it's found to violate another criterion. 16:54:09 proposed #agreed - 1170803 - RejectedBlocker - This bug is an annoyance, but not sufficiently problematic that it would be worth blocking a release over. 16:54:24 good timing sgallagh :) 16:54:31 I withdraw mine. Your phrasing is better 16:54:34 +1 roshi 16:54:35 ack to either 16:54:39 ack roshi 16:54:42 or that :) 16:54:42 ack roshi 16:54:50 #agreed - 1170803 - RejectedBlocker - This bug doesn't clearly violate any criteria and looks to be getting worked on either way. Please repropose if it's found to violate another criterion. 16:55:12 alright, onto the proposed beta bugs 16:55:24 #link http://fedoraproject.org/wiki/Fedora_22_Beta_Release_Criteria#Initialization_requirements 16:55:30 /me disappears for five minutes to microwave his lunch 16:55:37 #topic (1166598) going back to installation destination picker swaps partitions on disks 16:55:40 #link https://bugzilla.redhat.com/show_bug.cgi?id=1166598 16:55:42 #info Proposed Blocker, anaconda, ASSIGNED 16:55:43 what are we having sgallagh ? 16:59:41 I'm having mac-o-jeez in a bit. I'm not enthused. 17:00:38 lol 17:00:45 this looks like it's fixed? 17:00:49 roshi: If you were nearby, I'd share my homemade turkey soup. 17:00:58 I have over six gallons of it left from the holidays -_- 17:01:00 tasty 17:01:10 where would nearby be? 17:01:11 http://plantpoweredkitchen.com/recipes/recipe-mac-oh-geez/ 17:02:21 roshi: Westford 17:02:26 ah, yeah 17:02:28 not near there 17:02:47 I think the bug has morphed. The original problem seemed pretty serios, but the remaining issue seems more in the can be confusing category. 17:03:03 yeah 17:03:10 I remember reproducing this bug :) 17:04:56 C#22 seems to show that it is annoying and misleading, but not broken 17:05:00 (any longer) 17:05:11 I'd say -1, +1 FE 17:05:27 +1 FE 17:05:31 I think there should really be a separate bug for the remaining issue and the original closed. 17:06:02 we can do that too 17:06:24 I'm not sure if that fix made it to anaconda (I'm talking about c#22) 17:06:35 I'm 0 on the FE. 17:06:55 Without this fix it should be still happening. 17:07:56 I view this bug as not getting totally fixed, so not sure it needs a new bug 17:08:02 Until we confirm that the fix from c#21 is in anaconda I'm +1 for beta blocker. 17:08:05 but it could use a renaming and an FE, I would say 17:08:25 renaming, yes. 17:08:32 We do need to confirm the fix was applied, and that part is a blocker. 17:08:59 I'm +0 on this one...not convinced there is a problem, and not convinced it has been fix (if there is a problem) 17:09:01 punt until we know if it made it into anaconda? 17:09:36 +1 punt 17:09:49 punt it. If it haven't made it to anaconda yet I'm strongly +1 as it can possibly destroy user data. 17:10:32 proposed #agreed - 1166598 - Punt - It's not clear where this bug or the fix currently stands. Punting until we have more information. 17:11:08 ack 17:11:52 ack 17:12:00 #agreed - 1166598 - Punt - It's not clear where this bug or the fix currently stands. Punting until we have more information. 17:12:08 #topic (1177988) ConfigError: Repository updates has no mirror or baseurl set. 17:12:11 #link https://bugzilla.redhat.com/show_bug.cgi?id=1177988 17:12:14 #info Proposed Blocker, anaconda, ASSIGNED 17:14:13 ack 17:14:38 I don't have a strong opinion on this one either way. I need to get going for today. 17:14:54 have a good day brunowolff - thanks for coming! 17:14:59 +1 for me 17:17:29 +1 17:18:45 stand by, reading 17:18:59 kk 17:20:00 +1 17:20:40 proposed #agreed - 1177988 - AcceptedBlocker - This bug violates the Beta criterion: The installer must be able to complete a scripted installation which duplicates the default interactive installation as closely as possible. 17:20:46 ack 17:20:50 ack 17:20:55 #agreed - 1177988 - AcceptedBlocker - This bug violates the Beta criterion: The installer must be able to complete a scripted installation which duplicates the default interactive installation as closely as possible. 17:20:59 #topic (1170800) Please stop overwriting anaconda's stylesheet 17:21:00 #info Proposed Blocker, fedora-productimg-server, NEW 17:21:02 #link https://bugzilla.redhat.com/show_bug.cgi?id=1170800 17:21:23 sounds like an adamw bug from the name.... 17:21:33 but its not.... 17:22:47 lol 17:22:47 oh, morning. 17:22:58 +1 FE, not sure how this became a blocker 17:23:04 i thought we were changing this to mondays? 17:23:10 roshi: via my dupe 17:23:25 +1 FE. 17:23:33 https://bugzilla.redhat.com/show_bug.cgi?id=1176411 17:23:44 the bug that SUSE guy reported 17:23:49 adamw: we did change it, but from next week :) 17:24:04 adamw: Good morning. 17:25:06 we are, next time adamw 17:25:29 couldn't have my announcement be totally wrong and useless :p it had good info in it 17:26:12 so is this supposed to be a blocker proposal or FE? 17:26:40 well, it blocks keyboard navigation of anaconda's gui, so it's a blocker. 17:26:52 revote: +0FE, +1 block. 17:26:54 for 1170800? 17:27:12 it's the same underlying issue, according to 1176411 17:27:27 anaconda's style sheet is being overwritten. 17:27:29 ah 17:27:30 got it now 17:27:36 +1 blocker 17:27:42 thanks for the context adamw 17:27:43 right, CSS bug is nominated as a blocker due to impact on keyboard navigation. 17:27:59 I wouldn't have thought the CSS would be the culprit for this 17:28:20 me either, but that's what they say 17:29:12 proposed #agreed - 1170800 - AcceptedBlocker - This bug breaks keyboard usage for installation, and thus is a conditional violation of the following Final criterion: Installer must be able to complete an installation. 17:29:26 ack 17:29:35 works for me, as I almost always use the keyboard only for installs 17:29:41 ack 17:29:56 #agreed - 1170800 - AcceptedBlocker - This bug breaks keyboard usage for installation, and thus is a conditional violation of the following Final criterion: Installer must be able to complete an installation. 17:29:58 oh really? /me has all the mouse movements in muscle memory (ooh, say that five times fast) 17:30:01 #topic (1170788) [abrt] gnome-shell: check_fontmap_changed(): gnome-shell killed by SIGSEGV 17:30:04 #link https://bugzilla.redhat.com/show_bug.cgi?id=1170788 17:30:06 #info Proposed Blocker, gnome-shell, NEW 17:30:53 +1, pretty clear violation 17:32:05 +0, need reproducers 17:33:19 true 17:33:34 someone have a recent rawhide there to test? 17:33:34 yeah, and current ones, it's been a month 17:33:42 i don't have a live atm 17:33:46 psh, timestamps 17:33:47 i can try it again later 17:33:54 punt for now then 17:34:34 proposed #agreed - 1170788 - Punt - This bug might have gone stale in the past month. Will revisit next week after we've attempted to reproduce with more recent media. 17:34:43 ackityack 17:35:29 ack 17:35:53 #agreed - 1170788 - Punt - This bug might have gone stale in the past month. Will revisit next week after we've attempted to reproduce with more recent media. 17:36:02 last one 17:36:03 #topic (1175847) Missing high contrast icon for Documents 17:36:03 #link https://bugzilla.redhat.com/show_bug.cgi?id=1175847 17:36:03 #info Proposed Blocker, gnome-themes-standard, NEW 17:37:26 +1, though it might be fixed already 17:37:27 +1 17:37:37 +1 17:37:49 +1 (pace the discussion on whether we should do stuff with these polish criteria0 17:38:43 I'm fine with polish criteria like this one because it's pretty specific 17:40:42 where is this criteria? 17:41:02 it's part of the 'must meet the Workstation guidelines' thing isn't it? 17:41:22 I think so, trying to find that 17:41:35 "All applications installed by default in Fedora Workstation must comply with each MUST and MUST NOT guideline in the Applications and Launchers policy. " 17:41:44 https://fedoraproject.org/wiki/Fedora_22_Final_Release_Criteria#Default_application_functionality 17:42:15 yeah, that one 17:42:50 proposed #agreed - 1175847 -AcceptedBlocker - This bug is a clear violation of the Default application functionality criterion: All applications installed by default in Fedora Workstation must comply with each MUST and MUST NOT guideline in the Applications and Launchers policy. 17:43:58 ack 17:44:07 ack 17:44:24 ack 17:44:28 #agreed - 1175847 -AcceptedBlocker - This bug is a clear violation of the Default application functionality criterion: All applications installed by default in Fedora Workstation must comply with each MUST and MUST NOT guideline in the Applications and Launchers policy. 17:44:33 well, that's it 17:44:37 no need to go through FE's at this point 17:44:43 #topic Open Floor 17:44:50 anyone have anything for open floor? 17:45:00 thanks for secretarializing pschindl :) 17:46:07 don't think so 17:46:20 expect 2015-01-07 to be 'nominated for testing' just as soon as i get a fixed build of wikitcms 17:46:50 sweet 17:46:57 * roshi sets the fuse... 17:46:59 3... 17:47:01 roshi: Thanks for leading this 17:47:14 np :) 17:47:16 2.87345... 17:47:23 2... 17:47:28 lol 17:47:28 thanks roshi and pschindl! 17:47:56 1... 17:48:02 thanks everyone for showing up! 17:48:26 Showing up must go on :) 17:48:29 #endmeeting