15:58:52 #startmeeting F21-blocker-review 15:58:52 Meeting started Wed Oct 1 15:58:52 2014 UTC. The chair is roshi. Information about MeetBot at http://wiki.debian.org/MeetBot. 15:58:52 Useful Commands: #action #agreed #halp #info #idea #link #topic. 15:58:52 #meetingname F21-blocker-review 15:58:52 The meeting name has been set to 'f21-blocker-review' 15:58:53 #topic Roll Call 15:59:11 who's around for some review funtimes? 16:01:45 adamw: tflink danofsatx-work satellit_e pwhalen ? 16:01:50 anybody? 16:01:53 ahoyhoy 16:02:05 * adamw dons waders, prepares for 'fun' 16:02:06 * nirik is lurking, ping if I am needed. 16:02:16 * pwhalen is here 16:02:31 * tflink can be here but is trying to fix some stuff ATM 16:03:22 well, that's enough to go forward - hopefully more show up though :) 16:03:43 .moar boilerplate 16:03:43 roshi: (moar ) -- Alias for "echo here $2, have some more $1". 16:03:49 .moar boilerplate meeting 16:03:49 here meeting, have some more boilerplate 16:03:54 #topic Introduction 16:03:54 Why are we here? 16:03:54 #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:03:58 #info We'll be following the process outlined at: 16:04:01 #link https://fedoraproject.org/wiki/QA:SOP_Blocker_Bug_Meeting 16:04:03 #info The bugs up for review today are available at: 16:04:06 #link http://qa.fedoraproject.org/blockerbugs/current 16:04:08 #info The criteria for release blocking bugs can be found at: 16:04:11 #link https://fedoraproject.org/wiki/Fedora_21_Alpha_Release_Criteria 16:04:14 #link https://fedoraproject.org/wiki/Fedora_21_Beta_Release_Criteria 16:04:17 #link https://fedoraproject.org/wiki/Fedora_21_Final_Release_Criteria 16:04:20 alright, we've got 19 blockers for today 16:04:26 #chair adamw pwhalen tflink 16:04:26 Current chairs: adamw pwhalen roshi tflink 16:04:45 volunteer to secretialize? 16:05:03 sure 16:05:11 and someone to take over the meeting in 2.5 hours - I have an appt I'll have to leave for 16:05:25 i guess we could just wind up at that point? 16:05:29 well, let's see where we are 16:05:38 works for me 16:05:45 alright, first blocker 16:05:45 #topic (1074358) all initramfs in existing /boot are updated and broken on install 16:05:49 #link https://bugzilla.redhat.com/show_bug.cgi?id=1074358 16:05:51 #info Proposed Blocker, anaconda, NEW 16:06:41 +1 blocker in theory, knowing there's no criteria *yet* 16:07:35 so reading through this again, i'm curious whether the old kernels boot with the new distribution 16:07:47 i'm not sure if we really support sharing /boot with another release of fedora in this way 16:08:03 i think i'd like to get an anaconda dev's opinion before +1ing this 16:08:34 should there be a warning or something before it breaks existing installs though? 16:09:28 * danofsatx-work is here, but konversation is borked 16:09:41 .moar irssi danofsatx-work 16:09:41 here danofsatx-work, have some more irssi 16:10:16 can we get an anaconda dev in here to pontificate on it? 16:10:46 lets try kvirc 16:11:28 danofsatx: we're looking at .bug 1074358 16:13:11 roshi: well, it only breaks existing install if you share /boot with one 16:13:16 and i'm not really sure we intend to allow that 16:13:23 my opinion? we shouldn't allow use of preexisting /boot filesystem 16:13:30 (though i suspect that might make people kick) 16:13:59 I can see arguments either way 16:14:10 I'm curious why it's worked in the past 16:14:32 but that's more academic and less important 16:14:36 well, i think it's to do with whether we change things in grub or not 16:14:50 there's some kind of change with the s/linux/linux16/ stuff going on there, i don't understand what that is exactly 16:15:10 I guess I'm more +/- 1 at this point 16:15:15 feels like an edge case 16:15:41 * roshi only ever reuses /home 16:16:38 adamw: https://git.fedorahosted.org/cgit/anaconda.git/tree/pyanaconda/packaging/__init__.py?h=f21-branch#n345 16:16:38 dlehman: so, it's going to Do Stuff for all kernels it finds in /boot, basically? 16:16:38 yes 16:16:38 * dlehman originally tried to write it to use the contents of rpms we installed, but live 16:18:20 so i'm gonna say a weak -1 to this based on my understanding of the criteria we're currently reviewing 16:18:36 with the new info, I agree with the weak -1 16:18:40 under current criteria, -1. 16:18:47 * danofsatx reviews test@ 16:18:50 "The installer must be able to install into free space alongside an 16:18:50 > existing GNU/Linux installation, install and configure a bootloader that 16:18:50 > will boot both systems, within the limitations of the upstream 16:18:50 > bootloader." i don't think this would violate that 16:19:06 as this isn't the 'typical' dual boot scenario 16:19:21 yeah, because this borks other things 16:19:22 when we say 'install into free space', it sort of implies no shared /boot 16:19:27 yeah 16:19:29 right, close.. -1 based on that 16:21:15 proposed #agreed - RejectedBlocker - 1074358 - This bug doesn't directly violate any criteria and nothing indicates having a shared /boot is desired functionality. 16:21:36 ack 16:21:52 ack 16:22:01 ack 16:22:03 #agreed - RejectedBlocker - 1074358 - This bug doesn't directly violate any criteria and nothing indicates having a shared /boot is desired functionality. 16:22:20 * roshi writing it counts as an implied 'ack,' IMO 16:22:32 #topic (1114786) DeviceError: ('cannot replace active format', 'sda6') 16:22:35 #link https://bugzilla.redhat.com/show_bug.cgi?id=1114786 16:22:38 #info Proposed Blocker, anaconda, NEW 16:25:00 * roshi is reading 16:26:51 it's a bit of a mess between livesys, systemd and anaconda in swap partition handling 16:27:05 so it seems 16:27:54 it's live-specific 16:28:22 * adamw checks he can reproduce 16:28:24 I think chris is right though, it shouldn't result in a crash 16:30:48 yeah, i i think we can reasonably read c#12 criterion as covering this 16:30:51 just want to be sure it's reproducible 16:31:28 I can remove all partitions and go forward with no issues 16:31:38 * jreznik is here, mtg conflict again 16:32:13 yeah, me too 16:32:18 +1 blocker if reproducible; ack 16:32:26 theory: only happens if the swap is a 'simple' partition 16:32:29 doesn't happen if it's part of an lv 16:32:33 * pwhalen quickly grabs lunch 16:33:21 ah, yeah 16:33:35 `blkid -t TYPE=swap -o device` - the command livesys runs - returns nothing on my test system 16:33:36 * roshi runs a quick install not using lvm 16:34:18 my test system returns /dev/vda2 16:35:52 roshi: the one you had a successful run on? 16:36:32 successful in the sense that anaconda didn't crash when I reused swap and began the installation 16:36:50 * roshi thought the crash presented inside the storage spoke 16:37:21 oh, and cmurf was testing on GPT too 16:37:23 that's the way I read it, too 16:37:41 if you need both GPT and a non-LV swap partition to hit this, i'm not sure it's quite worth a blocker 16:37:50 * adamw runs some more tests 16:38:12 yeah, if that's the case, I think -1 16:38:52 why? one of the benfits of GPT was more than 4 partitions, which a lot of users used LVM to get around in the first place on MBR drives. 16:38:56 * roshi installs with simple partitions 16:40:07 danofsatx: we're not deciding whether it's a bug, remember. but whether it'sa blocker. 16:40:14 the default layout for UEFI installs is still LVM. 16:40:35 understood, I'm simply pointing out that it may be more common than you think 16:40:38 so you'd have to both do a UEFI/GPT install and explicitly pick a layout with a 'normal' swap device, then be trying to do this in custom part on a second install, to hit the bug. 16:41:05 and, er, you don't need LVM to avoid the partition limit. 16:41:14 you just need extended partitions, which have been a thing since, like, 1990 somehing? 16:42:17 anyhow, sidebar 16:42:37 * adamw has an MBR install with a 'regular' swap partition running 16:42:44 we do have a simple workaround for the bug, too: boot with noswap 16:43:21 which someone susceptible to this bug would know how to do. file it as a common bug with workaround, and move on. 16:43:53 just want to check if i can hit it with a non-GPT install 16:43:57 I installed with standard partitions in a VM 16:44:15 then clicked through storage messing with the existing swap and LVM and could get no crash 16:44:28 * roshi could be doing it wrong, but it wfm 16:44:34 good enough for me 16:44:46 * pwhalen reads scrollback 16:44:47 we can always revisit if cmurf can demonstrate wider impact 16:45:18 i might consider final blocker if it's not fixed by then, this might be the kind of thing where a workaround is OK for beta but not final 16:45:31 true 16:45:33 -1 16:45:55 -1 16:46:08 sounds pretty limited, also needs to be a live install+UEFI/GPT+ 16:46:30 change to -1 16:46:39 -1 Beta 16:47:16 proposed #agreed - RejectedBlocker - 1114786 - Couldn't reproduce this bug. Utilizing noswap is an easy workaround for this if it's run into. Document on Common Bugs. Please repropose for final if it can be shown to have a wider impact. 16:47:22 ack 16:47:22 ack 16:47:32 ack 16:47:33 #agreed - RejectedBlocker - 1114786 - Couldn't reproduce this bug. Utilizing noswap is an easy workaround for this if it's run into. Document on Common Bugs. Please repropose for final if it can be shown to have a wider impact. 16:47:48 sheesh, we're flying! 16:47:55 2 bugs in 49 minutes! 16:47:56 #topic (1098735) apper: hawkey backend missing features 16:47:56 #link https://bugzilla.redhat.com/show_bug.cgi?id=1098735 16:47:56 #info Proposed Blocker, apper, NEW 16:48:59 +1 16:52:42 which criteria was this filed against? 16:53:14 post-install updates, right? 16:53:21 The installed system must be able to download and install updates with the default graphical package manager in all release-blocking desktops. 16:53:23 that's what I'm getting out of it anyways 16:53:33 apper don't work. 16:53:49 * roshi grumbles at that not being put in the blocker proposal 16:54:02 +1 16:54:14 I don't use kde, so I had to look up what apper was 16:54:16 :p 16:54:27 "Installing updates via apper known to crash packagekitd occasionally" is a bit different from 'doesn't work' 16:54:27 * danofsatx didn't write it 16:55:19 does apper not work persistently danofsatx? 16:55:36 that's what I took this bug as saying, reading all the comments 16:55:39 hang on a sec.... 16:56:33 it seems like it can't do groups. 16:56:35 which isn't a criterion. 16:56:58 the only explicit criterion we have is that updates have to work. technically speaking we don't actually require graphical package *install* to work. 16:56:59 perhaps discuss if that should be a criterion at next QA meeting? 16:57:16 for Final we have "All applications that can be launched using the standard graphical mechanism of a release-blocking desktop after a default installation of that desktop must start successfully and withstand a basic functionality test. " 16:57:24 which a package installer that can't install packages might be argued to fail 16:57:30 unfortunately, I haven't been testing it. I've only been monitoring the conversations in #f-kde 16:57:42 i know halfway through this bug i said it was a blocker, but i think i had a different understanding of the bug at that time 16:58:16 i think i'd be -1 to this specific bug as it's a messy popcorn fest, if there are specific bugs in upgrade, we can consider a bug focused on that particular issue as a blocker, but if it's 'it basically works but you get a crash notification sometimes' i'm not sure that blocks 16:58:27 it's definitely something we want to fix for final, but it's not beta thing -1 16:58:56 I lean -1 as the criteria is written, but would be up for a discussion about it at a later time (adding a criteria) 16:59:16 would be +1 at final for sure though 16:59:18 * danofsatx didn't see jreznik in the corner 16:59:32 i can re-propose for final as part of secretarialization 16:59:41 despite the fact I only use the GUI package manager in testing, not irl 16:59:42 please do 16:59:46 -1, should be fixed in final 17:00:32 proposed #agreed - 1098735 - RejectedBlocker - This doesn't clearly violate any *beta* criteria, but would be considered a blocker for final. 17:00:55 s/would/may/ 17:01:01 let's not commit to anything :P 17:01:11 * roshi was wondering that 17:01:21 proposed #agreed - 1098735 - RejectedBlocker - This doesn't clearly violate any *beta* criteria, but may be considered a blocker for final. 17:02:25 * danofsatx reluctantly acks 17:03:02 * danofsatx also realizes kvirc doesn't do spell checking 17:03:24 ack/nack/patch? 17:03:58 danofsatx: do you see this as something that blocks on beta, or do you just think it should be fixed? 17:03:59 acl 17:04:00 ack 17:04:02 ack 17:04:10 final blocker 17:04:22 #agreed - 1098735 - RejectedBlocker - This doesn't clearly violate any *beta* criteria, but may be considered a blocker for final. 17:04:31 I'll be voting +1 at final time 17:04:41 I hope it gets fixed beforehand though 17:04:45 #topic (1147998) Cloud image does not permit successful reboot 17:04:45 #link https://bugzilla.redhat.com/show_bug.cgi?id=1147998 17:04:45 #info Proposed Blocker, cloud-utils, NEW 17:05:03 I've already documented this on common-bugs 17:05:27 basically, if you use an mbr in your image, growroot overwrites it 17:05:48 then you attempt to boot (from previous shutdown or reboot) and it just hangs 17:05:59 +1 blocker 17:06:09 fixes are being worked on now, aiui 17:06:33 adamw: this is that issue ab was running into in #freeipa 17:08:16 ah 17:08:19 you can only boot it once 17:08:22 yeah, sounds like +1 :) 17:10:16 +1, cloud guys really wants this fixed 17:10:22 proposed #agreed - 1147998 - AcceptedBlocker - This bug violates the "Shutdown, Reboot, Logout" Beta criteria. 17:10:31 +1 17:10:33 ack 17:10:34 ack 17:10:41 ack 17:10:46 the criteria just says "desktop" but i mailed test@ looking to change the wording to "system" 17:10:51 btw. criteria are written as release blocking desktops... 17:11:00 #agreed - 1147998 - AcceptedBlocker - This bug violates the "Shutdown, Reboot, Logout" Beta criteria. 17:11:57 or "release blocking products" would fit better 17:12:08 anyways, another discussion for another time 17:12:22 #topic (1142512) 21 Alpha KDE lives and ARM disk image over size limit 17:12:25 #link https://bugzilla.redhat.com/show_bug.cgi?id=1142512 17:12:27 #info Proposed Blocker, distribution, NEW 17:13:53 for arm, I dont think there is a reason to have a size limit. if we do, most users would be using 8GB media to write images. 17:14:16 The KDE image should already be below the size limit now, isn't it? 17:14:36 Kevin_Kofler: i didn't check tc1 yet, lemme see 17:14:42 pwhalen +1 17:14:50 makes no sense for arm 17:15:53 beta TC1 x86-32 live is still over 17:15:54 1054867456 17:16:11 i think we all agree it makes no sense for arm images now, i just need to check if any test cases / policies need to be amended there 17:16:24 beta tC1 x86-64 live is good 17:16:34 if you amend target size to 1400000000 everything is fine of course 17:16:58 I'll have a look at the situation, we may want to increase the target size anyway. 17:17:20 We'll have this sorted out by next Tuesday (next SIG meeting) at the latest. 17:17:42 so punt or -1? 17:18:43 -1 17:18:52 ? as it stands, it's clearly +1. 17:19:02 (if amended to remove 'ARM' and just refer to the 32-bit live.) 17:19:07 id say punt 17:19:14 there are easy things to do to fix it (take stuff out or adjust the target size) 17:19:27 but we have a target size, and we have a beta tc1 image, and the image is bigger than the target size. 17:19:38 i don't see how you can logically say anything but +1, the criterion is very clear. 17:19:54 since when are we logical? 17:19:58 * danofsatx didn't get that memo 17:20:07 I was assuming the target size was going to change 17:20:14 but yeah, you're right 17:20:27 refactor: punt or +1? 17:20:35 punt 17:20:37 punt 17:20:45 punt then, if you must 17:20:53 * adamw really doesn't understand why 17:20:56 but sure, whatever. 17:21:09 * adamw updated bug for TC1 17:21:10 either way we'll be looking at it next week 17:21:26 almost has the same effect does it? we'll be .. right, as roshi said 17:21:34 s/does/doesnt/ 17:21:43 it's a clear +1, but I was waiting to say +1 since the target size for beta was up in the air (even though there's already one written down) 17:23:37 proposed #agreed - 1142512 - Punt - The desired size limit is currently up for discussion. If the limit isn't upped this is a clear blocker, if it is we increased we can revisit next week. 17:23:42 sure, the practical difference isn't much 17:23:49 +1, whatever (pouts) 17:24:07 heh 17:24:39 ack 17:24:45 ack 17:25:10 it really doesn't matter to me - it violates the letter but I'm not sure it's going to stay that way for long 17:25:33 #agreed - 1142512 - Punt - The desired size limit is currently up for discussion. If the limit isn't upped this is a clear blocker, if it is we increased we can revisit next week. 17:25:49 #topic (1038413) fedup stage2 keymap will always be US again for F20-F21 due to anaconda not writing vconsole.keymap kernel parameter any more (#1035316) 17:25:52 #link https://bugzilla.redhat.com/show_bug.cgi?id=1038413 17:25:55 #info Proposed Blocker, fedup, NEW 17:26:07 ok, I'm out. Have a test in "Hardware and Systems Software", a class I really, really, *reaaaallly* don't need. 17:26:13 I'd like to add something about the PK/Hawkey/Apper issue (#1098735): It's right that the bug report is a bit of a mess, but the issue that really matters for us is that installing packages does not work (properly, at least) because Hawkey does not support comps. I've been looking into adding comps support to libhif and PackageKit-hif, but my time is limited, and my unfamiliarity with libhif code and with 17:26:15 GObject code in general does not help either. The crashes when updating, I have no idea whether they're even still reproducible. 17:26:40 + 17:26:47 good luck danofsatx :) 17:26:54 Kevin_Kofler: so the thing is, we don't actually block beta on graphical package install working (which is maybe odd, but hey) 17:27:13 Kevin_Kofler: because the bug covers something that possibly is a blocker under the criteria (but which it doesn't clearly infringe) and something that isn't but possibly shoudl be, the discussion gets confused 17:27:26 Kevin_Kofler: it'd be a lot clearer if there were separate bugs for whatever's wrong with updating vs. whatever's wrong with installing 17:27:46 danofsatx: gl! 17:27:52 danofsatx: Good luck! 17:29:06 adamw: The bug report has become a bit of a mess indeed, I'll see if we can make some clones for the different issues and then we can have a discussion on what blocks Beta, what blocks Final and what is just broken. 17:29:13 Kevin_Kofler: that'd be great, thanks a lot 17:29:26 awesome Kevin_Kofler, thanks :) 17:29:30 we can certainly have a discussion about whether we *should* block beta on graphical package install working, it just needs a clear context 17:30:48 QA agenda item we've created #2 17:32:31 +1 blocker for 1038413 17:32:41 * roshi remembers the discussion for this on F20 fondly 17:33:56 wait, we hit a new bug? 17:33:57 i missed that. 17:34:09 hey, this old friend 17:34:15 yep :) 17:36:42 * adamw refreshes memory 17:36:50 sorry, also splitting time with fesco meeting 17:37:00 np 17:37:24 so i'm pretty sure my initial evaluation is right, but it'd be good to explicitly test 17:37:29 of course, we'd need the fedup bug fixed for that 17:37:46 either +1 or punt, ig uess 17:38:48 any other votes? 17:40:59 i think they're all dead, jim 17:41:17 yeah 17:41:42 Scotty, beam up the bodies so we can do a proper burial 17:42:22 ah yes 17:42:25 I'll give it a few minutes before we call it I guess 17:42:27 sorry.. +1 17:42:43 adamw: get back! Zombie! 17:42:46 it's a miracle! 17:42:57 clearly, we have a difference in interpretation here. 17:43:01 ... 17:43:06 this is awkward 17:43:07 pwhalen: are you feeling more like a) turning water into wine or b) eating brains? 17:43:20 * oddshocks lurking 17:43:30 c) wine + brains 17:43:32 there's another, it's obviously zombies 17:43:41 aaaaaaaaaaaaahhhh alcoholic zombies 17:43:54 adamw: grab your cricket bat and we'll head to the Winchester 17:43:57 heh 17:44:19 oddshocks: vote on 1038413? 17:46:12 hrm, our zombies seem to be narcoleptic 17:46:51 how many blockers do we have left? any really significant ones? 17:47:42 13 left 17:47:48 IMHO, zes, a US kezboard lazout is verz clearlz a blocker, yombies or not. ;-) 17:47:50 eek 17:47:56 well, 14 counting the one we're voting on 17:48:45 well, boot failures, fedup issues, corrupted NTFS volumes 17:53:24 .moar cricket-noises meeting 17:53:25 here meeting, have some more cricket-noises 17:56:32 why does the number seem to keep going up? 17:56:38 i'm sure that's meant to happen the other way around. 17:56:45 proposed #agreed - 1038413 - AcceptedBlocker - This bug partially violates the Beta "Upgrade requirements" criteria. 17:56:47 i think we have enough +1s for this bug at least 17:56:48 ack 17:56:57 well, we started with 19 bugs for this meeting 17:57:07 14 when I emailed the announcement iirc 17:59:18 zoiks 17:59:31 ack 17:59:40 double duty time for me with the arm meeting 18:00:15 fesco is winding up so i can be back fulltime 18:00:31 that leaves you and me here fulltime adamw 18:00:36 unless others are going to join in 18:01:03 tflink oddshocks 18:01:06 ^^ 18:01:07 we should maybe consider changing the meeting day, again, it seems to be coinciding with an awful lot of others 18:01:13 yeah 18:01:19 * adamw tries to remember why we moved from fri to wed 18:01:38 easier for brno folks to make it since it isn't friday evening for them 18:01:48 it worked well until fesco changed to the same time 18:01:50 no idea, been wednesday the whole time for me, iirc 18:02:02 well, that's one of things 18:02:25 what if we moved it up 18:02:28 how short are you on people? 18:02:30 1500 UTC or something 18:02:32 roshi: ask adam 18:02:37 it's me and adamw 18:02:54 pwhalen was here, but is now in an arm meeting that's double booked 18:02:59 * tflink shifts gears 18:03:01 thoughts adamw ? 18:03:05 still here-ish 18:03:20 sigh, then i'd have three 8am meetings a week 18:03:28 it's like you people want me to keep sensible hours or something 18:03:34 we may not have enough for the arm meeting, two so far 18:03:42 DOWN WITH ARM 18:03:50 I'm down with arm 18:03:51 if it was at a different time I would go to the arm meetings :P 18:03:57 adamw: I have six 7am meetings a week... 18:04:01 (Yes, *six*) 18:04:06 ooof 18:04:22 but hey, people have surfaced 18:04:26 (Well, two of them are double-booked, so it's only four workdays, but still..) 18:04:28 * roshi quickly pastes the next bug 18:04:41 I'll help, but I'm multi-tasking 18:04:52 #topic (1146140) boot fail during upgrade from f20 to f21 on udev 18:04:52 #link https://bugzilla.redhat.com/show_bug.cgi?id=1146140 18:04:52 #info Proposed Blocker, fedup-dracut, NEW 18:04:58 thanks sgallagh tflink 18:06:47 seems a +1 to me 18:07:06 not enough data, I think 18:07:16 * tflink is still looking through logs, though 18:08:00 roshi: sorry, I'd have no idea whether to vote yes or no for something like that :P 18:08:02 -1 for now 18:08:10 those logs don't seem to be matching 18:08:11 eh? what data are you looking for? 18:08:21 afaik everyone who's tried a fedup from 20 to 21 hits this 18:08:26 if it's reproducible, +1 18:08:39 those logs aren't from a f20->f21 run 18:08:56 hum, maybe there's a better bug report 18:08:57 but if it's reproducable on a sane system, I'd be +1 18:09:02 i hit this in a clean 20 to 21 test 18:09:38 well, there are no "me too" in the bug, didn't realize it had been reproduced 18:09:48 yeah, that's what I was looking for too 18:10:21 hold on, let me find the one i was looking for 18:10:26 fedup has several issues going on now iirc 18:10:32 ah, https://bugzilla.redhat.com/show_bug.cgi?id=1099299 18:10:58 yeah, i believe this looks like a dupe of that bug 18:10:59 which is also proposed as a blocker for f21 18:11:01 same message 18:11:03 er, beta 18:11:59 close it as a dupe of 1099299. 18:12:07 WFM 18:12:11 Ack 18:12:13 wfm 18:13:09 proposed #agreed - 1146140 - Dupe - Close as a duplicate of 1099299. 18:13:24 ack 18:13:38 ack 18:13:47 #agreed - 1146140 - Dupe - Close as a duplicate of 1099299. 18:13:54 I have to leave for an appt 18:13:57 ack 18:14:10 someone want to take over or call it? 18:14:47 if you leave, do we have enough people to continue? 18:15:17 you, sgallagh adamw and pwhalen - but I think everyone also has other stuff they could/should be working on atm 18:15:36 I can take over if we continue 18:15:39 there's 12 left, not going to make it through them all anyway 18:17:04 adamw, sgallagh, pwhalen: thoughts? 18:17:36 maybe can it for today and try again tomorrow or fri or mon? 18:17:55 works for me 18:18:04 I'll send out an announcement when I get back 18:18:28 all agreed? 18:18:32 Yeah, I'm dealing with rolekit stuff right now 18:18:37 14 days to beta.... 18:18:47 when is freeze, btw? 18:18:51 is it tuesday? 18:19:26 well, I'm going to endmeeting then 18:19:41 thanks for coming! 18:19:42 tflink: no, two weeks 18:19:44 2014-10-14 18:19:51 oh, good 18:20:00 #endmeeting