21:00:39 #startmeeting F18 Alpha Go/No-Go meeting 21:00:39 Meeting started Wed Aug 22 21:00:39 2012 UTC. The chair is jreznik. Information about MeetBot at http://wiki.debian.org/MeetBot. 21:00:39 Useful Commands: #action #agreed #halp #info #idea #link #topic. 21:01:11 #meetingname F18 Alpha Go/No-Go meeting 21:01:11 The meeting name has been set to 'f18_alpha_go/no-go_meeting' 21:02:36 #topic roll call 21:02:42 * nirik waves 21:02:55 chair nirik 21:03:01 #chair nirik 21:03:01 Current chairs: jreznik nirik 21:03:12 adamw, tflink; ? 21:04:21 let's wait a moment... 21:05:58 sorry, lost track of time 21:06:43 tflink: np 21:06:49 #chair tflink 21:06:49 Current chairs: jreznik nirik tflink 21:07:08 who else is/should join? 21:07:15 * spoore is lurking 21:08:00 let's get the ball rolling 21:08:10 yep 21:08:30 #topic Purpose of this meeting 21:08:57 #info Purpose of this meeting is to see whether or not F18 Alpha is ready for shipment, according to the release criteria. 21:09:05 (stealing from robyn ;-) 21:09:17 #info This is determined in a few ways: 21:09:27 #info No remaining blocker bugs 21:09:44 #info Test matrices for Alpha are fully completed 21:10:03 #link http://qa.fedoraproject.org/blockerbugs/current 21:10:24 #link http://fedoraproject.org/wiki/Fedora_18_Alpha_Release_Criteria 21:11:05 anyone wants to add anything? 21:11:44 links for the test matrices? 21:12:19 #link https://fedoraproject.org/wiki/Test_Results:Current_Base_Test 21:12:22 tflink: could you post it - extremely slow network 21:12:25 ah, thanks 21:12:28 #link http://fedoraproject.org/wiki/Test_Results:Current_Installation_Test 21:12:37 #link http://fedoraproject.org/wiki/Test_Results:Current_Desktop_Test 21:14:01 becuase of TC3 installation problems, we do not have a lot of data yet 21:14:34 but adamw encouraged people to test with TC3 if possible to have more data even before TC4 is ready 21:15:06 #topic Blocker Bugs 21:15:41 how far do we want to go through bugs? as blockers meeting covered a lot of this topic a few hours before? 21:16:00 honestly, I don't see a whole lot of point 21:16:05 I think we can cut to the chase. 21:16:09 unless we want to go over the blocker that was just proposed 21:16:22 * jreznik neither 21:16:29 tflink: if there's new one, let's do it 21:17:26 tflink: could you take care (to make it in the right way/process)? 21:17:26 status "new" should suffices and unless wwoods has any updates for 848641 21:17:37 it's a sure no go 21:18:00 #topic (844167) Error in PREIN scriptlet in rpm package libvirt-daemon-0.9.11.4-3.fc17.x86_64 21:18:03 #link https://bugzilla.redhat.com/show_bug.cgi?id=844167 21:18:06 #info Proposed Blocker, ASSIGNED 21:18:16 Viking-Ice: there are more issues than just that bug, unfortunately :( 21:18:57 I'm not sure this is a blocker 21:19:15 if I'm reading this right, it shows up when doing a yum upgrade from F17 -> F18 21:19:33 which would be a beta issue, if we supported yum upgrades 21:19:39 yeah. 21:19:40 libvirt not working is not a blocker 21:19:52 Viking-Ice: how so? 21:19:58 sorry, misread that 21:20:21 selinux neither for alpha afaik 21:20:22 looks like upgrade issue 21:20:29 and a yum upgrade issue to boot 21:21:34 looks like it's even f17 update issue 21:21:58 "I was not upgrading to the f18 libvirt package just f17 updates-testing" 21:22:24 proposed #agreed 844167 - RejectedBlocker (Alpha) - As this is an upgrade issue, it does not fall under the F18 alpha release criteria and is not a blocker for F18 alpha. Upgrades are not considered blocker issues until Beta, it can be re-proposed as a F18 beta blocker. 21:22:38 ack 21:22:44 ack 21:23:44 any other ack/nak/patch? 21:23:47 ack 21:23:51 #agreed 844167 - RejectedBlocker (Alpha) - As this is an upgrade issue, it does not fall under the F18 alpha release criteria and is not a blocker for F18 alpha. Upgrades are not considered blocker issues until Beta, it can be re-proposed as a F18 beta blocker. 21:24:06 OK, that is the only blocker that we didn't hit a couple hours ago 21:24:12 #topic Blocker Bugs 21:25:18 #info at this time there are 19 unresolved blocker bugs for Fedora 18 alpha 21:25:20 #info we decided to skip already processed blockers bug today, see f18-alpha-blocker-review-4 meeting minutes 21:25:29 #link http://meetbot.fedoraproject.org/fedora-bugzappers/2012-08-22/f18-alpha-blocker-review-4.2012-08-22-16.01.html 21:26:21 anything else to blocker bugs topic? 21:26:38 nothing that I can think of 21:26:57 oof. 19. 21:27:07 yep, 19... 21:27:08 given that there already are 19 unresolved accepted blocker bugs then it's clearly a no go =) 21:27:17 several of those are just waiting for karma and push to stable 21:27:25 Viking-Ice: yeah. ;( 21:27:37 spins need to implement 1) asa here 850775 21:27:41 indeed, it's not as bad as it looked before 21:27:47 s/asa/asap 21:28:15 well, let's go to the verdict (surprise, surprise) 21:28:24 #topic Go or No Go? 21:28:49 no va. 21:28:56 Due to the fact that there are unresolved blocker bugs and unsatisfactory test matrix results, QA is no go 21:29:24 #info Due to the fact that there are unresolved blocker bugs and unsatisfactory test matrix results, QA is no go 21:30:16 * nirik nods. Lets put this down as a no-go and get back to trying to fix things. ;( 21:30:19 * jreznik as FPGM is no-go too, see tflink 21:31:15 nirik: yep, we need to fix things 21:32:08 blocker bug owners, please take a look on your bugs and try to fix them as soon as possible 21:33:19 proposal: F18 Alpha is no-go, we slip one week 21:33:26 +1 21:34:13 +1, yep. 21:34:35 ack 21:35:51 oh, sorry, battery died... 21:36:22 #chair jreznik_n9 21:36:22 Current chairs: jreznik jreznik_n9 nirik tflink 21:37:07 I suppose we agreed? when I was disconnected 21:37:17 yeah, +3 -0 21:38:04 tflink, could you please agree it, i'm on phone 21:38:18 #agreed F18 Alpha is no-go, we slip one week 21:38:38 thx 21:39:25 so what's up with team anaconda and this 849250 21:39:26 * jreznik_n9 is going to send a sad slip email, no spherical cows next week 21:39:40 no root password for server installs :( 21:40:16 Viking-Ice: I believe that they're working out a solution 21:40:48 tflink, let's hope so the community is far from being only desktop users ;) 21:40:52 Viking-Ice: we have to poke Anaconda guys 21:41:05 adam was talking to them about it a little while ago 21:41:21 not sure what the resolution was, though 21:41:34 jreznik; try poking with a hot stick next time ;) 21:42:08 * jreznik is nihilist :) 21:42:40 depending how far wwoods has climbed up the latter it might work better using a bottle of good cognac 21:42:59 is there not going to be text only support down the road for firstboot? 21:43:38 spoore: not sure, we dropped using that for F16, I think 21:43:44 I thought firstboot was supposed to die altogether 21:43:48 I accept brown liquor - or clear, if it's homemade 21:43:48 just for gnome 21:43:51 oh, yeah, there's this meeting. 21:44:14 Viking-Ice: there's a feature to replace it for GNOME, but i don't think any of the other desktops signed up for that. 21:44:49 adamw: it's not possible as it's GDM based 21:45:11 #action jreznik to send a slip announcement 21:45:16 #topic open floor 21:45:33 not to be OT :) 21:45:57 is release readiness tomorrow or was I remembering wrong? 21:46:00 if someone selects minimal install it should be presented with the root password dialog that should suffice I suppose 21:46:25 tflink: yes, it is 21:47:09 #info Fedora 18 Alpha Readiness meeting tomorrow - Thursday, Aug. 23, 19:00 UTC (3pm Eastern, 12pm Pacific) in #fedora-meeting-1 21:47:09 Viking-Ice, I'd personally like to see something more like sys-unconfig be supported again for text based installs that don't setup X 21:48:43 ok, anything else? 21:48:50 well team anaconda should consider my RFE about reading kickstart files of persistant storage on the usb install and leave it at that. From my point of view we should be pushing admins more towards kickstart usage 21:48:56 please, do not forget readiness meeting tomorrow\ 21:49:14 is there any point of holding that meeting? 21:49:41 since we are already slipping a week 21:49:47 jreznik, did the readiness meeting reminder go out to the test list? Maybe I missed it? 21:50:24 * jreznik is sorry for some sort of improvisation - but the worst two days in a few years, life does not like schedules... my grandma funeral is tmrw, with travelling and doing it for the first time... 21:50:36 we've been doing the release readiness meeting once right after the first go/no-go for the last couple releases, maybe more 21:51:01 that does not mean it actually made sense thou ;) 21:51:04 spoore: not sure to which list to send it - I sent it to logistic (looking in history what robyn did) 21:51:24 I can for sure forward it to test list 21:51:36 I don't see why not, it covers things like docs, infra rel-eng to try to catch any potential problems but I don't really have a huge preference for when it happens 21:51:37 jreznik, cool...thanks. 21:52:08 Viking-Ice: I think it's not a bad idea to get sync with other teams even we are no-go - they could be too no-go etc... 21:52:40 btw. just kick me when I miss or mess something :) I'm learning the processes! 21:53:06 well us and releng usually are in sync on these matters 21:54:16 Viking-Ice: there are more teams involved - but if you think we should change it, we can talk about it - when is the best time to meet 21:54:17 * jreznik is listening 21:54:39 btw, one more topic 21:54:45 jreznik, perhaps the design team whom else? 21:54:48 #topic next go/no-go meeting 21:55:04 same time next week? 21:55:20 tflink proposed Thursday for next meeting... 21:55:36 I'm pretty sure we agreed to thursday at some point in F17 21:55:55 or I'll propose it now, either way is fine with me :) 21:56:12 hm.. if we slip a week I would think we needed to hold it after that week or a day earlier? 21:56:39 tflink: yep, I saw it in log 21:56:50 not sure I follow, the slipped release date would be the same either way 21:57:12 we'd just be reducing the gap between go/no-go and the potential release date 21:57:56 well we need to have it atleast a day or two before the said release date to give releng time to work things out 21:58:17 IIRC, infra and releng were OK with moving it up a day 21:58:30 and no-go and readiness would be in the same day 21:58:39 if releng os a OK with it let's do it 21:58:49 s/os/is/ 22:00:11 ok, I'll announce the change so in case of any objections, there would be time to change it back to Wed 22:00:17 same time (but Thursday?) 22:00:51 works for me 22:00:53 yeah same time sounds fine since it's beer o clock here on top of the world ;) 22:01:44 for me a new day started a minute ago :))) 22:02:37 #agreed to have next Go/No-Go meeting on Thursday Aug 30, the same time (21:00 UTC/17:00 EDT), jreznik to announce it 22:03:33 well, I think it's all for today meeting, see you tmrw! 22:03:55 and thanks of course! 22:04:27 and thank you for chairing 22:04:46 3 22:04:58 2 22:05:13 1 22:05:20 #endmeeting